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 530318 - crash in Open Folder: reading a network samba ...
crash in Open Folder: reading a network samba ...
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-04-28 09:12 UTC by nick
Modified: 2008-04-28 11:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description nick 2008-04-28 09:12:18 UTC
Version: 2.20.0

What were you doing when the application crashed?
reading a network samba share containing many jpegs from within a working VirtualBox (5.x) VM client Debian/Lenny under Windows XP host



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

System: Linux 2.6.18-3-486 #1 Mon Dec 4 15:59:52 UTC 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 77926400 vsize: 77926400 resident: 22937600 share: 14606336 rss: 22937600 rss_rlim: 4294967295
CPU usage: start_time: 1209350226 rtime: 1077 utime: 539 stime: 538 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c06720 (LWP 2968)]
(no debugging symbols found)
0xb7f98402 in ?? ()

Thread 1 (Thread 0xb6c06720 (LWP 2968))

  • #0 ??
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 ??


----------- .xsession-errors ---------------------
Window manager warning: last_user_time (3076469808) is greater than comparison timestamp (2464485751).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2400931 () appears to be one of the offending windows with a timestamp of 3076469808.  Working around...
current dist not found in meta-release file
Window manager warning: last_user_time (3076240432) is greater than comparison timestamp (2464972239).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2400003 (Network Se) appears to be one of the offending windows with a timestamp of 3076240432.  Working around...
Window manager warning: last_user_time (3075753008) is greater than comparison timestamp (2465056921).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2400003 (Shared Fol) appears to be one of the offending windows with a timestamp of 3075753008.  Working around...
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x240029b specified for 0x24009b5 ().

** (shares-admin:17734): CRITICAL **: clearlooks_style_draw_focus: assertion `height >= -1' failed
Window manager warning: last_user_time (3075580976) is greater than comparison timestamp (2466380227).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2400003 (Services s) appears to be one of the offending windows with a timestamp of 3075580976.  Working around...
Window manager warning: last_user_time (3075572784) is greater than comparison timestamp (2466456497).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2400003 (Shared Fol) appears to be one of the offending windows with a timestamp of 3075572784.  Working around...
Failed to read a valid object file image from memory.
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-28 11:10:46 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 ***