Bug 193176 - Plasma Crash when changing wallpaper
Summary: Plasma Crash when changing wallpaper
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 192693 196136 200737 207467 211823 212716 222123 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-05-19 01:58 UTC by Alexander Shenoy
Modified: 2012-05-28 22:26 UTC (History)
10 users (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 Alexander Shenoy 2009-05-19 01:58:29 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.28-12-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
To recreate the crash: Just open the Desktop Settings dialog and then click the Browse button to browse for wallpaper on your hard drive. Plasma hangs and after a few minutes you have to close the dialog. The browse dialog never shows up. Even after closing, plasma is still not responsive. After a few minutes, I used kquitapp to quit plasma, and thats when the crash notification came up.

I am running this on Kubuntu 9.04 with KDE 4.3 Beta1. 

 -- Backtrace:
Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[Current thread is 0 (LWP 3619)]

Thread 4 (Thread 0xa7d21b90 (LWP 3627)):
#0  0xb7fe7430 in __kernel_vsyscall ()
#1  0xb50b80e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb63082ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb64ec5b2 in QWaitCondition::wait (this=0x9b7d968, mutex=0x9b7d964, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb794aae2 in QHostInfoAgent::run (this=0x9b7d958) at kernel/qhostinfo.cpp:260
#5  0xb64eb56e in QThreadPrivate::start (arg=0x9b7d958) at thread/qthread_unix.cpp:189
#6  0xb50b44ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb62f949e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread 0xa3bb5b90 (LWP 3628)):
#0  0xb4e6e0ac in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0xb660ce2b in QTimerInfoList::getTime (this=0x9c9463c, t=@0x9c94660) at kernel/qeventdispatcher_unix.cpp:339
#2  0xb660d001 in QTimerInfoList::updateCurrentTime (this=0x9c9463c) at kernel/qeventdispatcher_unix.cpp:297
#3  0xb660b2f3 in timerSourceCheck (source=0x9c94608) at kernel/qeventdispatcher_glib.cpp:156
#4  0xb4eb56f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#5  0xb4eb5fdd in ?? () from /usr/lib/libglib-2.0.so.0
#6  0xb4eb6268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#7  0xb660b1f7 in QEventDispatcherGlib::processEvents (this=0x9c6eb90, flags={i = -1548010280}) at kernel/qeventdispatcher_glib.cpp:326
#8  0xb65dddda in QEventLoop::processEvents (this=0xa3bb3d54, flags={i = -1548010216}) at kernel/qeventloop.cpp:149
#9  0xb65de21a in QEventLoop::exec (this=0xa3bb3d54, flags={i = -1548010148}) at kernel/qeventloop.cpp:200
#10 0xb7b4b8ab in KIO::NetAccess::enter_loop (this=0xa3bb3dc0) at /build/buildd/kde4libs-4.2.85/kio/kio/netaccess.cpp:502
#11 0xb7b4bf6f in KIO::NetAccess::synchronousRunInternal (this=0xa3bb3dc0, job=0xa9694d0, window=0x0, data=0xa3bb3e44, finalURL=0x0, metaData=0x0)
    at /build/buildd/kde4libs-4.2.85/kio/kio/netaccess.cpp:487
#12 0xb7b4c621 in KIO::NetAccess::synchronousRun (job=0xa9694d0, window=0x0, data=0xa3bb3e44, finalURL=0x0, metaData=0x0) at /build/buildd/kde4libs-4.2.85/kio/kio/netaccess.cpp:277
#13 0xa7f13c6f in ?? () from /usr/lib/kde4/plasma_applet_cwp.so
#14 0xa7f1cd92 in ?? () from /usr/lib/kde4/plasma_applet_cwp.so
#15 0xa7f20fa0 in ?? () from /usr/lib/kde4/plasma_applet_cwp.so
#16 0xb64eb56e in QThreadPrivate::start (arg=0xa9694d0) at thread/qthread_unix.cpp:189
#17 0xb50b44ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#18 0xb62f949e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xa29c6b90 (LWP 4631)):
#0  0xb7fe7430 in __kernel_vsyscall ()
#1  0xb50b8412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb6308344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb64ec58c in QWaitCondition::wait (this=0xa520b48, mutex=0xa520b44, time=30000) at thread/qwaitcondition_unix.cpp:85
#4  0xb64e1ac6 in QThreadPoolThread::run (this=0x9a78370) at concurrent/qthreadpool.cpp:140
#5  0xb64eb56e in QThreadPrivate::start (arg=0x9a78370) at thread/qthread_unix.cpp:189
#6  0xb50b44ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb62f949e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb3ce3730 (LWP 3619)):
[KCrash Handler]
#6  0x243489ff in ?? ()
#7  0xa335244b in KFileModule::createFileWidget (this=0xa774e88, startDir=@0xbfb033fc, parent=0x9baec78) at /build/buildd/kde4libs-4.2.85/kfile/kfilemodule.cpp:36
#8  0xb7bc1a6f in KFileDialog (this=0x9baec78, startDir=@0xbfb033fc, filter=@0xbfb03408, parent=0xaa53880, customWidget=0x0) at /build/buildd/kde4libs-4.2.85/kio/kfile/kfiledialog.cpp:238
#9  0xa81d2d7e in Image::showFileDialog (this=0xa86a4f8) at /build/buildd/kdebase-workspace-4.2.85/plasma/wallpapers/image/image.cpp:478
#10 0xa81d6833 in Image::qt_metacall (this=0xa86a4f8, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0xbfb0352c)
    at /build/buildd/kdebase-workspace-4.2.85/obj-i486-linux-gnu/plasma/wallpapers/image/image.moc:105
#11 0xb65f5a58 in QMetaObject::activate (sender=0xaaace80, from_signal_index=29, to_signal_index=30, argv=0xbfb0352c) at kernel/qobject.cpp:3120
#12 0xb65f5e90 in QMetaObject::activate (sender=0xaaace80, m=0xb710f1e4, from_local_signal_index=2, to_local_signal_index=3, argv=0xbfb0352c) at kernel/qobject.cpp:3214
#13 0xb6f26c81 in QAbstractButton::clicked (this=0xaaace80, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200
#14 0xb6c4f979 in QAbstractButtonPrivate::emitClicked (this=0xaaacea0) at widgets/qabstractbutton.cpp:543
#15 0xb6c515b4 in QAbstractButtonPrivate::click (this=0xaaacea0) at widgets/qabstractbutton.cpp:536
#16 0xb6c51846 in QAbstractButton::mouseReleaseEvent (this=0xaaace80, e=0xbfb03b28) at widgets/qabstractbutton.cpp:1115
#17 0xb6d3920c in QToolButton::mouseReleaseEvent (this=0xaaace80, e=0xbfb03b28) at widgets/qtoolbutton.cpp:709
#18 0xb68c18c3 in QWidget::event (this=0xaaace80, event=0xbfb03b28) at kernel/qwidget.cpp:7521
#19 0xb6c4f81e in QAbstractButton::event (this=0xaaace80, e=0xbfb03b28) at widgets/qabstractbutton.cpp:1077
#20 0xb6d3bc3a in QToolButton::event (this=0xaaace80, event=0xbfb03b28) at widgets/qtoolbutton.cpp:1151
#21 0xb686abcc in QApplicationPrivate::notify_helper (this=0x9466018, receiver=0xaaace80, e=0xbfb03b28) at kernel/qapplication.cpp:4057
#22 0xb6873851 in QApplication::notify (this=0x9458490, receiver=0xaaace80, e=0xbfb03b28) at kernel/qapplication.cpp:3759
#23 0xb76ccc9d in KApplication::notify (this=0x9458490, receiver=0xaaace80, event=0xbfb03b28) at /build/buildd/kde4libs-4.2.85/kdeui/kernel/kapplication.cpp:307
#24 0xb65df7ab in QCoreApplication::notifyInternal (this=0x9458490, receiver=0xaaace80, event=0xbfb03b28) at kernel/qcoreapplication.cpp:610
#25 0xb68728be in QApplicationPrivate::sendMouseEvent (receiver=0xaaace80, event=0xbfb03b28, alienWidget=0xaaace80, nativeWidget=0xa806400, buttonDown=0xb7116aa0, lastMouseReceiver=@0xb7116aa4)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#26 0xb68e2aee in QETWidget::translateMouseEvent (this=0xa806400, event=0xbfb051bc) at kernel/qapplication_x11.cpp:4448
#27 0xb68e1ead in QApplication::x11ProcessEvent (this=0x9458490, event=0xbfb051bc) at kernel/qapplication_x11.cpp:3444
#28 0xb690d06a in x11EventSourceDispatch (s=0x9468a70, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#29 0xb4eb2b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb4eb60eb in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb4eb6268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb660b1d8 in QEventDispatcherGlib::processEvents (this=0x945f2a8, flags={i = -1078963336}) at kernel/qeventdispatcher_glib.cpp:324
#33 0xb690c765 in QGuiEventDispatcherGlib::processEvents (this=0x945f2a8, flags={i = -1078963288}) at kernel/qguieventdispatcher_glib.cpp:202
#34 0xb65dddda in QEventLoop::processEvents (this=0xbfb05420, flags={i = -1078963224}) at kernel/qeventloop.cpp:149
#35 0xb65de21a in QEventLoop::exec (this=0xbfb05420, flags={i = -1078963160}) at kernel/qeventloop.cpp:200
#36 0xb65e06c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0xb686aa47 in QApplication::exec () at kernel/qapplication.cpp:3526
#38 0xb7f89290 in kdemain (argc=1, argv=0xbfb055d4) at /build/buildd/kdebase-workspace-4.2.85/plasma/shells/desktop/main.cpp:50
#39 0x08048712 in main (argc=173855152, argv=0x0) at /build/buildd/kdebase-workspace-4.2.85/obj-i486-linux-gnu/plasma/shells/desktop/plasma-desktop_dummy.cpp:3
Comment 1 Dario Andres 2009-05-19 02:40:10 UTC
*** Bug 192693 has been marked as a duplicate of this bug. ***
Comment 2 Aaron J. Seigo 2009-05-27 21:44:08 UTC
this looks like a bug in the filewidget, not the image plugin.
Comment 3 Dario Andres 2009-06-12 15:14:05 UTC
*** Bug 196136 has been marked as a duplicate of this bug. ***
Comment 4 Dario Andres 2009-07-18 20:41:23 UTC
Is this still happening with a recent KDE build? Thanks
Comment 5 Dario Andres 2009-08-12 23:35:10 UTC
*** Bug 200737 has been marked as a duplicate of this bug. ***
Comment 6 Caliburn 2009-08-17 02:09:58 UTC
This may be related or it may be unrelated. I'll post another bug report if unrelated.

Using KDE 4.3.0 and Arch Linux, changing a wallpaper 'Picture' will sometimes result in the 'Picture' setting becoming blank - no wallpaper selection appears whatsoever. If 'Apply' is clicked thereafter, the background comes up as if no option were selected and the background color is the only thing that appears.

Upon changing the background image once again, the wallpaper changer begins working as expected. 

There may be some relation here considering the crash and the location of the crash, atleast in my mind anyway. Nonetheless, I'll await further instruction.
Comment 7 David Hubner 2009-09-03 12:50:22 UTC
This bug is, as i found, due to duplication of libs withing archlinux when moving from kdemod to kde in the distribution. 

To solve this bug, remove all of kde and then look for any libs that belong to KDE and delete them.
Comment 8 Caliburn 2009-09-03 16:43:08 UTC
(In reply to comment #7)
> This bug is, as i found, due to duplication of libs withing archlinux when
> moving from kdemod to kde in the distribution. 
> 
> To solve this bug, remove all of kde and then look for any libs that belong to
> KDE and delete them.

.. if you use KDEmod, this is may or may not be a usable solution. For those of us using strict KDE from the repos within Arch Linux, however, this suggestion tends to go out the window. ;) Personally speaking, I've never used KDEmod and have no intention of using it.
Comment 9 David Hubner 2009-09-03 17:06:10 UTC
I believe yours is a different bug, although similar to this one. I would start a different bug report otherwise it might get burried in this one. 

The backtrace on the original poster points to KFileDialog bug through plasma which is the one due to duplicate libs. 

Does it crash when you do kquitapp plasma-desktop?
Comment 10 Beat Wolf 2009-10-08 09:46:08 UTC
*** Bug 207467 has been marked as a duplicate of this bug. ***
Comment 11 simon 2009-10-08 10:05:38 UTC
hi,

i reported the same issue today as bug 209844, but apart from a lot of closed dupes there us not real solution to this.
i don't have any mixed libraries (gentoo, kde from trunk) and so its not invalid for me, please reopen at least one bug to trace this.
how can on help with debugging?
Comment 12 Rodrigo 2009-10-25 21:29:49 UTC
*** Bug 211823 has been marked as a duplicate of this bug. ***
Comment 13 Rodrigo 2009-10-26 02:41:32 UTC
I see the bug resolved as invalid, can I ask why? It's not really a bug? Is there a workaround to fix it?
Comment 14 Dario Andres 2009-10-26 13:03:02 UTC
This is marked as INVALID because of comment 7; however... the issue has appeared on another systems too. But I can't be sure it isn't a downstream issue (on distributions) anyways...
Comment 15 Dario Andres 2009-11-06 03:44:38 UTC
Reopening...
Updated backtrace from bug 212716:
---


Thread 1 (Thread 0xb6065700 (LWP 3062)):
[KCrash Handler]
#6  0xb4b0868b in KFileWidget (this=0x9273fa8, _startDir=...,
parent=0xa85dcae0) at ../../kfile/kfilewidget.cpp:598
#7  0xa3b453fb in KFileModule::createFileWidget (this=0x8939b20, startDir=...,
parent=0xa85dcae0) at ../../kfile/kfilemodule.cpp:36
#8  0xb79f529f in KFileDialog (this=0xa85dcae0, startDir=..., filter=...,
parent=0xa854c3f0, customWidget=0x0) at ../../kio/kfile/kfiledialog.cpp:238
#9  0xa974708e in Image::showFileDialog (this=0xa854c4a8) at
../../../../plasma/wallpapers/image/image.cpp:469
#10 0xa974a873 in Image::qt_metacall (this=0xa854c4a8,
_c=QMetaObject::InvokeMetaMethod, _id=11, _a=0xbfa7a00c) at ./image.moc:106
Comment 16 Dario Andres 2009-11-06 03:45:12 UTC
From the same bug report:
What I was doing when the application crashed:
I changed the folders name where my wallpaper is located but I forgot to change
the path in the desktop background settings. When I opened the dialog for
changing the wallpaper and selected the "browse"-option the whole stuff crashed
pretty bad...
Comment 17 Dario Andres 2009-11-06 03:45:16 UTC
*** Bug 212716 has been marked as a duplicate of this bug. ***
Comment 18 Aaron J. Seigo 2009-11-06 19:26:30 UTC
#9  0xa974708e in Image::showFileDialog (this=0xa854c4a8) at
../../../../plasma/wallpapers/image/image.cpp:469

that line is "{" in the 4.3 branch. so, once again, we have something that's been patched.

http://websvn.kde.org/tags/KDE/4.3.2/kdebase/workspace/plasma/wallpapers/image/image.cpp?view=markup

i assume it's the new KFileDialog on line 471, in which case this is certainly a KFileDialog issue not a plasma issue.

looking at the code in KFileDialog, i'd not be surprised if it's a similar issue to the one already reported: a broken installation in some way. the reporter is using debian testing; perhaps a package update will fix it "magically" for them. in any case, information on whether it's repeatable or not, whether it happens only when opening the file dialog to a url that doesn't exist, whether it happens in other apps as well, etc would be useful.
Comment 19 Beat Wolf 2009-12-04 13:32:44 UTC
please reopen this bug if you can reproduce it with kde 4.4 (trunk)
Comment 20 Beat Wolf 2010-01-26 23:10:40 UTC
*** Bug 222123 has been marked as a duplicate of this bug. ***
Comment 21 Myriam Schweingruber 2012-05-28 22:26:13 UTC
Closing for lack of feedback.