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 537188 - crash in Open Folder: Had started a new nautil...
crash in Open Folder: Had started a new nautil...
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-08 01:08 UTC by gmail
Modified: 2008-06-08 04:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description gmail 2008-06-08 01:08:12 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Had started a new nautilus window on folder using "right-click, start as admin". Crash happened when I went to close that window. This seems to be repeatable, but only seems to happens with windows that were "started as admin". Not critical, since I'm exiting anyway. It is annoying to keep getting a crash message though rather than a clean exit.


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

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 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: 454590464 vsize: 454590464 resident: 29663232 share: 18632704 rss: 29663232 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212885309 rtime: 403 utime: 360 stime: 43 cutime:0 cstime: 1 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 0x2aaf7d430400 (LWP 11511)]
(no debugging symbols found)
0x00002aaf7664aedf in waitpid () from /lib/libpthread.so.0

+ Trace 199830

Thread 1 (Thread 0x2aaf7d430400 (LWP 11511))

  • #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 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


A. Walton





          2008-06-08 04:20:11 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 ***