Bug 173008 - crash after samba login with dolphin
Summary: crash after samba login with dolphin
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-17 08:08 UTC by Christian Haehnlein
Modified: 2009-01-16 12:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Haehnlein 2008-10-17 08:08:57 UTC 
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    SuSE RPMs

Anwendung: Dolphin (dolphin), Signal SIGSEGV
[?1034h(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 0x7f51165a8700 (LWP 3596)]
(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)
[KCrash handler]
#5  0x00007f5115bbf28a in ?? () from /usr/lib64/libkio.so.5
#6  0x00007f5115bc2147 in ?? () from /usr/lib64/libkio.so.5
#7  0x00007f5114491274 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#8  0x00007f5114acb432 in KJob::result () from /usr/lib64/libkdecore.so.5
#9  0x00007f5114acb7a7 in KJob::emitResult () from /usr/lib64/libkdecore.so.5
#10 0x00007f5115b98980 in KIO::SimpleJob::slotFinished ()
   from /usr/lib64/libkio.so.5
#11 0x00007f5115b98ab5 in KIO::ListJob::slotFinished ()
   from /usr/lib64/libkio.so.5
#12 0x00007f5115ba04ad in KIO::ListJob::qt_metacall ()
   from /usr/lib64/libkio.so.5
#13 0x00007f5114491274 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#14 0x00007f5115c3e101 in KIO::SlaveInterface::dispatch ()
   from /usr/lib64/libkio.so.5
#15 0x00007f5115c3c022 in KIO::SlaveInterface::dispatch ()
   from /usr/lib64/libkio.so.5
#16 0x00007f5115c2f85e in KIO::Slave::gotInput () from /usr/lib64/libkio.so.5
#17 0x00007f5115c2fb68 in KIO::Slave::qt_metacall ()
   from /usr/lib64/libkio.so.5
#18 0x00007f5114491274 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#19 0x00007f5115b6d2b1 in ?? () from /usr/lib64/libkio.so.5
#20 0x00007f5115b6d95a in KIO::Connection::qt_metacall ()
   from /usr/lib64/libkio.so.5
#21 0x00007f511448bf3d in QObject::event () from /usr/lib64/libQtCore.so.4
#22 0x00007f51110f517d in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#23 0x00007f51110fcf2a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#24 0x00007f5115703dcb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#25 0x00007f511447ce71 in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#26 0x00007f511447db2a in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib64/libQtCore.so.4
#27 0x00007f51144a5713 in ?? () from /usr/lib64/libQtCore.so.4
#28 0x00007f510e1ad93a in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#29 0x00007f510e1b1040 in g_main_context_iterate ()
   from /usr/lib64/libglib-2.0.so.0
#30 0x00007f510e1b11dc in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#31 0x00007f51144a539f in QEventDispatcherGlib::processEvents ()
   from /usr/lib64/libQtCore.so.4
#32 0x00007f5111185ccf in ?? () from /usr/lib64/libQtGui.so.4
#33 0x00007f511447b772 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#34 0x00007f511447b8fd in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#35 0x00007f511447dded in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#36 0x000000000044066d in _start ()
#0  0x00007f510f5dc230 in nanosleep () from /lib64/libc.so.6
Comment 1 Dario Andres 2008-10-19 05:21:32 UTC 
Seems to be related/duplicate of bug 168050 (bug 163824)
Comment 2 Dario Andres 2009-01-08 23:23:14 UTC 
Have you experienced this bug again using a recent KDE (4.1.3 / 4.2beta2 / 4.2svn) ? Thanks :)
Comment 3 Dario Andres 2009-01-16 12:05:21 UTC 
The reporter sent me an e-mail:
---------

Dear Andres,

the Problem is fixed with Suse 11.1. Thanks

Christian