Bug 220438 - krandrtray launching from systemsettings or tray icon
Summary: krandrtray launching from systemsettings or tray icon
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-28 20:01 UTC by droptheleash
Modified: 2009-12-28 20:05 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 droptheleash 2009-12-28 20:01:50 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-default i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:
KDE 4.3.4 - OPensuse 11.2
I try to open Screen options from 'Personal settings' and it crashes the whole systemsettings window.
If I start the application (krandtray) it shows the tray icon, but it crashes again when trying to double click it

 -- Backtrace:
Application: Preferencias del sistema (systemsettings), signal: Segmentation fault
[KCrash Handler]
#6  0xb721ff18 in QGraphicsScene::addItem(QGraphicsItem*) () from /usr/lib/libQtGui.so.4
#7  0xb35c04e6 in RandRConfig::load (this=0x82b1818) at /usr/src/debug/kdebase-workspace-4.3.4/kcontrol/randr/randrconfig.cpp:101
#8  0xb35ab53b in KRandRModule::load (this=0x8251a78) at /usr/src/debug/kdebase-workspace-4.3.4/kcontrol/randr/krandrmodule.cpp:109
#9  0xb76f078f in KCModule::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdeui.so.5
#10 0xb35aaf33 in KRandRModule::qt_metacall (this=0x8251a78, _c=InvokeMetaMethod, _id=29, _a=0x82a9460) at /usr/src/debug/kdebase-workspace-4.3.4/build/kcontrol/randr/krandrmodule.moc:58
#11 0xb66fb04a in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#12 0xb66fc796 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#13 0xb6c49230 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#14 0xb6bf28fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb6bfa29e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb7631451 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#17 0xb66ec32e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#18 0xb66ecfdc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#19 0xb66ed19c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#20 0xb67184dd in ?? () from /usr/lib/libQtCore.so.4
#21 0xb5b764c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb5b79d98 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb5b79ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb6718011 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0xb6c9429a in ?? () from /usr/lib/libQtGui.so.4
#26 0xb66ea98d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb66eadd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0xb66ed270 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#29 0xb6bf2774 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#30 0x0805320e in main (argc=5, argv=0xbfc276a4) 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 220158

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-28 20:05:46 UTC
This is being tracked at bug 217935. Thanks

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