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 486061 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 485997
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-12 16:04 UTC by dezo
Modified: 2007-10-13 00:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description dezo 2007-10-12 16:04:44 UTC
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.22-2-486 #1 Thu Aug 30 23:45:36 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Simple
Icon Theme: Nuvola

Memory status: size: 71499776 vsize: 71499776 resident: 21741568 share: 14872576 rss: 21741568 rss_rlim: 4294967295
CPU usage: start_time: 1192205027 rtime: 254 utime: 237 stime: 17 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c179f0 (LWP 17613)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6c179f0 (LWP 17613))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 _gdk_keymap_key_is_modifier
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (31 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Christian Kirbach 2007-10-13 00:27:39 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 485997 ***