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 519419 - crash in Computer: quiter nautilus lanser e...
crash in Computer: quiter nautilus lanser e...
Status: RESOLVED DUPLICATE of bug 496332
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-28 23:33 UTC by synops.corps
Modified: 2008-02-29 11:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description synops.corps 2008-02-28 23:33:56 UTC
Version: 2.20.0

What were you doing when the application crashed?
quiter nautilus lanser en sudo


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 409894912 vsize: 409894912 resident: 28446720 share: 17264640 rss: 28446720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1204241538 rtime: 164 utime: 147 stime: 17 cutime:121 cstime: 25 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b2b84152aa0 (LWP 1479)]
(no debugging symbols found)
0x00002b2b7e0d55ef in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b2b84152aa0 (LWP 1479))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #6 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #7 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #8 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #9 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #10 nautilus_module_extension_list_free
  • #11 eel_debug_shut_down
    from /usr/lib/libeel-2-2.20.so
  • #12 ??
  • #13 __libc_start_main
    from /lib/libc.so.6
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (1769009 sec old) ---------------------
ALSA lib ../../../src/pcm/pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave
ALSA lib ../../../src/pcm/pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave
ALSA lib ../../../src/pcm/pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave
(gecko:15126): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
** (gnome-panel:4076): WARNING **: Failed to establish a connection with GDM: Aucun fichier ou répertoire de ce type
Avertissement du gestionnaire de fenêtres : CurrentTime used to choose focus window; focus window may not be correct.
Avertissement du gestionnaire de fenêtres : Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
(startupmanager:5794): libgnomevfs-WARNING **: Failed to re-activate daemon: Connection is closed
** Message: Got disconnected from the session message bus; retrying to reconnect every 10 seconds
The application 'gnome-screensaver' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-02-29 11:14:58 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 496332 ***