Bug 175513

Summary:	Dolphin crashes on samba login
Product:	[Unmaintained] kio	Reporter:	Jonathan Thomas <echidnaman>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	alientxc, andresbajotierra, echidnaman
Priority:	NOR
Version First Reported In:	4.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jonathan Thomas 2008-11-18 21:00:44 UTC

Version:            (using KDE 4.1.2)
Compiler:          cc 
OS:                Linux
Installed from:    Ubuntu Packages

Originally reported at https://launchpad.net/bugs/289822

User reported a crash that he could reproduce following the listed steps:
1. ALT+F2 -> dolphin [ENTER]
 2. click in the location-bar and enter the address -> smb://192.168.100.175/ [ENTER]
 3. in the upcomming login-dialog I enter the correct credentials [enter]
 4. BAAM -> dolphin crashed :-(

The crash resulted in the following backtrace:

Anwendung: Dolphin (dolphin), Signal SIGABRT
 [Thread debugging using libthread_db enabled]
 [New Thread 0x7f4ad55666f0 (LWP 7910)]
 [KCrash handler]
 #5 0x00007f4ad1d42fd5 in raise () from /lib/libc.so.6
 #6 0x00007f4ad1d44b43 in abort () from /lib/libc.so.6
 #7 0x00007f4ad3be66b5 in qt_message_output () from /usr/lib/libQtCore.so.4
 #8 0x00007f4ad3be67fd in qFatal () from /usr/lib/libQtCore.so.4
 #9 0x00007f4ad4b1a92f in KDirLister::Private::redirect (this=0x2bd6dc0,
     oldUrl=@0x7fffdd59c080, newUrl=@0x7fffdd59c0a0)
     at /usr/include/qt4/QtCore/qlist.h:395
 #10 0x00007f4ad4b29292 in KDirListerCache::slotRedirection (this=0x27402a0,
     j=0x2a6f4e0, url=<value optimized out>)
     at /build/buildd/kde4libs-4.1.2/kio/kio/kdirlister.cpp:1112
 #11 0x00007f4ad4b2bd5b in KDirListerCache::qt_metacall (this=0x27402a0,
     _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>,
     _a=0x7fffdd59c350)
     at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kio/kdirlister_p.moc:99
 #12 0x00007f4ad3ceb134 in QMetaObject::activate ()
    from /usr/lib/libQtCore.so.4
 #13 0x00007f4ad4af4907 in KIO::ListJob::redirection (this=0x1ee6,
     _t1=0x2a6f4e0, _t2=<value optimized out>)
     at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kio/jobclasses.moc:770
 #14 0x00007f4ad4afa220 in KIO::ListJobPrivate::slotRedirection (
     this=0x2c03110, url=@0x7fffdd59c6c0)
     at /build/buildd/kde4libs-4.1.2/kio/kio/job.cpp:2372
 #15 0x00007f4ad4b01dae in KIO::ListJob::qt_metacall (this=0x2a6f4e0,
     _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>,
     _a=0x7fffdd59c580)
     at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kio/jobclasses.moc:751
 #16 0x00007f4ad3ceb134 in QMetaObject::activate ()
    from /usr/lib/libQtCore.so.4
 #17 0x00007f4ad4bb2715 in KIO::SlaveInterface::redirection (this=0x1ee6,
     _t1=<value optimized out>)
     at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kio/slaveinterface.moc:236
 #18 0x00007f4ad4bb5c30 in KIO::SlaveInterface::dispatch (this=0x2c16180,
     _cmd=20, rawdata=<value optimized out>)
     at /build/buildd/kde4libs-4.1.2/kio/kio/slaveinterface.cpp:278
 #19 0x00007f4ad4bb2f02 in KIO::SlaveInterface::dispatch (this=0x2c16180)
     at /build/buildd/kde4libs-4.1.2/kio/kio/slaveinterface.cpp:90
 #20 0x00007f4ad4ba3f53 in KIO::Slave::gotInput (this=0x2c16180)
     at /build/buildd/kde4libs-4.1.2/kio/kio/slave.cpp:322
 #21 0x00007f4ad4ba6678 in KIO::Slave::qt_metacall (this=0x2c16180,
     _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffdd59c970)
     at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kio/slave.moc:75
 #22 0x00007f4ad3ceb134 in QMetaObject::activate ()
    from /usr/lib/libQtCore.so.4
 #23 0x00007f4ad4ac8830 in KIO::ConnectionPrivate::dequeue (this=0x2a92540)
     at /build/buildd/kde4libs-4.1.2/kio/kio/connection.cpp:82
 #24 0x00007f4ad4ac896a in KIO::Connection::qt_metacall (this=0x2c1c970,
     _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x2c14390)
     at /build/buildd/kde4libs-4.1.2/obj-x86_64-linux-gnu/kio/connection.moc:72
 #25 0x00007f4ad3ce5da5 in QObject::event () from /usr/lib/libQtCore.so.4
 #26 0x00007f4ad2a88c3d in QApplicationPrivate::notify_helper ()
    from /usr/lib/libQtGui.so.4
 #27 0x00007f4ad2a909ea in QApplication::notify () from /usr/lib/libQtGui.so.4
 #28 0x00007f4ad4632b8b in KApplication::notify (this=0x7fffdd59d3c0,
     receiver=0x2c1c970, event=0x2c750c0)
     at /build/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311
 #29 0x00007f4ad3cd6d61 in QCoreApplication::notifyInternal ()
    from /usr/lib/libQtCore.so.4
 #30 0x00007f4ad3cd79fa in QCoreApplicationPrivate::sendPostedEvents ()
    from /usr/lib/libQtCore.so.4
 #31 0x00007f4ad3cff4d3 in ?? () from /usr/lib/libQtCore.so.4
 #32 0x00007f4acedc0d3b in IA__g_main_context_dispatch (context=0x24f2080)
     at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2144
 #33 0x00007f4acedc450d in g_main_context_iterate (context=0x24f2080, block=1,
     dispatch=1, self=<value optimized out>)
     at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2778
 #34 0x00007f4acedc46cb in IA__g_main_context_iteration (context=0x24f2080,
     may_block=1) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2841
 #35 0x00007f4ad3cff15f in QEventDispatcherGlib::processEvents ()
    from /usr/lib/libQtCore.so.4
 #36 0x00007f4ad2b1aa9f in ?? () from /usr/lib/libQtGui.so.4
 #37 0x00007f4ad3cd5682 in QEventLoop::processEvents ()
    from /usr/lib/libQtCore.so.4
 #38 0x00007f4ad3cd580d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
 #39 0x00007f4ad3cd7cbd in QCoreApplication::exec ()
    from /usr/lib/libQtCore.so.4
 #40 0x000000000044185d in main (argc=3, argv=0x7fffdd59d8a8)
     at /build/buildd/kdebase-4.1.2/apps/dolphin/src/main.cpp:94
 #0 0x00007f4ad1db8621 in nanosleep () from /lib/libc.so.6

Comment 1 Dario Andres 2008-12-19 15:38:38 UTC

Have you experienced this bug again with a recent KDE version? (4.1.3 / 4.2beta1 or beta2 / 4.2svn) ? Thanks :)

Comment 2 Jonathan Thomas 2009-01-29 00:25:34 UTC

Wow, I got un-CC'd for some reason...

Yes, we just got a downstream report of this today actually.

Comment 3 Dario Andres 2009-01-30 00:44:00 UTC

Using 4.2 ?
With exactly the same backtrace?
Thanks

Comment 4 Jonathan Thomas 2009-01-30 00:48:57 UTC

Oh, nevermind. I was looking at the wrong backtrace.

Comment 5 Dario Andres 2009-01-30 00:50:27 UTC

So, no one has reported the same crash ? Can I consider this as WORKSFORME?
Thanks for replying

Comment 6 Jonathan Thomas 2009-01-30 00:51:33 UTC

Sure.