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 532336 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-09 12:57 UTC by jgranqvist
Modified: 2008-05-09 18:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description jgranqvist 2008-05-09 12:57:42 UTC 
Version: 2.20.0

What were you doing when the application crashed?



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 Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tangerine

Memory status: size: 77660160 vsize: 77660160 resident: 31010816 share: 17702912 rss: 31010816 rss_rlim: 4294967295
CPU usage: start_time: 1210317175 rtime: 670 utime: 607 stime: 63 cutime:4 cstime: 2 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 0xb6b6a720 (LWP 3720)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197307

Thread 1 (Thread 0xb6b6a720 (LWP 3720))

  • #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 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libeel-2-2.20.so
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (17350 sec old) ---------------------
not trans
413
m| 180008
not rec
:images/receiving-high-signal.png
|idle-high-signal.png
 wlan0:21226456   52820    0    0    0     0          0         0  1054140    8817    0    0    0     0       0          0
not trans
455
m| 180008
not rec
:images/idle-high-signal.png
|idle-high-signal.png
 wlan0:21227738   5282
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-05-09 18:25:21 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 355018 ***