Bug 257656 - Crash sometimes happens when I activate the TV-out.
Summary: Crash sometimes happens when I activate the TV-out.
Status: RESOLVED DUPLICATE of bug 201620
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-23 00:39 UTC by Rafael
Modified: 2010-11-24 11:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael 2010-11-23 00:39:07 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.5.3 (KDE 4.5.3) "release 8"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.5-desktop i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
I just activated the TV-out on Systemsettings -> Monitor.

- Custom settings of the application:
Plasmoids in use: Desktop folder, moon, and pastebin.
This happens activating the Tv-out of an Intel 965 graphics card, working under the 2.9.1 xorg-x11-driver-intel  free driver.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#7  QWidget::mapToParent (this=0x0, pos=...) at kernel/qwidget.cpp:4021
#8  0xb6512e74 in QWidget::mapTo (this=0x8da5df0, parent=0x8226960, pos=...) at kernel/qwidget.cpp:3977
#9  0xab433d4e in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#10 0xab43419e in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#11 0xb6f98efd in QMetaObject::metacall (object=0x8155e28, cl=QMetaObject::InvokeMetaMethod, idx=4, argv=0xbfcebacc) at kernel/qmetaobject.cpp:237
#12 0xb6fa7fe8 in QMetaObject::activate (sender=0x8635544, m=0xb70af5a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#13 0xb6ff4a35 in QTimer::timeout (this=0x8635544) at .moc/release-shared/moc_qtimer.cpp:134
#14 0xb6fad8e6 in QTimer::timerEvent (this=0x8635544, e=0xbfcec000) at kernel/qtimer.cpp:271
#15 0xb6fa5774 in QObject::event (this=0x8635544, e=0xbfcec000) at kernel/qobject.cpp:1212
#16 0xb64cbc64 in QApplicationPrivate::notify_helper (this=0x80a5318, receiver=0x8635544, e=0xbfcec000) at kernel/qapplication.cpp:4302
#17 0xb64d3bf7 in QApplication::notify (this=0x809c3d8, receiver=0x8635544, e=0xbfcec000) at kernel/qapplication.cpp:3706
#18 0xb75b0941 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0xb6f92e0e in QCoreApplication::notifyInternal (this=0x809c3d8, receiver=0x8635544, event=0xbfcec000) at kernel/qcoreapplication.cpp:726
#20 0xb6fc170e in sendEvent (this=0x80a8434) at kernel/qcoreapplication.h:215
#21 QTimerInfoList::activateTimers (this=0x80a8434) at kernel/qeventdispatcher_unix.cpp:618
#22 0xb6fbe642 in timerSourceDispatch (source=0x80a8400) at kernel/qeventdispatcher_glib.cpp:184
#23 0xb5d19b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5d1a350 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5d1a60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb6fbed4b in QEventDispatcherGlib::processEvents (this=0x80a4ed8, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#27 0xb657c19a in QGuiEventDispatcherGlib::processEvents (this=0x80a4ed8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0xb6f9211d in QEventLoop::processEvents (this=0xbfcec2c4, flags=...) at kernel/qeventloop.cpp:149
#29 0xb6f92319 in QEventLoop::exec (this=0xbfcec2c4, flags=...) at kernel/qeventloop.cpp:201
#30 0xb6f96c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#31 0xb64c9164 in QApplication::exec () at kernel/qapplication.cpp:3581
#32 0xb2ea562a in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#33 0x0804e3f1 in _start ()

Possible duplicates by query: bug 257052, bug 256388, bug 256203, bug 256087, bug 252823.

Reported using DrKonqi
Comment 1 Beat Wolf 2010-11-24 11:53:21 UTC

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