Bug 252293

Summary: Plasma crashed after choosing type of displayed files in save dialog in GIMP
Product: [Unmaintained] plasma4 Reporter: Valentin <v.babosha>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: asraniel
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Valentin 2010-09-24 23:32:24 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.3-desktop i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
Plasma crashes always after choosing type of displayed files in save dialog in GIMP and trying to save file.

The crash can be reproduced every time.

 -- Backtrace:
Application: Рабочее пространство Plasma (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  TaskManager::Task::icon (this=0x0, width=32, height=32, allowResize=true) at /usr/src/debug/kdebase-workspace-4.4.4/libs/taskmanager/task.cpp:406
#7  0xa613fb77 in daisy::windowChanged (this=0x853d1b8, id=60824094, properties=0xbfb97174) at /usr/src/debug/plasma-applet-daisy-0.0.4.23/applet/src/daisyTasks.cpp:267
#8  0xa614a260 in daisy::qt_metacall (this=0x853d1b8, _c=QMetaObject::InvokeMetaMethod, _id=63, _a=0xbfb97114) at /usr/src/debug/plasma-applet-daisy-0.0.4.23/builddir/applet/daisy.moc:239
#9  0xb6c75efd in QMetaObject::metacall (object=0x853d1b8, cl=QMetaObject::InvokeMetaMethod, idx=148, argv=0xbfb97114) at kernel/qmetaobject.cpp:237
#10 0xb6c84fe8 in QMetaObject::activate (sender=0x819e4e0, m=0xb714ab30, local_signal_index=9, argv=0xbfb97114) at kernel/qobject.cpp:3295
#11 0xb6f180ad in KWindowSystem::windowChanged (this=0x819e4e0, _t1=60824094, _t2=0xbfb97174) at /usr/src/debug/kdelibs-4.4.4/build/kdeui/kwindowsystem.moc:178
#12 0xb6ff469a in KWindowSystemPrivate::x11Event (this=0x81f7fb8, ev=0xbfb9762c) at /usr/src/debug/kdelibs-4.4.4/kdeui/windowmanagement/kwindowsystem_x11.cpp:184
#13 0xb6fbef77 in publicx11Event (this=0x80b5420, _event=0xbfb9762c) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:903
#14 KApplication::x11EventFilter (this=0x80b5420, _event=0xbfb9762c) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:953
#15 0xb1e71933 in PlasmaApp::x11EventFilter (this=0x80b5420, event=0xbfb9762c) at /usr/src/debug/kdebase-workspace-4.4.4/plasma/desktop/shell/plasmaapp.cpp:600
#16 0xb621d591 in qt_x11EventFilter (ev=0xbfb9762c) at kernel/qapplication_x11.cpp:409
#17 0xb623024f in QApplication::x11ProcessEvent (this=0x80b5420, event=0xbfb9762c) at kernel/qapplication_x11.cpp:3243
#18 0xb625a570 in x11EventSourceDispatch (s=0x80c0840, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#19 0xb58f2b49 in g_main_dispatch (context=0x80bfa90) at gmain.c:1960
#20 IA__g_main_context_dispatch (context=0x80bfa90) at gmain.c:2513
#21 0xb58f3350 in g_main_context_iterate (context=0x80bfa90, block=1, dispatch=1, self=0x80bd570) at gmain.c:2591
#22 0xb58f360e in IA__g_main_context_iteration (context=0x80bfa90, may_block=1) at gmain.c:2654
#23 0xb6c9bd4b in QEventDispatcherGlib::processEvents (this=0x80bcc70, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#24 0xb625a19a in QGuiEventDispatcherGlib::processEvents (this=0x80bcc70, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0xb6c6f11d in QEventLoop::processEvents (this=0xbfb978e4, flags=...) at kernel/qeventloop.cpp:149
#26 0xb6c6f319 in QEventLoop::exec (this=0xbfb978e4, flags=...) at kernel/qeventloop.cpp:201
#27 0xb6c73c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#28 0xb61a7164 in QApplication::exec () at kernel/qapplication.cpp:3581
#29 0xb1e6c665 in kdemain (argc=1, argv=0x80af8d8) at /usr/src/debug/kdebase-workspace-4.4.4/plasma/desktop/shell/main.cpp:112
#30 0x0804e5b1 in _start ()

Possible duplicates by query: bug 248309, bug 247673, bug 244761, bug 241067, bug 235508.

Reported using DrKonqi
Comment 1 Beat Wolf 2010-09-25 10:46:36 UTC

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