Bug 177285 - Crash durring install of packages
Summary: Crash durring install of packages
Status: RESOLVED DUPLICATE of bug 165548
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-09 04:44 UTC by John
Modified: 2008-12-11 17:56 UTC (History)
2 users (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 John 2008-12-09 04:44:12 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

Application: KDE Daemon (kded4), signal SIGSEGV
(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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb623b6c0 (LWP 5783)]
(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]
#6  0xb755d2a4 in QString::operator== () from /usr/lib/libQtCore.so.4
#7  0xb7d819ed in ?? () from /usr/lib/libkio.so.5
#8  0xb7d81c9b in ?? () from /usr/lib/libkio.so.5
#9  0xb7620a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb76217e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb765b633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#12 0xb7626637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#13 0xb6b9e8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb6ba676e in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb7ada72d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb760be61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb763670a in ?? () from /usr/lib/libQtCore.so.4
#18 0xb65cd6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb65d0da3 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb65d0f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb7636478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#22 0xb6c38ee5 in ?? () from /usr/lib/libQtGui.so.4
#23 0xb760a52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#24 0xb760a6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#25 0xb760cda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#26 0xb6b9e767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#27 0xb805c0a6 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#28 0x080485a2 in _start ()
#0  0xb808d430 in __kernel_vsyscall ()
Comment 1 FiNeX 2008-12-09 11:39:54 UTC
Did you use adept?
Comment 2 Jonathan Thomas 2008-12-11 17:56:35 UTC

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