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 555485 - crash in Open Folder:
crash in Open Folder:
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-10-08 00:52 UTC by personal
Modified: 2008-10-08 15:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description personal 2008-10-08 00:52:33 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 81088512 vsize: 81088512 resident: 28291072 share: 16158720 rss: 28291072 rss_rlim: 4294967295
CPU usage: start_time: 1223427665 rtime: 914 utime: 792 stime: 122 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 0xb6a53710 (LWP 3311)]
0xb7f80424 in __kernel_vsyscall ()

+ Trace 207893

Thread 1 (Thread 0xb6a53710 (LWP 3311))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #8 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #9 ??
  • #10 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #11 ??
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2008-10-08 15:41:56 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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