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 589613 - crash in Home Folder: close nautilus
crash in Home Folder: close nautilus
Status: RESOLVED DUPLICATE of bug 584745
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-24 14:14 UTC by may
Modified: 2009-07-24 15:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description may 2009-07-24 14:14:59 UTC
What were you doing when the application crashed?
close nautilus


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.30go #5 SMP PREEMPT Tue Jun 16 15:35:19 CST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10602000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Shiki-Wise
Icon Theme: gnome-wise
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 92114944 vsize: 92114944 resident: 28344320 share: 21577728 rss: 28344320 rss_rlim: 18446744073709551615
CPU usage: start_time: 1248443712 rtime: 365 utime: 324 stime: 41 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]
0xb8024424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6f04750 (LWP 19057))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 __libc_start_main
    from /lib/i686/cmov/libc.so.6
  • #8 _start
    at ../sysdeps/i386/elf/start.S line 119
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (25593 sec old) ---------------------
(firefox-bin:2756): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2756): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2756): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2756): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2756): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2756): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2756): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-07-24 15:50:33 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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