Summary: | Plasma crashes when I try to change desktop wallpaper | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Sourish Basu <sourish.basu> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, aseigo, markotahal |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sourish Basu
2009-08-02 06:41:32 UTC
Can you install the "kdelibs5-dbg", "kdebase-workspace-dbg" and "libqt4-dbg" packages and try to reproduce the crash to get a complete backtrace? Thanks #14 0xb65aae51 in KIO::NetAccess::synchronousRun () from /usr/lib/libkio.so.5 #15 0xa92cdc0f in ?? () from /usr/lib/kde4/plasma_applet_cwp.so so the "customizable weather plasmoid" is the only thread that's actually running in this crash, and it's calling KIO methods from a separate thread. if you remove the CWP widget, does this crash go away? i dont have the plasmoid and there's no crash. # kde 4.3 not even w/ the plasmoid added I removed the customizable weather plasmoid, but I still get the mouse freeze. This time I did not get a KDE crash handler message, so I couldn't give you a backtrace. I had to do a "kquitapp plasma" to unfreeze. Will install the dbg packages and post the output. With the kde debug packages installed, the crash handler says: Application: Plasma Workspace (plasma), signal SIGSEGV [Current thread is 0 (LWP 4369)] Thread 3 (Thread 0xa6afeb90 (LWP 4397)): #0 0xb7f4a424 in __kernel_vsyscall () #1 0xb4ff9f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb7e5585d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb67c0502 in QWaitCondition::wait (this=0x8fbd140, mutex=0x8fbd13c, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 0xa92e8a5a in RenderThread::run (this=0x8fbd134) at ../../../../plasma/wallpapers/image/renderthread.cpp:91 #5 0xb67bf522 in QThreadPrivate::start (arg=0x8fbd134) at thread/qthread_unix.cpp:188 #6 0xb4ff64b5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb7e46a5e in clone () from /lib/i686/cmov/libc.so.6 Thread 2 (Thread 0xa62fdb90 (LWP 4821)): #0 0xb7f4a424 in __kernel_vsyscall () #1 0xb7e3efe1 in select () from /lib/i686/cmov/libc.so.6 #2 0xb688ec20 in QProcessManager::run (this=0x8c052d8) at io/qprocess_unix.cpp:296 #3 0xb67bf522 in QThreadPrivate::start (arg=0x8c052d8) at thread/qthread_unix.cpp:188 #4 0xb4ff64b5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #5 0xb7e46a5e in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb4c1b720 (LWP 4369)): [KCrash Handler] #6 0xb69e6016 in QDBusAdaptorConnector::relaySlot (this=0xa7304f90, argv=0xbf96797c) at qdbusabstractadaptor.cpp:268 #7 0xb69e69a8 in QDBusAdaptorConnector::qt_metacall (this=0xa7304f90, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf96797c) at qdbusabstractadaptor.cpp:364 #8 0xb68c5ad3 in QMetaObject::activate (sender=0xa7300a28, from_signal_index=0, to_signal_index=1, argv=0xbf96797c) at kernel/qobject.cpp:3112 #9 0xb68c5f00 in QMetaObject::activate (sender=0xa7300a28, m=0xb699d628, from_local_signal_index=0, to_local_signal_index=1, argv=0xbf96797c) at kernel/qobject.cpp:3206 #10 0xb68c5f8b in QObject::destroyed (this=0xa7300a28, _t1=0xa7300a28) at .moc/release-shared/moc_qobject.cpp:143 #11 0xb68c6d99 in ~QObject (this=0xa7300a28) at kernel/qobject.cpp:757 #12 0xb6569b7d in ~Scheduler (this=0xa7300a28) at ../../kio/kio/scheduler.cpp:246 #13 0xb656d2f4 in destroy () at ../../kio/kio/scheduler.cpp:102 #14 0xb64ab80b in ~KCleanUpGlobalStatic (this=0xb6676054) at ../../kdecore/kernel/kglobal.h:62 #15 0xb7d95589 in exit () from /lib/i686/cmov/libc.so.6 #16 0xb7d7b7ad in __libc_start_main () from /lib/i686/cmov/libc.so.6 #17 0x080484d1 in _start () at ../sysdeps/i386/elf/start.S:119 Mh, the last crash seems more like bug 189592. Thanks The crash was caused by the CWP widget (using KIO on a secondary thread) Update it to the latest version or remove it. Regards *** This bug has been marked as a duplicate of bug 189592 *** |