The command prints some errors and then hangs indefinetly. After cancelling with ctrl-c, nautilus crashes just as well as before.
I'd really like to produce a proper bactrace for you guys. I'm starting to believe that my system is messed up some how, but I've reinstalled all of nautilus's dependencies, and my file system is ok. I've tested my RAM with memtest86 too. I might reinstall, but i don't like to solve problems that way. Anyway, shouldn't nautilus provide a sane error message instead of crashing if something was wrong? [EMAIL PROTECTED]:~$ gnome-session-remove nautilus ** (gnome-session-remove:8613): CRITICAL **: gsm_protocol_new: assertion `GSM_IS_GNOME_CLIENT (gnome_client)' failed ** (gnome-session-remove:8613): CRITICAL **: gsm_protocol_get_current_session: assertion `protocol != NULL' failed ** (gnome-session-remove:8613): CRITICAL **: gsm_session_live: assertion `the_protocol != NULL' failed (gnome-session-remove:8613): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gnome-session-remove:8613): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Removing 'nautilus' from the session On 12/7/06, Sebastien Bacher <[EMAIL PROTECTED]> wrote: > > does running "gnome-session-remove nautilus" before makes a difference? > > -- > Nautilus crashes on startup > https://launchpad.net/bugs/73504 > -- Frode Haugsgjerd Norway -- Nautilus crashes on startup https://launchpad.net/bugs/73504 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
