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 305104 - connected to webdav directory and crashed
connected to webdav directory and crashed
Status: RESOLVED DUPLICATE of bug 168758
Product: gnome-vfs
Classification: Deprecated
Component: Module: http
2.10.x
Other other
: High critical
: ---
Assigned To: gnome-vfs maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-05-22 16:17 UTC by thomas.albrecht
Modified: 2005-07-17 12:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
debug information from gdb (13.21 KB, text/plain)
2005-05-26 11:50 UTC, Thomas Albrecht
Details

Description thomas.albrecht 2005-05-22 16:17:24 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: connected to webdav directory and crashed
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
connected to mediacenter.gmx.net) via http. i could see the folder for a
sec, then nautilus crashed

Steps to reproduce the crash:
1. define new webdav server connection
2. fill in every needed information (except port, because i didnt know)
3. open created link for webdav
4. fillin password
5. folder openes, and crashes

Expected Results:
Crash.

How often does this happen?
everytime

Additional Information:



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 12866)]
[New Thread -1239852112 (LWP 12880)]
[New Thread -1237042256 (LWP 12872)]
[New Thread -1226552400 (LWP 12869)]
(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 ()
  • #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-05-22 16:17 UTC -------


Unknown version 2.10.0 in product nautilus.  Setting version to "2.10.x".
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 thomas.albrecht@gmx.net.

Comment 1 Sebastien Bacher 2005-05-23 09:05:20 UTC
can you get a backtrace of the crash (http://live.gnome.org/GettingTraces) with
the libglib2.0-0-dbg libgtk2.0-0-dbg nautilus-dbg packages installed?
Comment 2 Thomas Albrecht 2005-05-23 17:33:30 UTC
Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1223891712 (LWP 9807)]
[New Thread -1237988432 (LWP 9854)]
[New Thread -1237722192 (LWP 9853)]
[New Thread -1237042256 (LWP 9846)]
[New Thread -1226552400 (LWP 9836)]
0xffffe410 in __kernel_vsyscall ()
  • #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 IA__g_free
    at gmem.c line 187

I hope this will help. For me it looks some kind confusing ;-)
Comment 3 Sebastien Bacher 2005-05-23 19:11:22 UTC
weird, the backtrace is quite useless.

Do you get a different one if you:
- ps ax | grep nautilus
- gdb -p <pid>, where "<pid>" is the first column of the previous line
(gdb) continue
... crash
(gdb) thread apply all bt
Comment 4 Thomas Albrecht 2005-05-26 11:50:07 UTC
Created attachment 46901 [details]
debug information from gdb

Sorry, it took some time, but here the information is...
Comment 5 Thomas Albrecht 2005-05-31 08:55:06 UTC
Status is still in "Need Info". Is there any more information i can provide?
Comment 6 Sebastien Bacher 2005-06-01 10:40:02 UTC
copying the backtrace to the bug:

Program received signal SIGABRT, Aborted.
[Switching to Thread -1223879424 (LWP 10263)]
0xffffe410 in ?? ()
(gdb) thread apply all bt


Comment 7 Sebastien Bacher 2005-06-01 10:41:06 UTC
no sure, the backtrace is quite short even with the debug packages. I'm
reopening the bug, maybe a maintainer will have an idea of what could be useful
to track this bug
Comment 8 Martin Wehner 2005-06-06 20:50:15 UTC
Reassigning to gnome-vfs.
Comment 9 Sebastien Bacher 2005-07-17 12:58:07 UTC
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 168758 ***