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 548745 - crash in Open Folder: connecting to samba or w...
crash in Open Folder: connecting to samba or w...
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-08-20 20:43 UTC by ericmayday
Modified: 2008-08-21 09:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description ericmayday 2008-08-20 20:43:31 UTC
Version: 2.20.0

What were you doing when the application crashed?
connecting to samba or windows share server by selecting places -> connect to server and type server location and shared floder.  For example: Service type: window share, Server: xxx.com, Share: warp/pub  NOTE: it is the same setting I did in etch version


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 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: 72830976 vsize: 72830976 resident: 14454784 share: 8282112 rss: 14454784 rss_rlim: 4294967295
CPU usage: start_time: 1218813837 rtime: 1586 utime: 1357 stime: 229 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 0xb6b32720 (LWP 2975)]
[New Thread 0xb56e7b90 (LWP 11469)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b32720 (LWP 2975))

  • #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 (740 sec old) ---------------------
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x2c00003 (PackETH - ); these messages lack timestamps and therefore suck.
The application 'gnome-terminal' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.

(gnome-terminal:7214): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
/usr/bin/su-to-root: line 105:  7498 Killed                  gksu -u "$PRIV" "$COMMAND"
/usr/bin/su-to-root: line 105:  7538 Killed                  gksu -u "$PRIV" "$COMMAND"
Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: No such file or directory
Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: No such file or directory
** (nautilus:2975): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-08-21 09:39:50 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 ***