Bug 187020 - Browsing WEBDAV folders cause crash
Summary: Browsing WEBDAV folders cause crash
Status: RESOLVED DUPLICATE of bug 174580
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-13 03:56 UTC by adam_e
Modified: 2009-03-13 16:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description adam_e 2009-03-13 03:56:28 UTC
Version:            (using KDE 4.1.4)
OS:                Linux
Installed from:    Ubuntu Packages

Whenever I attempt to connect to a WEBDAV share, Dolphin crashes with status 6. It works fine up until the actual connection is established.

WEBDAV share I am attempting to open appears to have a server signed certificate (I'm trying to connect to web hosting company for web site deployment)

Application: Dolphin (dolphin), signal SIGABRT
0x00007f90ddf516b0 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7f90e17056f0 (LWP 22951)):
[KCrash Handler]
#5  0x00007f90ddedc015 in raise () from /lib/libc.so.6
#6  0x00007f90ddeddb83 in abort () from /lib/libc.so.6
#7  0x00007f90dfd806b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007f90dfd807fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007f90e0cba498 in ?? () from /usr/lib/libkio.so.5
#10 0x00007f90e0cc7d2b in ?? () from /usr/lib/libkio.so.5
#11 0x00007f90dfe85134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0x00007f90e0c90b04 in KIO::ListJob::entries () from /usr/lib/libkio.so.5
#13 0x00007f90e0c9ddd6 in ?? () from /usr/lib/libkio.so.5
#14 0x00007f90e0c9df86 in KIO::ListJob::qt_metacall () from /usr/lib/libkio.so.5
#15 0x00007f90dfe85134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x00007f90e0d4fae5 in KIO::SlaveInterface::listEntries () from /usr/lib/libkio.so.5
#17 0x00007f90e0d531ff in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#18 0x00007f90e0d50102 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#19 0x00007f90e0d41143 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#20 0x00007f90e0d43868 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#21 0x00007f90dfe85134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0x00007f90e0c64be0 in ?? () from /usr/lib/libkio.so.5
#23 0x00007f90e0c64d1a in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#24 0x00007f90dfe7fda5 in QObject::event () from /usr/lib/libQtCore.so.4
#25 0x00007f90dec21c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#26 0x00007f90dec299ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#27 0x00007f90e07ce13b in KApplication::notify () from /usr/lib/libkdeui.so.5
#28 0x00007f90dfe70d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#29 0x00007f90dfe719fa in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#30 0x00007f90dfe994d3 in ?? () from /usr/lib/libQtCore.so.4
#31 0x00007f90daf59d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0x00007f90daf5d50d in ?? () from /usr/lib/libglib-2.0.so.0
#33 0x00007f90daf5d6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0x00007f90dfe9915f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#35 0x00007f90decb3a6f in ?? () from /usr/lib/libQtGui.so.4
#36 0x00007f90dfe6f682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#37 0x00007f90dfe6f80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#38 0x00007f90dfe71cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#39 0x00000000004418ed in _start ()
Comment 1 Dario Andres 2009-03-13 11:56:04 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
You need to install the "kdelibs5-dbg" package
((BTW: this is probably fixed on KDE4.2.x ))
Thanks :)
Comment 2 David Faure 2009-03-13 15:30:08 UTC
Yes I recommend testing with KDE-4.2 first.
Comment 3 David Faure 2009-03-13 16:44:52 UTC
Ah, no, actually this is 174580.

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