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 537714 - crash in Open Folder: Browsing the C$ share on...
crash in Open Folder: Browsing the C$ share on...
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-11 03:24 UTC by mike
Modified: 2008-06-11 11:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description mike 2008-06-11 03:24:52 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Browsing the C$ share on the host system through VMWare Server 1.06


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

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 84500480 vsize: 84500480 resident: 29097984 share: 16556032 rss: 29097984 rss_rlim: 4294967295
CPU usage: start_time: 1213150525 rtime: 1267 utime: 697 stime: 570 cutime:0 cstime: 1 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 0xb6b8a720 (LWP 3594)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 200087

Thread 1 (Thread 0xb6b8a720 (LWP 3594))

  • #0 __kernel_vsyscall
  • #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 __kernel_vsyscall 


----------- .xsession-errors (23 sec old) ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x40 specified for 0xa03383 ().
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-11 11:14:11 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 ***