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 538574 - crash in Open Folder: browsing samba folder
crash in Open Folder: browsing samba folder
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-16 10:01 UTC by vesavan
Modified: 2008-06-16 15:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description vesavan 2008-06-16 10:01:55 UTC 
Version: 2.20.0

What were you doing when the application crashed?
browsing samba folder



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: Clearlooks
Icon Theme: gnome

Memory status: size: 468086784 vsize: 468086784 resident: 43499520 share: 17694720 rss: 43499520 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213605828 rtime: 204 utime: 180 stime: 24 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 0x2aadb1819240 (LWP 4319)]
(no debugging symbols found)
0x00002aadaad0fedf in waitpid () from /lib/libpthread.so.0

+ Trace 200549

Thread 1 (Thread 0x2aadb1819240 (LWP 4319))

  • #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 ---------------------
shutting down input chan 0x2b0ca40
Shutting down
Child process exited with status 15
plugin instance destruction
shutting down input chan 0x3620280
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
current dist not found in meta-release file
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Window manager warning: last_user_time (1456382624) is greater than comparison timestamp (4550506).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_A
Window manager warning: 0x3000004 (Software U) appears to be one of the offending windows with a timestamp of 1456382624.  Working around...
current dist not found in meta-release file
warning: .dynamic section for "/lib/libacl.so.1" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 A. Walton 2008-06-16 15:15:23 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 ***