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 530225 - crash in Open Folder: Trying to open a SAMBA n...
crash in Open Folder: Trying to open a SAMBA n...
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-27 17:43 UTC by henley-bugs
Modified: 2008-04-27 22:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description henley-bugs 2008-04-27 17:43:05 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Trying to open a SAMBA network share. Had just entered authentication details.


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

System: Linux 2.6.24-1-powerpc #1 Fri Apr 18 19:53:00 CEST 2008 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 92991488 vsize: 92991488 resident: 24825856 share: 14823424 rss: 24825856 rss_rlim: 4294967295
CPU usage: start_time: 1209307148 rtime: 1796 utime: 1629 stime: 167 cutime:38 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x480416a0 (LWP 3583)]
(no debugging symbols found)
0x0f15e290 in waitpid () from /lib/libpthread.so.0

+ Trace 196270

Thread 1 (Thread 0x480416a0 (LWP 3583))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
  • #17 ??
    from /lib/libc.so.6
  • #18 __libc_start_main
    from /lib/libc.so.6
  • #19 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
** (nautilus:3583): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:3583): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
** (nautilus:3583): CRITICAL **: file_get_share_status_file: assertion `path != NULL' failed
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-27 22:28: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 ***