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 520698 - crash in Open Folder: looking at a remote dire...
crash in Open Folder: looking at a remote dire...
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-03-06 09:50 UTC by rixed
Modified: 2008-03-06 16:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description rixed 2008-03-06 09:50:20 UTC 
Version: 2.20.0

What were you doing when the application crashed?
looking at a remote directory with the file browser (protocol used was ssh)


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist-Ashen
Icon Theme: gartoon

Memory status: size: 419790848 vsize: 419790848 resident: 26677248 share: 16904192 rss: 26677248 rss_rlim: 18446744073709551615
CPU usage: start_time: 1204782703 rtime: 363 utime: 316 stime: 47 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b8210cd7060 (LWP 3076)]
(no debugging symbols found)
0x00002b820aa1b34f in waitpid () from /lib/libpthread.so.0

+ Trace 191483

Thread 1 (Thread 0x2b8210cd7060 (LWP 3076))

  • #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 strcmp
    from /lib/libc.so.6
  • #6 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libeel-2-2.20.so
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 __libc_start_main
    from /lib/libc.so.6
  • #14 ??
  • #15 ??
  • #16 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (6 sec old) ---------------------
(gnome-panel:3077): Wnck-WARNING **: Unhandled action type (nil)
xscreensaver: 10:48:19: 0: unrecognised ClientMessage "_KDE_WM_CHANGE_STATE" received
xscreensaver: 10:48:19: 0: for window 0x1000c82 (nautilus / Nautilus)
(gnome-panel:3077): Wnck-WARNING **: Unhandled action type (nil)
(nautilus:3076): Eel-WARNING **: No extension, not implemented yet
xscreensaver: 10:48:31: 0: unrecognised ClientMessage "_KDE_WM_CHANGE_STATE" received
xscreensaver: 10:48:31: 0: for window 0x1000e52 (nautilus / Nautilus)
(gnome-panel:3077): Wnck-WARNING **: Unhandled action type (nil)
xscreensaver: 10:48:34: 0: unrecognised ClientMessage "_KDE_WM_CHANGE_STATE" received
xscreensaver: 10:48:34: 0: for window 0x2c00003 (bug-buddy / Bug-buddy)
(gnome-panel:3077): Wnck-WARNING **: Unhandled action type (nil)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-06 16:33:48 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 ***