Bug 289148

Summary: Crash of plasma after KDE starts
Product: [Plasma] krunner Reporter: kdeBugs <kde>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kdeBugs@suykerbuyk.org 2011-12-16 22:28:40 UTC
Application: krunner (0.1)
KDE Platform Version: 4.6.5 (4.6.5) "release 7"
Qt Version: 4.7.4
Operating System: Linux 2.6.37.6-0.9-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Just starting KDE - worked fine yesterday.  I never make it to the desktop.

The crash can be reproduced every time.

-- Backtrace:
Application: Run Command Interface (kdeinit4), signal: Bus error
[Current thread is 1 (Thread 0x7fd73270b760 (LWP 6932))]

Thread 2 (Thread 0x7fd719301700 (LWP 6933)):
#0  0x00007fd72fe034f3 in poll () from /lib64/libc.so.6
#1  0x00007fd72cc3a114 in ?? () from /lib64/libglib-2.0.so.0
#2  0x00007fd72cc3a650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007fd731401636 in QEventDispatcherGlib::processEvents (this=0x752410, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007fd7313d5c22 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fd7313d5e35 in QEventLoop::exec (this=0x7fd719300de0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fd7312eabe4 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:498
#7  0x00007fd7313b7358 in QInotifyFileSystemWatcherEngine::run (this=0x722090) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fd7312ed4d5 in QThreadPrivate::start (arg=0x722090) at thread/qthread_unix.cpp:331
#9  0x00007fd73105ca3f in start_thread () from /lib64/libpthread.so.0
#10 0x00007fd72fe0c66d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fd73270b760 (LWP 6932)):
[KCrash Handler]
#6  0x00007fd73186a2f7 in findNamedEntry (this=0x7995f0, key=<value optimized out>, destination=0x7fffeba1f560) at /usr/src/debug/kdelibs-4.6.5/kdecore/util/kshareddatacache.cpp:687
#7  KSharedDataCache::find (this=0x7995f0, key=<value optimized out>, destination=0x7fffeba1f560) at /usr/src/debug/kdelibs-4.6.5/kdecore/util/kshareddatacache.cpp:1469
#8  0x00007fd7321b0c7f in KImageCache::findPixmap (this=0x7995f0, key=..., destination=0x7fffeba1f5c0) at /usr/src/debug/kdelibs-4.6.5/kdeui/util/kimagecache.cpp:150
#9  0x00007fd7281862f3 in Plasma::Theme::findInCache (this=0x75ef50, key=..., pix=...) at /usr/src/debug/kdelibs-4.6.5/plasma/theme.cpp:906
#10 0x00007fd728182931 in Plasma::SvgPrivate::findInCache (this=0x75eaa0, elementId=<value optimized out>, s=<value optimized out>) at /usr/src/debug/kdelibs-4.6.5/plasma/svg.cpp:339
#11 0x00007fd7281830aa in Plasma::Svg::pixmap (this=0x7e4820, elementID=<value optimized out>) at /usr/src/debug/kdelibs-4.6.5/plasma/svg.cpp:651
#12 0x00007fd720690e08 in Interface::themeUpdated (this=0x7e4fe0) at /usr/src/debug/kdebase-workspace-4.6.5/krunner/interfaces/default/interface.cpp:334
#13 0x00007fd720692783 in Interface::Interface (this=0x7e4fe0, runnerManager=0x72f8e0, parent=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.5/krunner/interfaces/default/interface.cpp:168
#14 0x00007fd72068f324 in KRunnerApp::initialize (this=0x6a8f30) at /usr/src/debug/kdebase-workspace-4.6.5/krunner/krunnerapp.cpp:168
#15 0x00007fd72068fb33 in KRunnerApp::KRunnerApp (this=0x6a8f30) at /usr/src/debug/kdebase-workspace-4.6.5/krunner/krunnerapp.cpp:79
#16 0x00007fd72068fb85 in KRunnerApp::self () at /usr/src/debug/kdebase-workspace-4.6.5/krunner/krunnerapp.cpp:66
#17 0x00007fd720690285 in kdemain (argc=1, argv=0x692bd0) at /usr/src/debug/kdebase-workspace-4.6.5/krunner/main.cpp:62
#18 0x00000000004075c9 in _start ()

Possible duplicates by query: bug 270915.

Reported using DrKonqi
Comment 1 Aaron J. Seigo 2011-12-17 17:00:04 UTC

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