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 575979 - crash in Home Folder: I ran nautilus from comm...
crash in Home Folder: I ran nautilus from comm...
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-19 15:48 UTC by xxtjaxx
Modified: 2009-03-19 15:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description xxtjaxx 2009-03-19 15:48:07 UTC
What were you doing when the application crashed?
I ran nautilus from commandshell as root then i removed some Filöes that i didnt needed anymore from my homes directory which were just for personal purpose and no configuration files then i closed the nautilus windows one after another  and after the last window it crashed 


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 448913408 vsize: 448913408 resident: 27168768 share: 16424960 rss: 27168768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237477411 rtime: 225 utime: 200 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[Thread debugging using libthread_db enabled]
[New Thread 0x7faf2ec63780 (LWP 12142)]
0x00007faf29c525ef in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7faf2ec63780 (LWP 12142))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #7 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #8 IA__g_object_unref
    at /build/buildd/glib2.0-2.16.6/gobject/gobject.c line 1793
  • #9 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #10 IA__g_object_unref
    at /build/buildd/glib2.0-2.16.6/gobject/gobject.c line 1765
  • #11 nautilus_module_extension_list_free
    at nautilus-module.c line 250
  • #12 eel_debug_shut_down
    from /usr/lib/libeel-2-2.20.so
  • #13 main
    at nautilus-main.c line 572
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (2489202 sec old) ---------------------
(nautilus:2360): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch
** (gnome-screensaver:2431): WARNING **: screensaver already running in this session
** Message: Could not connect to power manager: Could not get owner of name 'org.freedesktop.PowerManagement': no such name
** (nm-applet:2391): WARNING **: <WARN>  nma_dbus_init(): org.freedesktop.DBus.Error.FileNotFound raised:
 Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
** (gnome-panel:2357): WARNING **: Failed to establish a connection with GDM: No such file or directory
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2009-03-19 15:58:23 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 480179 ***