Bug#827306: general: won't open file browser/manager if several other programs are already open

[Alberto Luaces]

D&P Dimov writes:

> Alberto Luaces  wrote:
>> several other programs are already open
>>
>> reassign 827306 nautilus
>> thanks
>>
>> D&P Dimov writes:
>>
>>> Dear Alberto,
>>>
>>> I am using GNOME.
>>> When I type nautilus in terminal, and I already have a few programs
>>> running, it doesn't open.
>>> When I type nautilus after fresh restart, I get:
>>>
>>> $ nautilus
>>>
>>> (nautilus:2059): GLib-GIO-CRITICAL **:
>>> g_dbus_interface_skeleton_unexport: assertion
>>> 'interface_->priv->connections != NULL' failed
>>>
>>> (nautilus:2059): GLib-GIO-CRITICAL **:
>>> g_dbus_interface_skeleton_unexport: assertion
>>> 'interface_->priv->connections != NULL' failed
>>> Could not register the application: Timeout was reached
>>>
>>> (nautilus:2059): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
>>> assertion 'GDK_IS_SCREEN (screen)' failed
>>>
>>> (nautilus:2059): GLib-GObject-WARNING **: invalid (NULL) pointer
>>> instance
>>>
>>> (nautilus:2059): GLib-GObject-CRITICAL **: g_signal_connect_object:
>>> assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
>>
>> Those messages seem harmless. From your post, I understand that when
>> it fails, the program just does not output anything to the console and
>> it stays frozen.
>>
>> You can try to see where it is getting stuck by launching it with the
>> debugger:
>>
>> $ gdb nautilus
>>
>> At the gdb prompt, type "r" and then ENTER. When it gets stuck, press
>> ctrl-C and then type "bt" and ENTER. Please post the results.
>
>
>
> Dear Alberto,
> Since the gdb didn't work (see my message below from June 16), is
> there something else I can try to fix the problem? 
> Thanks,
> Luben

Ok, it seems your debugger is not installed.  Please follow the
instructions given in another nautilus reported bug:

"Looks like a livelock. Please install nautilus-dbg and gvfs-dbg, and
obtain a gdb backtrace of the locked process.

See http://wiki.debian.org/HowToGetABacktrace for more information."

In addition, please reply to the bug report address and not directly to
me (I am subscribed to this bug) since otherwise the maintainers of the
package will not see any of your replies since they are held out of the
bug tracking system.

Regards,