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 533837 - crash in Open Folder: Opening a samba share
crash in Open Folder: Opening a 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-19 10:38 UTC by berndt
Modified: 2008-05-19 10:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description berndt 2008-05-19 10:38:19 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Opening a 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-686 #1 SMP Sat Apr 19 00:37:55 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: 81215488 vsize: 81215488 resident: 26574848 share: 16277504 rss: 26574848 rss_rlim: 4294967295
CPU usage: start_time: 1211185556 rtime: 374 utime: 344 stime: 30 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 0xb6c1c720 (LWP 3076)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198101

Thread 1 (Thread 0xb6c1c720 (LWP 3076))

  • #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 (19 sec old) ---------------------
CALLBACK: full-authentication!!!
** (gnome-panel:3074): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-mpmlBa/socket: Connection refused
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:3076): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-mpmlBa/socket: Connection refused
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:3076): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-mpmlBa/socket: Connection refused
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** (nautilus:3076): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-mpmlBa/socket: Connection refused
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-19 10:45:24 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 ***