Spacefm

[Taco.22]

What system are you running, Archie?

[Archie]

Test4 KDE 64-bit

[Taco.22]

Well, this is almost amusing - not .  Just did an update on my system, rebooted and got this -

No Exec line in the session file;
26 Openbox.  Running the GNOME failsafe session instead.

Updates amounted to an 18mb download, and were for Openbox, Thunderbird, htop and some other little thing.  Can't remember if I had updated at all during the Spacefm testing, but I do know I always do updates with a sense of uneasiness!  

EDIT - gnupg (1.4.11-1pclos2010) to 1.4.12-1pclos2012
          htop (0.9-1pclos2010) to 1.0-1pclos2012
          mozilla-thunderbird (9.0.1-1pclos2011) to 10.0-1pclos2012
          openbox (3.5.0-2pclos2011) to 3.5.0-3pclos2012

Got back in through xterm and disabling GDM auto login.  Lost my "desktop" and will have to go fossicking.  Everything else seems to work- -keyboard commands etc.  Who knows!?!  

EXTRA EDIT - Seems that the OB session has changed to "26Openbox", and it had been running "25Openbox" as found in  /etc/X11/wmsession.d.  Wondering if that is purely due to the OB update, or whether there is a conflict.  Either way conky and stalonetray fail to start as listed in the autostart.sh file.

[melodie]

Not fun for sure.

Here is the file:

[root@herisson wmsession.d]# pwd
/etc/X11/wmsession.d

[root@herisson wmsession.d]# cat 26openbox
NAME=Openbox
ICON=/usr/share/pixmaps/openbox
EXEC=/usr/bin/startopenbox
DESC=Documentation for openbox
SCRIPT:
exec /usr/bin/startopenbox
[root@herisson wmsession.d]#

I hope this can help you.

[melodie]

EXTRA EDIT - Seems that the OB session has changed to "26Openbox", and it had been running "25Openbox" as found in  /etc/X11/wmsession.d.  Wondering if that is purely due to the OB update, or whether there is a conflict.  Either way conky and stalonetray fail to start as listed in the autostart.sh file.

/etc/X11/dm/Sessions/ contains 26Openbox.desktop

/etc/X11/wmsession.d contains 26openbox, not "26Openbox".

Yes I remember a change some time ago, it was last year when we got a new Openbox... I don't remember it as very difficult to solve..

[Taco.22]

/etc/X11/dm/Sessions/ contains 26Openbox.desktop

/etc/X11/wmsession.d contains 26openbox, not "26Openbox".

Yes I remember a change some time ago, it was last year when we got a new Openbox... I don't remember it as very difficult to solve..

I don't seem to have any 26openbox.  My /etc/X11/dm/Sessions/ contains 25Openbox.desktop and /etc/X11/wmsession.d contains 25openbox, as well as 27,28 and 29 as kde, gnome and drak3d respectively in both folders.  How do I get this current session to see the autostart.sh file, and could this glitch be related to Spacefm or just an upgrade snafu?

EDIT - Oops, sorry Melodie, I didn't notice that you had posted earlier with a sample file.  It is identical to my 25openbox file.  Do I create a new one called 26openbox?

[Neal ManBear]

Taco.22,    
Create the 26openbox file. Check its permissions to be sure they are correct.    

edit: Check to see if you have libopenbox2 installed. If not, install it.     

[Taco.22]

Looks like my issue with the update may be due to other factors - not Spacefm.  Maybe.

Hey Archie, did you do an update on your system, and when?  Do you have a list of what was installed/updated?  Might be worth looking at.

[Neal ManBear]

Question:     
Did you use the -ivh or the -Uvh option when installing the rpm?     

[Taco.22]

Question:     
Did you use the -ivh or the -Uvh option when installing the rpm?     

Sorry Neal, who is this question for?

[Neal ManBear]

Question:     
Did you use the -ivh or the -Uvh option when installing the rpm?     

Sorry Neal, who is this question for?

     
That's a plural "you." It is for anyone/everyone who installed Archie's RPM.     

[Taco.22]

Oh, well I did install using the -Uvh.  Normally I install things -ivh but I kept reading that the correct way was -Uvh, so I did it this time!  Don't tell me...

[Neal ManBear]

Yes, -Uvh is the better option. It adds the rpm to your update path.      

[Taco.22]

Ah, well I glad I got that right .  Had been wondering.

[Taco.22]

So, to get back to the issue at hand - is it agreed that the issue regarding OB updates is not attributed to Spacefm?  If yes we can move on to further testing of this application.

Regarding Archie's issues - we need to wait for his details regarding updates and/or whatever before we can make any calls regarding Spacefm and his problem.