Summary: | plasma crashed when I was doing nothing | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | Miguel Tadeu <mtadeunet> |
Component: | widget-taskbar | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | aseigo |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Miguel Tadeu
2009-05-31 21:52:58 UTC
something very odd happens here: #6 TaskManager::Task::window (this=0xa060ad8) at /build/buildd/kdebase-workspace-4.2.85/libs/taskmanager/task.cpp:356 #7 0xb6618f0f in QObject::event (this=0xa060ad8, e=0x0) at kernel/qobject.cpp:1082 #8 0xb6f1c257 in QGraphicsWidget::event (this=0xa060ad8, event=0xbf92981c) at graphicsview/qgraphicswidget.cpp:1340 first off, qgraphicswidget.cpp:1340 is a call to QObject::event(event), though in the call event is now a null pointer (!) and then that results in a call to TaskManager::Task::window which is not in any way related to or callable from QObject::event. does this happen on every log in? what widgets are you using? That looks like the classic epic fail of the taskbar widget as seen in 4.3beta1. Marking as duplicate, as the possibility looks quite high. In case it would be not (and you can still reproduce the problem with more recent versions), feel free to reopen. *** This bug has been marked as a duplicate of bug 191412 *** |