Hi,
I just found out something that could be
very interesting. I am now in a live USB session, and that is where I am writing from.
Figure out, I got all : background wallpaper and desktop icon as soon as I logged in !!! Here is my ~/.xsession-errors:
[guest@localhost ~]$ cat .xsession-errors
localhost being added to access control list
** (lxpanel:2627): DEBUG: cache file_name = /home/guest/.cache/menus/a7cabe738af90d5719a123b7735af397
SIOCETHTOOL: Operation not supported
SIOCETHTOOL: Operation not supported
[guest@localhost ~]$
This shows NO PCManFM ERROR !
I will ask the poeple who will test the next to try this, to check if my finding works for all:
At the start when boot menus appear, if you use Grub: Edit the boot line, at the end of line add this :
init 3. change the splash=silent for splash=noquiet.
If you use a CD, or Virtualbox, you have the isolinux boot, and there, there is a line to boot in mode "Console", choose this one.
Then boot.
At the end of the boot time you will have just a prompt : write
guest for login, validate, write
guest for password and BEFORE running startx, go to the .config/openbox directory and
edit autostart.sh:
[guest@localhost ~]$ cd .config/openbox
[guest@localhost ~]$ mcedit autostart.shwith keyboard arrow go down to the line feh and
add a # to comment it out at the beginning of the line, then
hit F2 to save the change
then F10 to quit the mc editor.
Then only,
type startx to start the session. Come back, and tell us the result of this.
It must absolutely be done
in a live session, to check this hypothesis : I think that pcmanfm can't start normally because of a certain number of processes that have not finished to start, at the moment when the session is started - when in runlevel 5 -
Why that ? I noticed in one of the tty, just after login with GDM that several processes where still being started and took some time to finish start before offering the login prompt (it might be in tty6). Then this morning, I read in the /etc/rc.sysinit file : that if the boot is not done in runlevel 5 (graphical boot) then SPEEDBOOT is NOT USED. Therefore I think that if what I think is right, then I would just have to ask about to the people knowing the initscripts to learn how to deactivate speedboot properly to solve the problem. And that would be the clean solution I am looking for.
Thanks,
Mélodie.