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 300080 - Nautilus crashes when accessing secure Webdav Share (mediacenter.gmx.net)
Nautilus crashes when accessing secure Webdav Share (mediacenter.gmx.net)
Status: RESOLVED DUPLICATE of bug 153054
Product: gtk+
Classification: Platform
Component: .General
2.6.x
Other other
: Normal normal
: ---
Assigned To: gtk-bugs
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-10 13:35 UTC by christian.georg
Modified: 2005-06-19 22:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description christian.georg 2005-04-10 13:35:05 UTC 
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: Nautilus crashes when accessing secure Webdav Share (mediacenter.gmx.net)
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:

Nautilus crashes reproducably when accessing the secure Webdav Share of
mediacenter.gmx.net

Steps to reproduce the crash:
1. Places/Connect to Server
2. Secure Webdav
3. Enter Login Data
4. Open the mounted share

Expected Results:
One should be able to browse the share but Nautilus crashes instead.

How often does this happen?
Every time


Additional Information:
System is Ubuntu Linux Hoary on i386 Gnome 2.10.1


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223891712 (LWP 9922)]
[New Thread -1239221328 (LWP 9933)]
[New Thread -1238955088 (LWP 9932)]
[New Thread -1237996624 (LWP 9931)]
[New Thread -1226597456 (LWP 9927)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 57974

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
  • #42 ??
  • #43 ??
  • #44 g_free
    from /usr/lib/libglib-2.0.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-10 09:35 -------


Unknown version 2.10.0 in product nautilus.  Setting version to "2.10.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was christian.georg@gmx.de.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Sebastien Bacher 2005-04-10 13:55:04 UTC 
can you get a backtrace with libglib2.0-0-dbg libgnomevfs2-0-dbg libgtk2.0-0-dbg
nautilus-dbg ?
Comment 2 Christian Georg 2005-04-10 21:06:55 UTC 
Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223895808 (LWP 8259)]
[New Thread -1237709904 (LWP 8265)]
[New Thread -1236968528 (LWP 8264)]
[New Thread -1226609744 (LWP 8260)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 58000

Thread 4 (Thread -1226609744 (LWP 8260))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_context_poll
    at gmain.c line 2880
  • #3 g_main_context_iterate
    at gmain.c line 2573
  • #4 IA__g_main_loop_run
    at gmain.c line 2782
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 __JCR_LIST__
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_thread_create_proxy
    at gthread.c line 561
  • #0 __kernel_vsyscall 






Comment 3


Sebastien Bacher





          2005-04-10 21:17:08 UTC
        



thanks for the backtrace. Seems to be a gtk bug, reassigning






Comment 4


Christian Georg





          2005-04-10 22:35:44 UTC
        



thanks for the great desktop! was a pleasure to help.






Comment 5


Christian Kirbach





          2005-06-19 22:14:57 UTC
        



Actually a known problem (Bug 153054) of gnome-vfs

Thanks for the bug report. This particular bug has already been reported into 
our bug tracking system, but please feel free to report any further bugs you 
find.

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