Bug 245192

Summary: kde crashed after dual monitor conection(ati) and plasmoid config
Product: [Applications] marble Reporter: herbert <javafreak>
Component: plasmoidAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, matsatzpolatsss
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description herbert 2010-07-20 01:55:25 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.34-12-desktop i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
configured some plasmoids at last startrek-com-logo, but kde did not look well after i tried to manage the two screens(lcd monitor and lcd tv) in differend solutions with an ati hd 3400 series - may be the problem would be solved when i install ati propriet drivers - i use open suse 11.3 - now, when i tried to configure startrek logo, the kde got frozen and at restart it remained black till now, since gnome is still starting

 -- Backtrace:
Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb54dd710 (LWP 3092))]

Thread 2 (Thread 0xa6799b70 (LWP 3198)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb6ad5125 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb3266fa7 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0xb334e1a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2304
#3  0xb3266fef in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0xb334e1a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1438
#4  0xb6ad0b25 in start_thread () from /lib/libpthread.so.0
#5  0xb5ebd46e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb54dd710 (LWP 3092)):
[KCrash Handler]
#6  ref (this=0x84cb17c, other=@0x9ff02004) at ../../src/corelib/arch/qatomic_i386.h:120
#7  QString::operator= (this=0x84cb17c, other=@0x9ff02004) at tools/qstring.cpp:1280
#8  0xa77b874b in Marble::WorldClock::init (this=0x84cb130) at /usr/src/debug/kdeedu-4.4.4/marble/src/plasmoid/worldclock.cpp:119
#9  0xb51b3211 in Plasma::Corona::loadLayout (this=0x8148980, configName=...) at /usr/src/debug/kdelibs-4.4.4/plasma/corona.cpp:421
#10 0xb51b3e54 in Plasma::Corona::initializeLayout (this=0x8148980, configName=...) at /usr/src/debug/kdelibs-4.4.4/plasma/corona.cpp:337
#11 0xb33c6fcb in PlasmaApp::corona (this=0x8097318) at /usr/src/debug/kdebase-workspace-4.4.4/plasma/desktop/shell/plasmaapp.cpp:684
#12 0xb33c7330 in PlasmaApp::setupDesktop (this=0x8097318) at /usr/src/debug/kdebase-workspace-4.4.4/plasma/desktop/shell/plasmaapp.cpp:276
#13 0xb33d277d in PlasmaApp::qt_metacall (this=0x8097318, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbff67b1c)
    at /usr/src/debug/kdebase-workspace-4.4.4/build/plasma/desktop/shell/plasmaapp.moc:141
#14 0xb6c49efd in QMetaObject::metacall (object=0x8097318, cl=QMetaObject::InvokeMetaMethod, idx=39, argv=0xbff67b1c) at kernel/qmetaobject.cpp:237
#15 0xb6c58fe8 in QMetaObject::activate (sender=0x81323b0, m=0xb6d5f188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#16 0xb6c5e9d5 in QSingleShotTimer::timeout (this=0x81323b0) at .moc/release-shared/qtimer.moc:82
#17 0xb6c5ea8c in QSingleShotTimer::timerEvent (this=0x81323b0) at kernel/qtimer.cpp:308
#18 0xb6c56774 in QObject::event (this=0x81323b0, e=0xbff68050) at kernel/qobject.cpp:1212
#19 0xb617dc64 in QApplicationPrivate::notify_helper (this=0x809f730, receiver=0x81323b0, e=0xbff68050) at kernel/qapplication.cpp:4302
#20 0xb6185bf7 in QApplication::notify (this=0x8097318, receiver=0x81323b0, e=0xbff68050) at kernel/qapplication.cpp:3706
#21 0xb6e879d1 in KApplication::notify (this=0x8097318, receiver=0x81323b0, event=0xbff68050) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302
#22 0xb6c43e0e in QCoreApplication::notifyInternal (this=0x8097318, receiver=0x81323b0, event=0xbff68050) at kernel/qcoreapplication.cpp:726
#23 0xb6c7270e in sendEvent (this=0x80a18f4) at kernel/qcoreapplication.h:215
#24 QTimerInfoList::activateTimers (this=0x80a18f4) at kernel/qeventdispatcher_unix.cpp:618
#25 0xb6c6f642 in timerSourceDispatch (source=0x80a18c0) at kernel/qeventdispatcher_glib.cpp:184
#26 0xb58c6b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb58c7350 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb58c760e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb6c6fd4b in QEventDispatcherGlib::processEvents (this=0x809cca8, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#30 0xb622e19a in QGuiEventDispatcherGlib::processEvents (this=0x809cca8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0xb6c4311d in QEventLoop::processEvents (this=0xbff68314, flags=...) at kernel/qeventloop.cpp:149
#32 0xb6c43319 in QEventLoop::exec (this=0xbff68314, flags=...) at kernel/qeventloop.cpp:201
#33 0xb6c47c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#34 0xb617b164 in QApplication::exec () at kernel/qapplication.cpp:3581
#35 0xb33be665 in kdemain (argc=1, argv=0x80938c0) at /usr/src/debug/kdebase-workspace-4.4.4/plasma/desktop/shell/main.cpp:112
#36 0x0804e5b1 in _start ()

Reported using DrKonqi
Comment 1 Dennis Nienhüser 2010-08-08 20:07:23 UTC
*** Bug 246742 has been marked as a duplicate of this bug. ***
Comment 2 Dario Andres 2010-11-15 20:57:20 UTC
[Comment from a bug triager]
The plasma crash is related to the Word Clock widget. Merging with bug 248200. Thanks

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