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 525671 - crash in Computer: Open share forlder via n...
crash in Computer: Open share forlder via n...
Status: RESOLVED DUPLICATE of bug 525181
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-02 01:27 UTC by danny.bc.chang
Modified: 2008-04-04 10:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description danny.bc.chang 2008-04-02 01:27:10 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Open share forlder via network.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-486 #1 Mon Feb 11 13:52:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 133713920 vsize: 133713920 resident: 41746432 share: 20529152 rss: 41746432 rss_rlim: 4294967295
CPU usage: start_time: 1206922494 rtime: 233805 utime: 209137 stime: 24668 cutime:250 cstime: 38 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 0xb6b9b720 (LWP 3118)]
[New Thread 0xb5360b90 (LWP 5846)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 193958

Thread 1 (Thread 0xb6b9b720 (LWP 3118))

  • #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 ---------------------
視窗總管警告：0x3200027 (kdiff3) 指定了無效的 WM_TRANSIENT_FOR 視窗 0x63。
(gnome-terminal:3195): Vte-WARNING **: 未指定控制字元序列‘device-control-string’的處理方式。
(gnome-terminal:3195): Vte-WARNING **: 未指定控制字元序列‘device-control-string’的處理方式。
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
warning: .dynamic section for "/usr/lib/gtk-2.0/modules/libgnomebreakpad.so" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libfam.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-04 10:24:51 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 525181 ***