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 536411 - crash in Home Folder: exited nautilus via "nau...
crash in Home Folder: exited nautilus via "nau...
Status: RESOLVED DUPLICATE of bug 481533
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-03 11:52 UTC by Johannes Rohr
Modified: 2008-06-03 12:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Johannes Rohr 2008-06-03 11:52:20 UTC 
What were you doing when the application crashed?
exited nautilus via "nautilus -q"


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 78954496 vsize: 78954496 resident: 30064640 share: 15687680 rss: 30064640 rss_rlim: 4294967295
CPU usage: start_time: 1212489903 rtime: 3359 utime: 3014 stime: 345 cutime:482 cstime: 76 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6bba720 (LWP 7322)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 199477

Thread 1 (Thread 0xb6bba720 (LWP 7322))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #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-2.0/libnautilus-actions.so
  • #8 ??
  • #9 ??
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #10 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (171 sec old) ---------------------
Arg: 
Itm: file:///home/data/Russia/DANIDA%20RUSLAND%202004-06/REPORTS%20TO%20DANIDA/Auditing%20overview%20Spring07.doc
Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x660583b (OpenOffice)
Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Cmd: xdg-open
Arg: 
Itm: file:///home/data/Russia/DANIDA%20RUSLAND%202004-06/Implementation%20Russia/Small%20grants/North%20People%20Sakha/project%20proposal/Project%20proposal%20North%20People_IWGIA.doc
Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6606266 (OpenOffice)
Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
UPDATING SHAPE
UPDATING SHAPE
UPDATING SHAPE
UPDATING SHAPE
UPDATING SHAPE
UPDATING SHAPE
--------------------------------------------------
Comment 1 A. Walton 2008-06-03 12:06:17 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 481533 ***