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 535395 - crash in Open Folder: Im try to explore a Host...
crash in Open Folder: Im try to explore a Host...
Status: RESOLVED DUPLICATE of bug 522534
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-29 04:20 UTC by basher2
Modified: 2008-05-29 11:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description basher2 2008-05-29 04:20:08 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Im try to explore a Host network with SAMBA, the host network have a lot of folders and files.


Distribution: Red Hat Linux Release 4.0
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 467775488 vsize: 467775488 resident: 25432064 share: 13352960 rss: 25432064 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212034446 rtime: 251 utime: 216 stime: 35 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 0x2b74cd841b80 (LWP 16502)]
(no debugging symbols found)
0x00002b74c7366edf in waitpid () from /lib/libpthread.so.0

+ Trace 198933

Thread 1 (Thread 0x2b74cd841b80 (LWP 16502))

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


----------- .xsession-errors (8 sec old) ---------------------
(nautilus:16502): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:16502): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running

(gnome-terminal:16536): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Window manager warning: last_user_time (1294582432) is greater than comparison timestamp (853715507).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: 0x3800020 (Terminal) appears to be one of the offending windows with a timestamp of 1294582432.  Working around...
Window manager warning: last_focus_time (853745947) is greater than comparison timestamp (853745619).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
** (nautilus:16502): WARNING **: No description found for mime type "x-directory/smb-share" (file is "music"), please tell the gnome-vfs mailing list.
--------------------------------------------------
Comment 1 Gianluca Borello 2008-05-29 11:20:58 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 522534 ***