Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-14-generic i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: When I open "Desktop Settings" and chose the "Globe" wallpaper type the screen immediately goes black (even before the UI updates to show the Globe options and before I can select Apply) and then plasma restarts. The first time I chose the globe (yesterday) it worked and I could interact with its configuration UI, and it did update the desktop wallpaper. At the time I decided against using it... now I can't seem to revert this decision. This is a vanilla Kubuntu 9.04 Jaunty Jackalope updated to KDE 4.3 RC1 from the "official" PPA on Launchpad. -- Backtrace: Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault [Current thread is 0 (LWP 10021)] Thread 2 (Thread 0xa8527b90 (LWP 10035)): #0 0xb8012430 in __kernel_vsyscall () #1 0xb50d20e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb63132ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0xb64ff9b2 in QWaitCondition::wait (this=0x9682040, mutex=0x968203c, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 0xb7989152 in QHostInfoAgent::run (this=0x9682030) at kernel/qhostinfo.cpp:260 #5 0xb64fe96e in QThreadPrivate::start (arg=0x9682030) at thread/qthread_unix.cpp:189 #6 0xb50ce4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb630449e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb3ed6b70 (LWP 10021)): [KCrash Handler] #6 0x0ae83000 in ?? () #7 0xa296769c in Marble::MarbleModel::setupTextureMapper () from /usr/lib/libmarblewidget.so.4 #8 0xa296eed6 in Marble::MarbleMap::setProjection () from /usr/lib/libmarblewidget.so.4 #9 0xa2a662a7 in ?? () from /usr/lib/kde4/plasma_wallpaper_marble.so #10 0xb7e958c9 in Plasma::Wallpaper::restore (this=0x9979bf8, config=@0xbfa2f210) at /build/buildd/kde4libs-4.2.98a/plasma/wallpaper.cpp:227 #11 0xb7fa9926 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so #12 0xb7fa655c in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so #13 0xb6608ca8 in QMetaObject::activate (sender=0xa580450, from_signal_index=32, to_signal_index=32, argv=0xbfa2f33c) at kernel/qobject.cpp:3069 #14 0xb6609932 in QMetaObject::activate (sender=0xa580450, m=0xb71303d8, local_signal_index=5, argv=0xbfa2f33c) at kernel/qobject.cpp:3143 #15 0xb6c9a313 in QComboBox::currentIndexChanged (this=0xa580450, _t1=7) at .moc/release-shared/moc_qcombobox.cpp:297 #16 0xb6c9c45a in QComboBoxPrivate::_q_emitCurrentIndexChanged (this=0x97c3870, index=@0x9d76d58) at widgets/qcombobox.cpp:1205 #17 0xb6c9dd93 in QComboBoxPrivate::setCurrentIndex (this=0x97c3870, mi=@0xbfa2f560) at widgets/qcombobox.cpp:1943 #18 0xb6c9df2e in QComboBoxPrivate::_q_itemSelected (this=0x97c3870, item=@0xbfa2f560) at widgets/qcombobox.cpp:1174 #19 0xb6ca3f9e in QComboBox::qt_metacall (this=0xa580450, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfa2f51c) at .moc/release-shared/moc_qcombobox.cpp:186 #20 0xb6608ca8 in QMetaObject::activate (sender=0x9282cc8, from_signal_index=27, to_signal_index=27, argv=0xbfa2f51c) at kernel/qobject.cpp:3069 #21 0xb6609932 in QMetaObject::activate (sender=0x9282cc8, m=0xb713d5f4, local_signal_index=0, argv=0xbfa2f51c) at kernel/qobject.cpp:3143 #22 0xb6f573f3 in QComboBoxPrivateContainer::itemSelected (this=0x9282cc8, _t1=@0xbfa2f560) at .moc/release-shared/moc_qcombobox_p.cpp:198 #23 0xb6c9c229 in QComboBoxPrivateContainer::eventFilter (this=0x9282cc8, o=0x960a228, e=0xbfa2fa38) at widgets/qcombobox.cpp:667 #24 0xb65f1c5a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x8fc1048, receiver=0x960a228, event=0xbfa2fa38) at kernel/qcoreapplication.cpp:718 #25 0xb689fe7a in QApplicationPrivate::notify_helper (this=0x8fc1048, receiver=0x960a228, e=0xbfa2fa38) at kernel/qapplication.cpp:4080 #26 0xb68a8b11 in QApplication::notify (this=0x8fba788, receiver=0x960a228, e=0xbfa2fa38) at kernel/qapplication.cpp:3786 #27 0xb770a5cd in KApplication::notify (this=0x8fba788, receiver=0x960a228, event=0xbfa2fa38) at /build/buildd/kde4libs-4.2.98a/kdeui/kernel/kapplication.cpp:302 #28 0xb65f2a3b in QCoreApplication::notifyInternal (this=0x8fba788, receiver=0x960a228, event=0xbfa2fa38) at kernel/qcoreapplication.cpp:602 #29 0xb68a7b7e in QApplicationPrivate::sendMouseEvent (receiver=0x960a228, event=0xbfa2fa38, alienWidget=0x960a228, nativeWidget=0x9282cc8, buttonDown=0xb714a200, lastMouseReceiver=@0xb714a204) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #30 0xb6917c06 in QETWidget::translateMouseEvent (this=0x9282cc8, event=0xbfa3007c) at kernel/qapplication_x11.cpp:4359 #31 0xb6916ca7 in QApplication::x11ProcessEvent (this=0x8fba788, event=0xbfa3007c) at kernel/qapplication_x11.cpp:3421 #32 0xb6941c6a in x11EventSourceDispatch (s=0x8fc7b68, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #33 0xb4eccb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #34 0xb4ed00eb in ?? () from /usr/lib/libglib-2.0.so.0 #35 0xb4ed0268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #36 0xb661e438 in QEventDispatcherGlib::processEvents (this=0x8fa57f8, flags={i = -1079836104}) at kernel/qeventdispatcher_glib.cpp:323 #37 0xb6941365 in QGuiEventDispatcherGlib::processEvents (this=0x8fa57f8, flags={i = -1079836056}) at kernel/qguieventdispatcher_glib.cpp:202 #38 0xb65f106a in QEventLoop::processEvents (this=0xbfa302e0, flags={i = -1079835992}) at kernel/qeventloop.cpp:149 #39 0xb65f14aa in QEventLoop::exec (this=0xbfa302e0, flags={i = -1079835928}) at kernel/qeventloop.cpp:200 #40 0xb65f3959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #41 0xb689fd17 in QApplication::exec () at kernel/qapplication.cpp:3553 #42 0xb7fb75d0 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so #43 0x08048712 in _start () Reported using DrKonqi
After some unfortunate changes to my KDE configuration which made the login process freeze after the "disk" icon appeared during the login splash screen, I backed up my ~/.kde directory and logged in... a new ~/.kde directory was generated and all my previous configurations where reset, but this time everything seems to be working ok (regarding marble, that is).
*** Bug 215240 has been marked as a duplicate of this bug. ***
Please reopen if still happening.