After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 545481 - Nautilus not showing the desktop icons & wallpaper on login
Nautilus not showing the desktop icons & wallpaper on login
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: [obsolete] GIO
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-30 10:57 UTC by Sebastien Bacher
Modified: 2012-05-04 20:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Sebastien Bacher 2008-07-30 10:57:04 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/218070

"Binary package hint: nautilus

After an upgrade to hardy, nautilus is often not showing the desktop icons & wallpaper, although the process itself is still running. Attaching strace to it shows it continually trying to read from a socket:

restart_syscall(<... resuming interrupted call ...>) = 0
gettimeofday({1208331785, 315126}, NULL) = 0
stat64("/home/ajmitch/.recently-used.xbel", {st_mode=S_IFREG|0644, st_size=118622, ...}) = 0
read(3, 0x819489c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1208331785, 316371}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8, events=POLLIN|POLLPRI}, {fd=11, events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13, events=POLLIN|POLLPRI}, {fd=14, events=POLLIN}, {fd=19, events=POLLIN|POLLPRI}, {fd=18, events=POLLIN|POLLPRI}, {fd=10, events=POLLIN|POLLPRI}, {fd=26, events=POLLIN}, {fd=31, events=POLLIN}, {fd=16, events=POLLIN}, {fd=21, events=POLLIN}, {fd=17, events=POLLIN}, {fd=20, events=POLLIN, revents=POLLIN}], 16, 4997) = 1
read(20, "l\4\1\1\254\0\0\0\202\6\0\0\255\0\0\0\1\1o\0?\0\0\0/or"..., 2048) = 364
read(20, 0xb5b51008, 2048) = -1 EAGAIN (Resource temporarily unavailable)
read(3, 0x819489c, 4096) = -1 EAGAIN (Resource temporarily unavailable)"


The ubuntu bug has some duplicates, one user mentionned that fc9 has the same issue, the bug seems to happen randomly, bug #543744 could be the same issue
Comment 1 Ilya Chernykh 2008-07-30 11:17:33 UTC
Similar bug in Fedora bug tracker:

https://bugzilla.redhat.com/show_bug.cgi?id=447446
Comment 2 Xavier 2008-08-19 08:53:00 UTC
I have been experiencing this issue for more than one month, and was desperately trying to find the correct search terms until today :)

So I am using gnome 2.22.3 on Arch Linux i686, with default settings. I tried several times to delete all gnome settings from my $HOME folder but it did not help.

Nxx asked on launchpad if we had autologin enabled :
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/218070/comments/21
and that he suspected that not all gconf settings had time to load :
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/218070/comments/23

I am indeed using autologin. I will try without it when I have a chance.

A second thing I noticed :
when my external usb drive is plugged in, this bug is reproducible at 99%
when it is not plugged in, it happens at nearly 0%

But this could be in concordance with some timing issues during startup as Nxx said.

Until now, I just used the "killall nautilus" workaround like Oliver:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/218070/comments/16
Comment 3 Alexander Vasenin 2008-11-23 18:51:57 UTC
This bug never affected me on Ubuntu Hardy, but now on Ubuntu Intrepid I can't see my desktop icons after boot most of the time. 'killall nautilus' helps, but that's ugly. Is there any other workarounds?
Comment 4 Neil Levine 2009-02-04 18:01:57 UTC
I have this issue with Ubuntu 8.10 on a fresh install.

Killing nautilus, as per the suggestion above, does not work for me. Nor does invoking the process manually.

Comment 5 Cosimo Cecchi 2012-05-04 20:41:27 UTC
I think this hasn't been an issue for a long while now.