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 539717 - crash in Open Folder: Browsina a folder over S...
crash in Open Folder: Browsina a folder over S...
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-06-23 10:13 UTC by Shakey_Jake33
Modified: 2008-06-23 10:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Shakey_Jake33 2008-06-23 10:13:20 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Browsina a folder over Samba share that had video files.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 451330048 vsize: 451330048 resident: 31711232 share: 17387520 rss: 31711232 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214218952 rtime: 221 utime: 200 stime: 21 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 0x2abd38376220 (LWP 3245)]
(no debugging symbols found)
0x00002abd3144dedf in waitpid () from /lib/libpthread.so.0

+ Trace 201148

Thread 1 (Thread 0x2abd38376220 (LWP 3245))

  • #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 (14 sec old) ---------------------
(npviewer.bin:3484): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
(npviewer.bin:3484): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
** (gnome-system-monitor:3540): WARNING **: SELinux was found but is not enabled.
(npviewer.bin:3484): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed

(gnome-terminal:3562): 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 (718116480) is greater than comparison timestamp (540553).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACT
Window manager warning: 0x280001f (Terminal) appears to be one of the offending windows with a timestamp of 718116480.  Working around...
** (nautilus:3245): WARNING **: No description found for mime type "x-directory/smb-share" (file is "sda5"), please tell the gnome-vfs mailing list.
--------------------------------------------------
Comment 1 Gianluca Borello 2008-06-23 10:19:56 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 ***