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 457481 - crash in Open Folder: I was browsing a folder ...
crash in Open Folder: I was browsing a folder ...
Status: RESOLVED DUPLICATE of bug 447104
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-16 20:33 UTC by jason
Modified: 2007-07-16 22:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jason 2007-07-16 20:33:12 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I was browsing a folder that I was SSHed into, I knew the server was down because I had reboot it. I refreshed the folder I was on while the server was down, and got this error.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 109395968 vsize: 109395968 resident: 34435072 share: 19353600 rss: 34435072 rss_rlim: 4294967295
CPU usage: start_time: 1184610055 rtime: 6541 utime: 3699 stime: 2842 cutime:2 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208903968 (LWP 3571)]
[New Thread -1242473584 (LWP 3957)]
[New Thread -1231983728 (LWP 3956)]
[New Thread -1293591664 (LWP 3955)]
[New Thread -1211004016 (LWP 3859)]
(no debugging symbols found)
0x4199d3bd in pthread_mutex_lock () from /lib/libpthread.so.0

+ Trace 148451

Thread 4 (Thread -1293591664 (LWP 3955))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_malloc
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/gnome-vfs-2.0/modules/libsftp.so
  • #11 ??
  • #12 ??
  • #13 ??
    from /usr/lib/gnome-vfs-2.0/modules/libsftp.so
  • #14 ??
  • #15 ?? 


----------- .xsession-errors (9 sec old) ---------------------
aborting...
Xlib: unexpected async reply (sequence 0x497a1)!
(nautilus:3571): gnome-vfs-modules-CRITICAL **: Could not read 1 bytes
(nautilus:3571): gnome-vfs-modules-CRITICAL **: Could not read 4 bytes
(nautilus:3571): gnome-vfs-modules-CRITICAL **: ID mismatch (0 != 15)
(nautilus:3571): gnome-vfs-modules-CRITICAL **: Expected SSH2_FXP_HANDLE(102) packet, got 0
(nautilus:3571): gnome-vfs-modules-CRITICAL **: Could not read 4 bytes
GLib-ERROR **: gmem.c:135: failed to allocate 3103767048 bytes
aborting...
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-07-16 22:46:18 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 447104 ***