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 532471 - crash in Computer: I was trying to access a...
crash in Computer: I was trying to access a...
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-10 12:14 UTC by chuichih
Modified: 2008-05-10 13:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description chuichih 2008-05-10 12:14:28 UTC 
Version: 2.20.0

What were you doing when the application crashed?
I was trying to access a notebook which is connected in the same network under a router. The notebook has Windows XP.
I tried to access a shared directory on the notebook and Nautilus failed every time.


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

System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: gnome

Memory status: size: 493023232 vsize: 493023232 resident: 36597760 share: 21065728 rss: 36597760 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210421269 rtime: 304 utime: 282 stime: 22 cutime:0 cstime: 0 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 0x2b18f2401240 (LWP 3008)]
(no debugging symbols found)
0x00002b18ebce034f in waitpid () from /lib/libpthread.so.0

+ Trace 197370

Thread 1 (Thread 0x2b18f2401240 (LWP 3008))

  • #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 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
(nautilus:3008): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:3008): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:3008): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running
** (nautilus:3008): WARNING **: 沒有任何有關 mime 類型“x-directory/smb-share”的說明（檔案為“share”），請回報至 gnome-vfs 電郵論壇。
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-10 13:35:29 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 ***