nautilus unable to start on login

thank you for your bug report, do you use the option to not display the background in nautilus?

nautilus show_desktop value in gconf is set to true.

This behaiviour suddely stopped after being logged in for two hours (vmware machine sitting in background), no apparent reason ( I was at the time looking at the gnome "run" application, system monitor, and an idle terminal, nothing of which reproduces the remedy when I shutdown and boot again (behaviour is back to snafu)

Still experiencing same problem, fully updated.

Wallpaper shows up randomly when the bug happens, i.e. it may or may not show up whilst nautilus is "erroring" (but no icons).
Wallpaper always shows up along with icons when error stops.

Error usually stops at some random point after login, anything from 10 seconds to 2 hours according to experience.

This is happening to me as described also, but not under vmware.

Solution described by Bernard works for me as well, assigning bug to brasero instead.

and what's the workaround? why is this a brasero issue? could you please elaborate?

Simply
sudo apt-get remove brasero
solves the issue, thus presuming it's brasero-related.

End of messages log (attached) shows segfaults in nautilus caused by libbrasero-media0 (presumably) as described by Bernard.

However, it seems I only have 181 instances mentioning brasero in all message logs (# cat /var/log/messages* | grep -c brasero # ) And at an average rate of more than 1 new nautilus instance per second I'm guessing that it is only a relative few of the instances which segfaults (if all segfaulted I'd have well over 3000 from a single 1h test session).

Correction:
# sudo apt-get remove libbrasero-media0 # solves the issue.

Since I'm using vmware, why not use it for reproducing bug:
Download vmx and vmdk files attached.
add to library containing latest jaunty daily livecd 19-Feb-2009 08:11. (alteratively edit vmx file to correct iso path)
start vmx file with vmware player.

even on livecd boot I experience this bug.

second file

Issue persists on livecd 24-Feb-2009 08:16

I've tested installing .deb packages manually:

Error shows up in latest three package versions:
libbrasero-media0_2.25.90-0ubuntu1_i386.deb
libbrasero-media0_2.25.91-0ubuntu1_i386.deb
libbrasero-media0_2.25.91.1-0ubuntu1_i386.deb (current)

Error does NOT show up in earlier package versions:
libbrasero-media0_0.9.1-0ubuntu1_i386.deb
libbrasero-media0_0.9.1-0ubuntu2_i386.deb
libbrasero-media0_0.9.1-0ubuntu3_i386.deb

What are the changes from 0_0* to 0_2* ?

Further testing in vmware indicates that this is probably a conflict with specific hardware/drivers, since this only happens when I have iso mounted to vmware machine, if I switch over to physical drive (host drive access) it works.

Would be interesting to see what type of drive Bernard was using though. Since it was non-virtual.

Please could someone please test this so we can confirm it?

It may be that it only appears on obscure hardware but it is still a bug (and vmware isn't really that uncommon...)

This is happening on non-obscure hardware as well now. Just installed the beta on a Dell 1420n and experience the same effects. 'killall nautilus' takes care of it, but there has to be a better way.

I have removed libbrasero-media0 (along with the rest of Brasero), yet the problem still persists after every login.

Daisuke_Ido: Could you have a look at your dmesg and see if it is libbrasero that causes things in your case, you can use the command:

cat /var/log/messages | grep nautilus

And see if you also get strings like:
[ 42.636631] nautilus[3660]: segfault at 98a0008 ip b5d9755d sp b5d85fc0 error 4 in libbrasero-media.so.0.1.1[b5d87000+1e000]

If not it may be a different issue. Or it may be that the fundamental error isn't in brasero after all...

This is NOT a definite indication, since it has to go on for a while before you see a few crashes (only very few of the hundreds of nautilus apps do crash and generate this message, and depending on the case maybe none will crash like this?)

Turns out there's absolutely nothing in /var/log/messages about nautilus crashing. Interesting side effect, after about 15 minutes of leaving it running to see if I could catch a crash, my entire desktop locked up. It could be unrelated, though.

I completely removed Brasero as per Bernard's original suggestion and your follow up. To take care of thie issue, I am able to pkill nautilus after logging in. After that, Nautilus works as expected.

I ended up doing a fresh beta install on that laptop, switching from 32-bit to 64-bit. I did not experience this bug there.

I confirm the bug. I installed ubuntu 9.04 beta in vmware fusion 2.0 (over a macbook pro)

Hit this bug, it seems, on vmware fusion 2.0.3 just now.

unmouting the install iso fixed the issue before applying any updates/patches

I too face this issue. Seems this happens when there is a mounted volume which is no longer available.

Fully updated now I seem not to face this issue, and when I try downgrade brasero + libbrasero-media0 to versions which caused trouble before I get a slightly different behaviour: nautilus refuses to start but is not "spammed" in window list, and when started manually it gives a very different error...

Anyhow could anyone else confirm/refute that this issue is gone in latest versions: daily live >= 6/march

I have this bug after an recent upgrade of samba and vlc main packages (with the related libraries) - searching over the net I found this bug under different instances so is not related to Brasero (I removed brasero with config files and some related libraries - restart ).

After cat /var/log/messages | grep nautilus I get the following ... :
Jul 10 15:16:46 SQ2 kernel: [ 1741.254289] nautilus[10512]: segfault at b4d9bd50 ip b4d9bd50 sp bfd5dd7c error 4 in SYSV00000000 (deleted)[b4e8f000+60000]
Jul 10 15:18:11 SQ2 kernel: [ 1826.371974] nautilus[11591]: segfault at b4fa0d50 ip b4fa0d50 sp bf8689ac error 4 in SYSV00000000 (deleted)[b50bb000+60000]
Jul 10 18:14:11 SQ2 kernel: [ 2773.002205] nautilus[7218]: segfault at b6328d50 ip b6328d50 sp bf9c026c error 4
Jul 10 18:22:33 SQ2 kernel: [ 3275.234963] nautilus[10036]: segfault at b61a5d50 ip b61a5d50 sp bfb473fc error 4
Jul 10 18:22:44 SQ2 kernel: [ 3285.594691] nautilus[9971]: segfault at b4ee3d50 ip b4ee3d50 sp bf8a68bc error 4 in SYSV00000000 (deleted)[b4fca000+60000]
Jul 10 19:17:03 SQ2 kernel: [ 2176.735920] nautilus[12599]: segfault at b630fd50 ip b630fd50 sp bfcaf55c error 4
Jul 10 19:49:02 SQ2 kernel: [ 4095.376448] nautilus[14180]: segfault at b4f28d50 ip b4f28d50 sp bf9f2a0c error 4 in SYSV00000000 (deleted)[b5043000+60000]
Jul 11 17:17:59 SQ2 kernel: [ 2457.685645] nautilus[8702]: segfault at b4ecad50 ip b4ecad50 sp bfc96cbc error 4 in SYSV00000000 (deleted)[b4fe4000+60000]
Jul 11 17:21:15 SQ2 kernel: [ 2653.436199] nautilus[9847]: segfault at b501ad50 ip b501ad50 sp bffe17fc error 4 in 4c73fe0c47614734b17d736dbde7580a-x86.cache-2[b513f000+1000]
Jul 11 17:48:02 SQ2 kernel: [ 1573.491976] nautilus[7782]: segfault at b4ed3d50 ip b4ed3d50 sp bf96e98c error 4 in SYSV00000000 (deleted)[b4fed000+60000]
Jul 11 17:49:24 SQ2 kernel: [ 1655.944604] nautilus[8348]: segfault at b5048d50 ip b5048d50 sp bfee983c error 4 in SYSV00000000 (deleted)[b5162000+60000]
Jul 11 22:30:37 SQ2 kernel: [ 757.018356] nautilus[5077]: segfault at b6236d50 ip b6236d50 sp bfcc2d7c error 4

I can't start nautilus in 10.04 Beta 1. It tries to open windows but it does nothing. I get no message when launching nautilus from terminal.

I just started experiencing this in Ubuntu 10.04 64bit.

First it started out with both my desktop icons and panels not showing up.

I fixed the panels by simply adding "gnome-panel" to the startup applications.

However the desktop icons remain missing until I manually open up a nautilus window, then the desktop icons will appear.

$ nautilus -q
(nautilus:2060): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)

$ ps aux | grep nautilus
jeff 2063 0.0 0.0 7616 892 pts/0 S+ 17:51 0:00 grep --color=auto nautilus

$ nautilus
Initializing nautilus-gdu extension
(Icons appear after that)

Nemes Ioan Sorin mentioned "vlc" and "samba" above which just happen to be two apps I just installed about the same time I started experiencing this problem. I'm removing those now and will test out the environment to see if that solved the problem for me.

UPDATE: Removing "vlc" and "samba" didn't seem to do anything. Desktop icons are still missing upon startup. The desktop icons do show up after I open a nautilus folder.

To expand on my setup/situation...

I just started having this problem today in Ubuntu 10.04. It started out as I wasn't able to see panels, desktop icons, or window borders and Alt+F2 didn't work either among several other problems. The entire desktop was useless -- I couldn't do anything. This all occurred after I performed some system updates, installed Minitube and Minitunes. I was doing some system maintenance so to pin point what started this issue would be tough.

So I reinstalled a brand new (downloaded from ubuntu.com today) copy of 10.04. The initial startup was problem-free, but somewhere after installing apps/updates I started experiencing problems. The desktop environment was functional at least, but the gnome-panel and desktop icons weren't showing up (Fix for my gnome-panel problem is in my above post).

Applications I installed: Parcellite Clipboard Manager, GIMP, Pidgin, Adobe Reader, Songbird, Docky, Ubuntu Tweak, and medibuntu, restricted extras, codecs and those things. I also uninstalled some default software like Rhythmbox and Empathy.

I am using elementary theme and nautilus-elementary breadcrumbs.

Ubuntu Tweak settings are as follows:
Compiz Settings: No boxes checked
Desktop Icon Settings: Shop desktop icons
GNOME Settings: Enable Panel Animations, Show icons in menus, Show icons on buttons
Window Manager Settings: Use Metacity window theme, Enable window transparency
Session control: File Manger: nautilus / Panel: gnome-panel / Window Manger: gnome-wm

+1 experiencing this bug from today... Here my Desktop icons dissapear, but no problem with gnome-pannel. Alt+f2 works...
Trying to run nautilus from shell gives same DBUS error
I did not install anything, just made updates..
I get an error in dmesg abouyt fglrx,
[fglrx:fireglAsyncioIntDisableMsgHandler] *ERROR* IRQMGR returned error 1 when trying to disable interrupt source ff000066
but removing it in jockey and restarting did not fix it...

It seems that my problem was this issue: http://ubuntuforums.org/showthread.php?p=8686018
I solved it by moving all my files in the Desktop folder to a temp one... It is probably a corrupted jpg file... Hope this solve others problems... It is still a bug though...

Since we have so much baggage from an old prerelease Jaunty issue, which was likely fixed, and is likely not related to the new issues seen:
Please report a new and clean bug report detailing the issues present NOW, with Lucid.

I think from an organisatory point of view, and for the sake of drawing attention to it. Reporting a new bug instead of completely redirecting this one, will be better.

Feel free to put a link to the new bug in the description and in the comments, if people end up finding this bug first.

I just added "nautilus" to my auto start programs and it fixed the problem of nautilus not launching upon starting up.