Le vendredi 07 décembre 2007 à 17:10 +0000, Jay Sears a écrit :
> Package: Nautilus
> Version: 2.20.0
> 
> I use Debian lenny/sid with an up-to-date installation of Nautilus
> (2.20.0). 
> 
> I can run Nautilus as Root when I log in as Root without any problems,
> but when I log in as User and run Nautilus with gksu the cpu goes to
> 100% when I exit Nautilus. An enormous (1 Mb+) debug file is created
> in /root. When I do this on the command line I get a lot of this:
> 
> (nautilus:4328): GLib-GObject-CRITICAL **: g_object_ref: assertion 
> `G_IS_OBJECT (object)' failed
> 
> (nautilus:4328): Gtk-CRITICAL **: gtk_widget_destroy: assertion 
> `GTK_IS_WIDGET (widget)' failed
> 
> (nautilus:4328): GLib-GObject-CRITICAL **: g_object_unref: assertion 
> `G_IS_OBJECT (object)' failed
> 
> (nautilus:4328): GLib-GObject-CRITICAL **: g_object_ref: assertion 
> `G_IS_OBJECT (object)' failed
> 
> etc.
> 
> I have to kill Nautilus before I can use it again (as root).

I’m afraid I can’t reproduce that.

Please install nautilus-dbg, libgtk2.0-0-dbg and libglib2.0-dbg. Then,
when the nautilus process goes wild, open a root terminal and launch
“gdb /usr/bin/nautilus <pid of process running wild>”.

Inside gdb, type “thread apply all bt full” and send us the output.

> PS - you will get more bug reports if you DO NOT EXPOSE THE EMAIL
> ADDRESS of people that submit the reports.
> Spammmers are everywhere.

If we drop useful functionality for the sake of spammers, this means the
terrorists have already won. There are several highly functional spam
filters in Debian.

Thanks,
-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée

Reply via email to