Bug 195989 - Plasma workspace crashed after raising kde notification
Summary: Plasma workspace crashed after raising kde notification
Status: RESOLVED DUPLICATE of bug 176014
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 11:03 UTC by Eduard Kracmar
Modified: 2009-06-23 02:36 UTC (History)
5 users (show)

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


Attachments
broken notification painting after crash (243.88 KB, image/png)
2009-06-11 14:55 UTC, Eduard Kracmar
Details
main plasma panel right after the crash (90.79 KB, image/png)
2009-06-11 15:40 UTC, Eduard Kracmar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eduard Kracmar 2009-06-11 11:03:41 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.1
Operating System: Linux 2.6.28-11-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
After systray notification raising plasma crashed. I don't know which application raised notification because after crash every plasma frame loses text a icons but a assume it's kopete. 

 -- Backtrace:
Application: Plasma Workspace (kdeinit), signal: Segmentation fault
[Current thread is 0 (LWP 5715)]

Thread 2 (Thread 0x7faaee3f8950 (LWP 5720)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007fab0f38cce9 in QWaitCondition::wait (this=0x225dee0, mutex=0x225ded8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007fab0e2185dc in QHostInfoAgent::run (this=0x225dec0) at kernel/qhostinfo.cpp:260
#3  0x00007fab0f38bd02 in QThreadPrivate::start (arg=0x225dec0) at thread/qthread_unix.cpp:189
#4  0x00007fab0b25c3ba in start_thread (arg=<value optimized out>) at pthread_create.c:297
#5  0x00007fab0be40fcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fab0f94c750 (LWP 5715)):
[KCrash Handler]
#5  0x0000000000000000 in ?? ()
#6  0x00007fab0cbc0e14 in blend_src_generic<RegularSpans> (count=98, spans=0x7fff17986d30, userData=<value optimized out>) at painting/qdrawhelper.cpp:3389
#7  0x00007fab0cbc19be in blend_transformed_tiled_argb<RegularSpans> (count=395840272, spans=0x7fff17984b10, userData=0x4761390) at painting/qdrawhelper.cpp:6344
#8  0x00007fab0cb7b37f in QRasterizer::rasterize (this=0x40c97c0, path=@0x7fff17987680, fillRule=<value optimized out>) at painting/qrasterizer.cpp:105
#9  0x00007fab0cba245a in QRasterPaintEngine::fillPath (this=0x48dd320, path=@0x7fff17987c70, fillData=0x4761390) at painting/qpaintengine_raster.cpp:1362
#10 0x00007fab0cbacf41 in QRasterPaintEngine::drawPath (this=0x48dd320, path=@0x7fff17987c70) at painting/qpaintengine_raster.cpp:1897
#11 0x00007fab0cb38b6d in QPainterPrivate::draw_helper (this=0x49aad60, originalPath=@0x7fff17987c70, op=<value optimized out>) at painting/qpainter.cpp:451
#12 0x00007fab0cb3bb17 in QPainter::drawRects (this=<value optimized out>, rects=<value optimized out>, rectCount=1) at painting/qpainter.cpp:3334
#13 0x00007fab0cb3dc6e in QPainter::drawPixmap (this=0x7fff17987f10, r=<value optimized out>, pm=@0x24ceaa8, sr=<value optimized out>) at ../../include/QtGui/../../src/gui/painting/qpainter.h:604
#14 0x00007fab06db8595 in Plasma::FrameSvg::paintFrame (this=0x23c62b0, painter=0x7fff17987f10, target=@0x7fff17987ef0, source=@0x7fff17987ed0)
    at /build/buildd/kde4libs-4.2.90/plasma/framesvg.cpp:370
#15 0x00007fab06da2f1e in Plasma::Dialog::paintEvent (this=0x205dc40, e=<value optimized out>) at /build/buildd/kde4libs-4.2.90/plasma/dialog.cpp:292
#16 0x00007fab0ca68c06 in QWidget::event (this=0x205dc40, event=0x7fff17988610) at kernel/qwidget.cpp:7659
#17 0x00007fab06da2c80 in Plasma::Dialog::event (this=0x205dc40, event=0x7fff17988610) at /build/buildd/kde4libs-4.2.90/plasma/dialog.cpp:396
#18 0x00007fab0ca17b9d in QApplicationPrivate::notify_helper (this=0x1b969e0, receiver=0x205dc40, e=0x7fff17988610) at kernel/qapplication.cpp:4057
#19 0x00007fab0ca1fdea in QApplication::notify (this=0x1b559d0, receiver=0x205dc40, e=0x7fff17988610) at kernel/qapplication.cpp:4022
#20 0x00007fab0db5406b in KApplication::notify (this=0x1b559d0, receiver=0x205dc40, event=0x7fff17988610) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302
#21 0x00007fab0f474dfc in QCoreApplication::notifyInternal (this=0x1b559d0, receiver=0x205dc40, event=0x7fff17988610) at kernel/qcoreapplication.cpp:610
#22 0x00007fab0ca6fe55 in QWidgetPrivate::drawWidget (this=0x23c5fd0, pdev=0x2052988, rgn=@0x7fff179889a0, offset=@0x23e8f54, flags=5, sharedPainter=0x0, backingStore=0x23e8f10)
    at kernel/qwidget.cpp:5052
#23 0x00007fab0cc15622 in QWidgetBackingStore::sync (this=0x23e8f10) at painting/qbackingstore.cpp:1268
#24 0x00007fab0ca61510 in QWidgetPrivate::syncBackingStore (this=0x23c5fd0) at kernel/qwidget.cpp:1602
#25 0x00007fab0ca68a9d in QWidget::event (this=0x205dc40, event=0x4bb0180) at kernel/qwidget.cpp:7799
#26 0x00007fab06da2c80 in Plasma::Dialog::event (this=0x205dc40, event=0x4bb0180) at /build/buildd/kde4libs-4.2.90/plasma/dialog.cpp:396
#27 0x00007fab0ca17b9d in QApplicationPrivate::notify_helper (this=0x1b969e0, receiver=0x205dc40, e=0x4bb0180) at kernel/qapplication.cpp:4057
#28 0x00007fab0ca1fdea in QApplication::notify (this=0x1b559d0, receiver=0x205dc40, e=0x4bb0180) at kernel/qapplication.cpp:4022
#29 0x00007fab0db5406b in KApplication::notify (this=0x1b559d0, receiver=0x205dc40, event=0x4bb0180) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302
#30 0x00007fab0f474dfc in QCoreApplication::notifyInternal (this=0x1b559d0, receiver=0x205dc40, event=0x4bb0180) at kernel/qcoreapplication.cpp:610
#31 0x00007fab0f475a6a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1b03100) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#32 0x00007fab0f49e8a3 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#33 0x00007fab0b4ab20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0x00007fab0b4ae8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#35 0x00007fab0b4aea7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0x00007fab0f49e52f in QEventDispatcherGlib::processEvents (this=0x1b95e70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#37 0x00007fab0cab070f in QGuiEventDispatcherGlib::processEvents (this=0x7fff17980b10, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#38 0x00007fab0f4736a2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 395875472}) at kernel/qeventloop.cpp:149
#39 0x00007fab0f473a6d in QEventLoop::exec (this=0x7fff179894d0, flags={i = 395875552}) at kernel/qeventloop.cpp:200
#40 0x00007fab0f475d34 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#41 0x00007fab032bc7eb in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#42 0x000000000040714e in launch (argc=1, _name=0x1b62a28 "/usr/bin/plasma-desktop", args=<value optimized out>, cwd=0x0, envc=0, envs=0x1b62a48 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x40a308 "0") at /build/buildd/kde4libs-4.2.90/kinit/kinit.cpp:671
#43 0x0000000000407978 in handle_launcher_request (sock=7, who=<value optimized out>) at /build/buildd/kde4libs-4.2.90/kinit/kinit.cpp:1163
#44 0x0000000000407f25 in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.90/kinit/kinit.cpp:1356
#45 0x0000000000408a66 in main (argc=2, argv=0x7fff1798a368, envp=0x7fff1798a380) at /build/buildd/kde4libs-4.2.90/kinit/kinit.cpp:1783

Reported using DrKonqi
Comment 1 Marco Martin 2009-06-11 12:29:29 UTC
looks like an upstream bug in the Qt raster paint engine
can you deterministically reproduce the crash?
if so, try if you can also when running plasma from the console with the command plasma-desktop -graphicssystem x11
Comment 2 Dario Andres 2009-06-11 14:39:55 UTC
May be related to bug 176014. Thanks
Comment 3 Eduard Kracmar 2009-06-11 14:46:01 UTC
I can't reproduce bug, it happens while using within one to five times within 8 hours. And it looks like it's not only with kopete notification, because my office box is staying on through the night, I'm locking session and kopete is turned off.

I can try to start plasma from konsole as you suggested.
Comment 4 Eduard Kracmar 2009-06-11 14:55:32 UTC
Created attachment 34435 [details]
broken notification painting after crash

Don't know if related to crash, but this happens a lot.
Comment 5 Artur Souza (MoRpHeUz) 2009-06-11 15:20:42 UTC
It really seems a bug with the raster engine. Adding Alexis to CC. The test with the other graphicssystem (x11) will really help.
Comment 6 Eduard Kracmar 2009-06-11 15:40:04 UTC
Created attachment 34437 [details]
main plasma panel right after the crash
Comment 7 Eduard Kracmar 2009-06-11 15:42:52 UTC
Added screenshot from panel right after the crash. Missing names of tasks in task manager widget and clock on right side. I should also mention that I'm running dualhead Xorg configuration. I'm also on same configuration at home, but no dualhead there and I don't have any problems.
Comment 8 Eduard Kracmar 2009-06-11 15:45:28 UTC
output of plasma-destop after running from shell:


kraken@thingol ~ $ plasma-desktop -graphicssystem x11
Unable to load graphicssystem "x11"                  
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
"KConfigIni: In file /usr/share/kubuntu-default-settings/kde4-profile/default/share/config/kickoffrc, line 3: " Invalid entry (missing '=') 
findServiceByDesktopPath: systemsettings not found                                                                                          
findServiceByDesktopPath: kde4-audex.desktop not found                                                                                      
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/plasma02.png[2].desktop not found                                    
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/plasma02.png.desktop not found                                       
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/show_bug.cgi.desktop not found                                       
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/plast.htm.desktop not found                                          
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/bilancia.ods.desktop not found                                       
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/sykoru-vyradilo-zranenie-dostane-satan-sancu.html.desktop not found  
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/ignoracia-dokazov-pokracuje-pozrite-si-ako-to-ficov-hovorca-vysvetluje.html.desktop not found                                                                                                                                                    
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/321.desktop not found                                                                
findServiceByDesktopPath: /home/kraken/.kde/share/apps/RecentDocuments/music.desktop not found                                                              
Object::connect: No such slot TaskManager::TaskManager::configureStartup()                                                                                  
Object::connect:  (sender name:   'KDirWatch-4')                                                                                                            
Object::connect: No such slot TaskManager::TaskManager::configureStartup()                                                                                  
Object::connect:  (sender name:   'KDirWatch-4')
Object::connect: No such slot TaskManager::TaskManager::configureStartup()
Object::connect:  (sender name:   'KDirWatch-4')
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 1
Comment 9 Alexis MENARD 2009-06-11 17:38:48 UTC
mmm not sure it is a bug in Qt, is there any way to reproduce that thing? It might be related to the leak because i have seen that Qt crashes when it was not able to allocate data. Perhaps a clip problem otherwise or the pixmap is corrupted. But without a way to reproduce i don't know how i can help....
Comment 10 Aaron J. Seigo 2009-06-23 02:36:09 UTC

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