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 533097 - crash in Open Folder: browsing samba share
crash in Open Folder: browsing samba share
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-14 12:46 UTC by vesavan
Modified: 2008-05-14 16:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description vesavan 2008-05-14 12:46:22 UTC
Version: 2.20.0

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



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 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: 519688192 vsize: 519688192 resident: 48685056 share: 19513344 rss: 48685056 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210600476 rtime: 2105 utime: 1913 stime: 192 cutime:1139 cstime: 121 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 0x2ab00d00c240 (LWP 19281)]
(no debugging symbols found)
0x00002ab006902edf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2ab00d00c240 (LWP 19281))

  • #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 ---------------------
** (gnome-system-monitor:14239): WARNING **: SELinux was found but is not enabled.
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
/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 (2168791712) is greater than comparison timestamp (129768313).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: 0x3a00004 (Software U) appears to be one of the offending windows with a timestamp of 2168791712.  Working around...
Window manager warning: 0x3e00004 (Software U) appears to be one of the offending windows with a timestamp of 1968886432.  Working around...
error from apt: 'E:Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?'
Window manager warning: last_user_time (2168791712) is greater than comparison timestamp (129768425).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: 0x3a00113 () appears to be one of the offending windows with a timestamp of 2168791712.  Working around...
current dist not found in meta-release file
warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-14 16:52:00 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 522534 ***