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 520520 - crash in File Browser: Navegando por carpetas d...
crash in File Browser: Navegando por carpetas d...
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-05 14:14 UTC by giampaolig
Modified: 2008-03-06 16:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description giampaolig 2008-03-05 14:14:53 UTC
Version: 2.18.3

What were you doing when the application crashed?
Navegando por carpetas de red wan


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

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 112005120 vsize: 112005120 resident: 33173504 share: 19087360 rss: 33173504 rss_rlim: 4294967295
CPU usage: start_time: 1204725257 rtime: 1484 utime: 1281 stime: 203 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 -1208228128 (LWP 3368)]
[New Thread -1220224112 (LWP 3611)]
[New Thread -1242494064 (LWP 3543)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1220224112 (LWP 3611))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strstr
    from /lib/libc.so.6
  • #5 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #6 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 ??
  • #11 atol
    from /lib/libc.so.6
  • #12 gnome_vfs_parse_ls_lga
    from /usr/lib/libgnomevfs-2.so.0
  • #13 ??
    from /usr/lib/gnome-vfs-2.0/modules/libftp.so
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??


----------- .xsession-errors (24 sec old) ---------------------
localuser:giampaolig being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3245
could not attach to desktop process
Advertencia del gestor de ventanas: Received a _NET_WM_MOVERESIZE message for 0x1201629 (CASO_SBC3 ); these messages lack timestamps and therefore suck.
(nautilus:3368): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is
(nautilus:3368): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is
(nautilus:3368): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is
(nautilus:3368): libgnomevfs-WARNING **: gnome-vfs-monitor.c: A monitor handle was destroyed before it was added to the method hash table. This is a bug in the application and can cause crashes. It is
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-06 16:58:08 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 454799 ***