Bug 162635 - dolphin crashed while scanning network for smb resources
Summary: dolphin crashed while scanning network for smb resources
Status: RESOLVED DUPLICATE of bug 162285
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-26 08:57 UTC by Oliver Putz
Modified: 2008-05-26 12:41 UTC (History)
0 users

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 Oliver Putz 2008-05-26 08:57:38 UTC
Version:            (using Devel)
Installed from:    Compiled sources
OS:                Linux

Setup: 

I ran a recent KDE4 SVN snapshot via a liveCD (http://grundleborg.wordpress.com/2008/05/25/kde-pim-krush-day-is-now/) in a virtual machine. After I experienced bug #162634 (a Plasma crash) I tried to save the backtraces. Therefore I opened dolphin and clicked on "Networks". After that, dolphin crashed with the following backtrace:

Application: Dolphin (dolphin), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb5d92940 (LWP 4801)]
[KCrash handler]
#6  0x091cbf2c in ?? ()
#7  0xb76f4c06 in qDeleteAll<QList<KJob*>::const_iterator> ()
   from /opt/kde4/lib/libkdecore.so.5
#8  0xb76f4c6c in qDeleteAll<QList<KJob*> > ()
   from /opt/kde4/lib/libkdecore.so.5
#9  0xb76f48c2 in KCompositeJobPrivate::~KCompositeJobPrivate ()
   from /opt/kde4/lib/libkdecore.so.5
#10 0xb7d770ee in KIO::JobPrivate::~JobPrivate ()
   from /opt/kde4/lib/libkio.so.5
#11 0xb7db3dcc in KIO::FileCopyJobPrivate::~FileCopyJobPrivate ()
   from /opt/kde4/lib/libkio.so.5
#12 0xb76f670a in KJob::~KJob () from /opt/kde4/lib/libkdecore.so.5
#13 0xb76f4735 in KCompositeJob::~KCompositeJob ()
   from /opt/kde4/lib/libkdecore.so.5
#14 0xb7dac011 in KIO::Job::~Job () from /opt/kde4/lib/libkio.so.5
#15 0xb7dac057 in KIO::FileCopyJob::~FileCopyJob ()
   from /opt/kde4/lib/libkio.so.5
#16 0xb74b9ee1 in qDeleteInEventHandler (o=0x91f54b8)
    at /usr/src/KDE/source/qt-copy/src/corelib/kernel/qobject.cpp:3586
#17 0xb74be9b4 in QObject::event (this=0x91f54b8, e=0x91c0398)
    at /usr/src/KDE/source/qt-copy/src/corelib/kernel/qobject.cpp:1115
#18 0xb65ec261 in QApplicationPrivate::notify_helper (this=0x8e53488, 
    receiver=0x91f54b8, e=0x91c0398)
    at /usr/src/KDE/source/qt-copy/src/gui/kernel/qapplication.cpp:3772
#19 0xb65ec57a in QApplication::notify (this=0xbf9d37e0, receiver=0x91f54b8, 
    e=0x91c0398)
    at /usr/src/KDE/source/qt-copy/src/gui/kernel/qapplication.cpp:3366
#20 0xb7b7075b in KApplication::notify () from /opt/kde4/lib/libkdeui.so.5
#21 0xb74a90e9 in QCoreApplication::notifyInternal (this=0xbf9d37e0, 
    receiver=0x91f54b8, event=0x91c0398)
    at /usr/src/KDE/source/qt-copy/src/corelib/kernel/qcoreapplication.cpp:587
#22 0xb74ad71f in QCoreApplication::sendEvent (receiver=0x91f54b8, 
    event=0x91c0398)
    at ../../include/QtCore/../../../../source/qt-copy/src/corelib/kernel/qcoreapplication.h:215
#23 0xb74a968a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, 
    event_type=0, data=0x8e42cc0)
    at /usr/src/KDE/source/qt-copy/src/corelib/kernel/qcoreapplication.cpp:1198
#24 0xb74a98ff in QCoreApplication::sendPostedEvents (receiver=0x0, 
    event_type=0)
    at /usr/src/KDE/source/qt-copy/src/corelib/kernel/qcoreapplication.cpp:1091
#25 0xb74e010e in QCoreApplication::sendPostedEvents ()
    at ../../include/QtCore/../../../../source/qt-copy/src/corelib/kernel/qcoreapplication.h:220
#26 0xb74df2fb in postEventSourceDispatch (s=0x8e55180)
    at /usr/src/KDE/source/qt-copy/src/corelib/kernel/qeventdispatcher_glib.cpp:211
#27 0xb5f8e978 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0xb5f91bce in ?? () from /usr/lib/libglib-2.0.so.0
#29 0x08e550f8 in ?? ()
#30 0x00000000 in ?? ()
#0  0xb7fb7422 in __kernel_vsyscall ()

Remark: I tried to reproduce the bug, but the next dolphin session just showed me that there are no computers I can connect to (without crashing)
Comment 1 Jakub Stachowski 2008-05-26 09:54:21 UTC
Backtrace looks the same as in bug #162285
Comment 2 Oliver Putz 2008-05-26 12:41:04 UTC
Hm, true. Apparently I ran a somewhat too specific query when I checked if this bug is already known. As the description matches too, I'll mark this one as a duplicate.

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