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 419485 - crash in Computer: connecting to a samba sh...
crash in Computer: connecting to a samba sh...
Status: RESOLVED DUPLICATE of bug 389375
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-17 20:13 UTC by CodySchuyler
Modified: 2007-03-29 02:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description CodySchuyler 2007-03-17 20:13:07 UTC
Version: 2.16.3

What were you doing when the application crashed?
connecting to a samba share


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.3 2007-03-16 (Gentoo)
BugBuddy Version: 2.16.1

System: Linux 2.6.19-gentoo-r5 #2 SMP Sat Mar 17 00:12:06 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled

Memory status: size: 269340672 vsize: 269340672 resident: 20115456 share: 14028800 rss: 20115456 rss_rlim: -1
CPU usage: start_time: 1174147965 rtime: 38 utime: 36 stime: 2 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47896289768992 (LWP 6009)]
[New Thread 1124096320 (LWP 6036)]
[New Thread 1082132800 (LWP 6035)]
[New Thread 1098918208 (LWP 6034)]
[New Thread 1090525504 (LWP 6033)]
[New Thread 1107310912 (LWP 6032)]
[New Thread 1115703616 (LWP 6017)]
0x00002b8fb8fc2869 in poll () from /lib/libc.so.6

Thread 7 (Thread 1115703616 (LWP 6017))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 ??
    from /usr/lib/libdbus-1.so.3
  • #6 ??
    from /usr/lib/libdbus-1.so.3
  • #7 dbus_pending_call_steal_reply
    from /usr/lib/libdbus-1.so.3
  • #8 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #11 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #12 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6
  • #17 ??


----------- .xsession-errors ---------------------
** (bug-buddy:5987): WARNING **: Couldn't load icon for Open Folder
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
process 6009: arguments to dbus_pending_call_steal_reply() were incorrect, assertion "pending->completed" failed in file dbus-pending-call.c line 674.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
** (bug-buddy:6031): WARNING **: Couldn't load icon for Bonobo Component Browser
** (bug-buddy:6031): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 Susana 2007-03-18 17:57:04 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 André Klapper 2007-03-29 02:02:20 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 389375 ***