Bug 218283 - I tried to start the displaymanager from system stettings. It crashes immediately.
Summary: I tried to start the displaymanager from system stettings. It crashes immedia...
Status: RESOLVED DUPLICATE of bug 217935
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: System Settings Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-11 15:30 UTC by Oliver Zimmermann
Modified: 2009-12-11 16:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Zimmermann 2009-12-11 15:30:55 UTC
Application that crashed: systemsettings
Version of the application: 1.0
KDE Version: 4.3.4 (KDE 4.3.4) "release 2"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.5-0.1-desktop i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:
Calling the displaymanager of system settings crashes. I have KDE 4.3.4 from the stable repository installed.

 -- Backtrace:
Application: Systemeinstellungen (systemsettings), signal: Segmentation fault
[KCrash Handler]
#6  0xb71ae9d7 in QGraphicsItem::scene() const () from /usr/lib/libQtGui.so.4
#7  0xb71ddeda in QGraphicsScene::addItem(QGraphicsItem*) () from /usr/lib/libQtGui.so.4
#8  0xb31904e6 in RandRConfig::load (this=0x82197b8) at /usr/src/debug/kdebase-workspace-4.3.4/kcontrol/randr/randrconfig.cpp:101
#9  0xb317b53b in KRandRModule::load (this=0x826b848) at /usr/src/debug/kdebase-workspace-4.3.4/kcontrol/randr/krandrmodule.cpp:109
#10 0xb76ae78f in KCModule::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdeui.so.5
#11 0xb317af33 in KRandRModule::qt_metacall (this=0x826b848, _c=InvokeMetaMethod, _id=29, _a=0x827d008) at /usr/src/debug/kdebase-workspace-4.3.4/build/kcontrol/randr/krandrmodule.moc:58
#12 0xb66b904a in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#13 0xb66ba796 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb6c07230 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb6bb08fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb6bb829e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb75ef451 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#18 0xb66aa32e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#19 0xb66aafdc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#20 0xb66ab19c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#21 0xb66d64dd in ?? () from /usr/lib/libQtCore.so.4
#22 0xb5b344c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb5b37d98 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb5b37ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb66d6011 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0xb6c5229a in ?? () from /usr/lib/libQtGui.so.4
#27 0xb66a898d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0xb66a8dd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0xb66ab270 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#30 0xb6bb0774 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#31 0x0805320e in main (argc=5, argv=0xbff20044) at /usr/src/debug/kdebase-workspace-4.3.4/systemsettings/app/main.cpp:51

This bug may be a duplicate of or related to bug 217935

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-11 16:20:42 UTC
Sorry, my fault. It is fixed on KDE SC 4.4.

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