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 540212 - crash in Open Folder: logging into my windows ...
crash in Open Folder: logging into my windows ...
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-25 20:32 UTC by lennartackermans
Modified: 2008-06-25 20:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description lennartackermans 2008-06-25 20:32:37 UTC 
Version: 2.20.0

What were you doing when the application crashed?
logging into my windows file server with smb


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

System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 76447744 vsize: 76447744 resident: 25812992 share: 14520320 rss: 25812992 rss_rlim: 4294967295
CPU usage: start_time: 1214400336 rtime: 6623 utime: 5881 stime: 742 cutime:0 cstime: 4 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 0xb6b91720 (LWP 2967)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 201387

Thread 1 (Thread 0xb6b91720 (LWP 2967))

  • #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 (164852 sec old) ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
Window manager warning: last_focus_time (1231594) is greater than comparison timestamp (1231573).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACT
gnome-mount 0.7
gnome-mount 0.7
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-8043--1927794639-1214260849 --active --geometry 80x24+51+346 --title lennart@lenserver: ~ 
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
** Message: Got disconnected from the session message bus; retrying to reconnect every 10 seconds
--------------------------------------------------
Comment 1 Gianluca Borello 2008-06-25 20:45:44 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 ***