plasma-desktop crashes repeatedly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Base Workspace |
Fix Released
|
High
|
|||
kde-workspace (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Since upgrading Kubuntu from 12.10 to 13.04, plasma-desktop has crashed repeatedly. I used to have a few crashes here or there (every week or 2) in 12.10 (especially when using the comics widget), but since upgrading, it crashes whenever I:
- switch application windows
- switch desktops
- change tabs in firefox
- access any desktop widget
- try to add a widget
I have removed as many of the desktop widgets that I can to eliminate them. I still have:
- A standard panel
-- KDE Application Launcher
-- Show Desktop
-- Task Manager
-- Pager
-- System Tray
-- Digital Clock
- Twitter
I have NOT been able to fill out an automated crash report, as the desktop crashes and restarts when I try an open the crash reporter. I can force a crash every time by trying to add/remove/modify any widget.
I have run plasma-desktop from terminal and this is the output I get when it crashes:
KCrash: Attempting to start /usr/bin/
sock_
KCrash: Application 'plasma-desktop' crashing...
KCrash: Attempting to start /usr/lib/
sock_
The full terminal output is uploaded as the attachment "terminalOutput
kdm.log is empty
apport.log is attached
I have never been able to get the debugging symbols for plasma-desktop to install. Everytime I try to do it via the crash handler, it says they install, then sends me back to saying I need to install them (repeat in endless loop). If someone can tell me the package name and repository, I will install them and try to run the crash handler again.
If there is anything else I can provide, please let me know.
In KDE Bug Tracking System #311871, freedomrun (freedomrun) wrote : | #7 |
In KDE Bug Tracking System #311871, Adam Maćkowiak (admc) wrote : | #8 |
Created attachment 75913
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.9.90 using Qt 4.8.3
- What I was doing when the application crashed:
I was browsing internet using Mozilla Firefox.
-- Backtrace (Reduced):
#8 0xb6cd6fe5 in QPointer (p=..., this=0xbfab040c) at ../../include/
#9 takeAt (i=14, this=0x998a704) at ../../include/
#10 QDeclarativeRep
#11 0xb6e352c2 in qt_static_metacall (_a=0xbfab0524, _id=6, _o=0x998a528, _c=<optimized out>) at .moc/release-
#12 QDeclarativeRep
In KDE Bug Tracking System #311871, Fraph24 (fraph24) wrote : | #9 |
Created attachment 76092
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.9.95 using Qt 4.8.4
- What I was doing when the application crashed:
I was browsing with Firefox
- Custom settings of the application:
I had KDE Telepathy minimized and maybe Konsole, nothing more.
-- Backtrace (Reduced):
#7 0x000000303757261e in QPointer (p=..., this=0x7fffef87
#8 takeAt (i=13, this=0x4941c08) at ../../src/
#9 QDeclarativeRep
[...]
#11 0x00000030376b792f in QDeclarativeVis
#12 0x000000303758954c in QDeclarativeVis
In KDE Bug Tracking System #311871, sumski (hrvoje-senjan) wrote : | #10 |
Created attachment 76118
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.60 "release 16" using Qt 4.8.5
- What I was doing when the application crashed:
It seems to me this kind of crash is related to notifications. Only activity *i think* whas happening, is the next song started in Clementine --> hence a notification about it.
-- Backtrace (Reduced):
#7 0x00007f28a1f096ee in QPointer (p=..., this=0x7fff0977
#8 takeAt (i=4, this=0x408fd48) at ../../src/
#9 QDeclarativeRep
[...]
#11 0x00007f28a204e69f in QDeclarativeVis
#12 0x00007f28a1f2061c in QDeclarativeVis
In KDE Bug Tracking System #311871, Jirislaby (jirislaby) wrote : | #11 |
Created attachment 76275
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.9.95 using Qt 4.8.3
- What I was doing when the application crashed:
Nothing, I returned to PC and saw this. Perhaps a notification by gpmc player or thunderbird.
-- Backtrace (Reduced):
#6 0x00007f7bc3852cde in QPointer (p=..., this=0x7fffb9b5
#7 takeAt (i=5, this=0x27829c8) at ../../src/
#8 QDeclarativeRep
[...]
#10 0x00007f7bc399716f in QDeclarativeVis
#11 0x00007f7bc3869c3c in QDeclarativeVis
In KDE Bug Tracking System #311871, Mgraesslin (mgraesslin) wrote : | #12 |
*** Bug 313239 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #13 |
*** Bug 314125 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Nico-kruber (nico-kruber) wrote : | #14 |
Created attachment 76985
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 using Qt 4.8.4
- What I was doing when the application crashed:
I was playing around with kmymoney - but did not open or close any application
-- Backtrace (Reduced):
#6 0x00007f6e3e39abe1 in QPointer (p=..., this=0x7ffff0fc
#7 takeAt (i=4, this=0x4437d38) at ../../src/
#8 QDeclarativeRep
[...]
#10 0x00007f6e3e4dfb1f in QDeclarativeVis
#11 0x00007f6e3e3b1b1c in QDeclarativeVis
In KDE Bug Tracking System #311871, Marek Śledziona (m-sledziona) wrote : | #15 |
Created attachment 77007
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4
- What I was doing when the application crashed:
Just browsint hhe Web with Firefox (18.0.1) and listening to music using Amarok (2.7.0).
- Unusual behavior I noticed:
Just before the crash my desktop (Plasma Desktop and Firefox) freezed for a few seconds. Crash did not affect Amarok playing music, only the UI was freezed.
-- Backtrace (Reduced):
#7 0x00007facc069abee in QPointer (p=..., this=0x7fffad1e
#8 takeAt (i=8, this=0x26b42f8) at ../../src/
#9 QDeclarativeRep
[...]
#11 0x00007facc07dfb1f in QDeclarativeVis
#12 0x00007facc06b1b1c in QDeclarativeVis
In KDE Bug Tracking System #311871, Stratos Zolotas (baskin) wrote : | #16 |
Created attachment 77040
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4
- What I was doing when the application crashed:
Automaticaly refreshing choqok that includes notification.
-- Backtrace (Reduced):
#6 0x00007f671c1b2bee in QPointer (p=..., this=0x7fffc8c4
#7 takeAt (i=1, this=0x4188648) at ../../src/
#8 QDeclarativeRep
[...]
#10 0x00007f671c2f7b1f in QDeclarativeVis
#11 0x00007f671c1c9b1c in QDeclarativeVis
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #17 |
*** Bug 314904 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #18 |
*** Bug 314917 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Simon Andric (simonandric5) wrote : | #19 |
Application: plasma-desktop (0.4)
KDE Platform Version: 4.10.00
Qt Version: 4.8.4
Operating System: Linux 3.8.0-5-generic i686
Distribution: Ubuntu Raring Ringtail (development branch)
-- Information about the crash:
<Podrobno opišite, kaj ste počeli, ko se je program sesul.>
The crash can be reproduced every time.
-- Backtrace:
Application: Delovno okolje Plasma Desktop (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/i386-
[Current thread is 1 (Thread 0xb1c88740 (LWP 2510))]
Thread 5 (Thread 0xae3e3b40 (LWP 2518)):
#0 0xb77b0424 in __kernel_vsyscall ()
#1 0xb2aa184b in pthread_
#2 0xb765bd6c in __pthread_cond_wait (cond=0xb3bac670, mutex=0xb3bac658) at forward.c:149
#3 0xb3a9a14d in ?? () from /usr/lib/
#4 0xb3a9a17f in ?? () from /usr/lib/
#5 0xb2a9dd78 in start_thread (arg=0xae3e3b40) at pthread_
#6 0xb764e3ce in clone () at ../sysdeps/
Thread 4 (Thread 0xa790db40 (LWP 2519)):
#0 __pthread_
#1 0xb765bfb4 in pthread_
#2 0xb29d2050 in g_mutex_unlock () from /lib/i386-
#3 0xb298dc50 in g_main_
#4 0xb298e50f in ?? () from /lib/i386-
#5 0xb298e771 in g_main_
#6 0xb604cc1f in QEventDispatche
#7 0xb60193cc in QEventLoop:
#8 0xb60196c1 in QEventLoop::exec (this=0xa790d228, flags=...) at kernel/
#9 0xb5f04fcc in QThread::exec (this=0xa793080) at thread/
#10 0xb5ff8f0d in QInotifyFileSys
#11 0xb5f07af8 in QThreadPrivate:
#12 0xb2a9dd78 in start_thread (arg=0xa790db40) at pthread_
#13 0xb764e3ce in clone () at ../sysdeps/
Thread 3 (Thread 0xa5259b40 (LWP 2522)):
#0 0xb298d7b0 in g_main_
#1 0xb298e5b8 in ?? () from /lib/i386-
#2 0xb298e771 in g_main_
#3 0xb604cc1f in QEventDispatche
#4 0xb60193cc in QEventLoop:
#5 0xb60196c1 in QEventLoop::exec (this=0xa5259228, flags=...) at kernel/
#6 0xb5f04fcc in QThread::exec (this=0xacc6fd8) at thread/
#7 0xb5ff8f0d in QInotifyFileSys
In KDE Bug Tracking System #311871, Simon Andric (simonandric5) wrote : | #20 |
Application: Delovno okolje Plasma Desktop (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/i386-
[Current thread is 1 (Thread 0xb1c88740 (LWP 2510))]
Thread 5 (Thread 0xae3e3b40 (LWP 2518)):
#0 0xb77b0424 in __kernel_vsyscall ()
#1 0xb2aa184b in pthread_
#2 0xb765bd6c in __pthread_cond_wait (cond=0xb3bac670, mutex=0xb3bac658) at forward.c:149
#3 0xb3a9a14d in ?? () from /usr/lib/
#4 0xb3a9a17f in ?? () from /usr/lib/
#5 0xb2a9dd78 in start_thread (arg=0xae3e3b40) at pthread_
#6 0xb764e3ce in clone () at ../sysdeps/
Thread 4 (Thread 0xa790db40 (LWP 2519)):
#0 __pthread_
#1 0xb765bfb4 in pthread_
#2 0xb29d2050 in g_mutex_unlock () from /lib/i386-
#3 0xb298dc50 in g_main_
#4 0xb298e50f in ?? () from /lib/i386-
#5 0xb298e771 in g_main_
#6 0xb604cc1f in QEventDispatche
#7 0xb60193cc in QEventLoop:
#8 0xb60196c1 in QEventLoop::exec (this=0xa790d228, flags=...) at kernel/
#9 0xb5f04fcc in QThread::exec (this=0xa793080) at thread/
#10 0xb5ff8f0d in QInotifyFileSys
#11 0xb5f07af8 in QThreadPrivate:
#12 0xb2a9dd78 in start_thread (arg=0xa790db40) at pthread_
#13 0xb764e3ce in clone () at ../sysdeps/
Thread 3 (Thread 0xa5259b40 (LWP 2522)):
#0 0xb298d7b0 in g_main_
#1 0xb298e5b8 in ?? () from /lib/i386-
#2 0xb298e771 in g_main_
#3 0xb604cc1f in QEventDispatche
#4 0xb60193cc in QEventLoop:
#5 0xb60196c1 in QEventLoop::exec (this=0xa5259228, flags=...) at kernel/
#6 0xb5f04fcc in QThread::exec (this=0xacc6fd8) at thread/
#7 0xb5ff8f0d in QInotifyFileSys
#8 0xb5f07af8 in QThreadPrivate:
#9 0xb2a9dd78 in start_thread (arg=0xa5259b40) at pthread_
#10 0xb764e3ce in clone () at ../sysdeps/
Thread 2 (Thread 0xa2983b40 (LWP 2561)):
#0 0xb77b0424 in __kernel_vsyscall ()
#1 0xb766...
In KDE Bug Tracking System #311871, Simon Andric (simonandric5) wrote : | #21 |
Application: Delovno okolje Plasma Desktop (plasma-desktop (deleted)), signal: Segmentation fault
[Current thread is 1 (process 2575)]
Thread 1 (process 2575):
#0 0xb775a424 in ?? ()
In KDE Bug Tracking System #311871, Radimx (radimx) wrote : | #22 |
Created attachment 77222
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4
- What I was doing when the application crashed:
I was working in konsole and been logged via SSH to a remote server.
-- Backtrace (Reduced):
#7 0x00007fd0a91f3bee in QPointer (p=..., this=0x7fff1bc5
#8 takeAt (i=3, this=0x3b61b28) at ../../src/
#9 QDeclarativeRep
[...]
#11 0x00007fd0a9338b1f in QDeclarativeVis
#12 0x00007fd0a920ab1c in QDeclarativeVis
In KDE Bug Tracking System #311871, Radimx (radimx) wrote : | #23 |
Created attachment 77258
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4
- What I was doing when the application crashed:
I was browsing internet with Mozilla Firefox.
-- Backtrace (Reduced):
#7 0x00007f028fcadbee in QPointer (p=..., this=0x7fff575c
#8 takeAt (i=2, this=0x36e5588) at ../../src/
#9 QDeclarativeRep
[...]
#11 0x00007f028fdf2b1f in QDeclarativeVis
#12 0x00007f028fcc4b1c in QDeclarativeVis
In KDE Bug Tracking System #311871, Erwin Van de Velde (evdvelde) wrote : | #24 |
Created attachment 77259
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4
I have had this crash in a number of cases, independently of what I was doing, sometimes surfing with firefox, sometimes typing documents in kile, etc. I always keep a number of applications open, so I cannot tell if it is application related.
It happens occasionally to me (3-5 times per day).
-- Backtrace (Reduced):
#6 0x00007f512ca6ebee in QPointer (p=..., this=0x7fff2b22
#7 takeAt (i=5, this=0x3623b18) at ../../src/
#8 QDeclarativeRep
[...]
#10 0x00007f512cbb3b1f in QDeclarativeVis
#11 0x00007f512ca85b1c in QDeclarativeVis
In KDE Bug Tracking System #311871, Simon Andric (simonandric5) wrote : | #25 |
Application: plasma-desktop (0.4)
KDE Platform Version: 4.10.00
Qt Version: 4.8.4
Operating System: Linux 3.8.0-6-generic i686
Distribution: Ubuntu Raring Ringtail (development branch)
-- Information about the crash:
<Podrobno opišite, kaj ste počeli, ko se je program sesul.>
The crash can be reproduced every time.
-- Backtrace:
Application: Delovno okolje Plasma Desktop (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/i386-
[Current thread is 1 (Thread 0xb1c09740 (LWP 2534))]
Thread 5 (Thread 0xae360b40 (LWP 2544)):
#0 0xb7731424 in __kernel_vsyscall ()
#1 0xb2a2284b in pthread_
#2 0xb75dcd7c in __pthread_cond_wait (cond=0xb3b2d670, mutex=0xb3b2d658) at forward.c:149
#3 0xb3a1b14d in ?? () from /usr/lib/
#4 0xb3a1b17f in ?? () from /usr/lib/
#5 0xb2a1ed78 in start_thread (arg=0xae360b40) at pthread_
#6 0xb75cf3de in clone () at ../sysdeps/
Thread 4 (Thread 0xa788ab40 (LWP 2545)):
#0 0xb75dcf75 in pthread_mutex_lock (mutex=0xa6f00558) at forward.c:192
#1 0xb2953010 in g_mutex_lock () from /lib/i386-
#2 0xb290f061 in g_main_
#3 0xb290f5a2 in ?? () from /lib/i386-
#4 0xb290f771 in g_main_
#5 0xb5fcdc1f in QEventDispatche
#6 0xb5f9a3cc in QEventLoop:
#7 0xb5f9a6c1 in QEventLoop::exec (this=0xa788a228, flags=...) at kernel/
#8 0xb5e85fcc in QThread::exec (this=0xa54b9f8) at thread/
#9 0xb5f79f0d in QInotifyFileSys
#10 0xb5e88af8 in QThreadPrivate:
#11 0xb2a1ed78 in start_thread (arg=0xa788ab40) at pthread_
#12 0xb75cf3de in clone () at ../sysdeps/
Thread 3 (Thread 0xa51c8b40 (LWP 2548)):
#0 0xb2a21c09 in __pthread_
#1 0xb75dcfc4 in pthread_
#2 0xb2953050 in g_mutex_unlock () from /lib/i386-
#3 0xb290e666 in g_main_
#4 0xb290f4b8 in ?? () from /lib/i386-
#5 0xb290f771 in g_main_
#6 0xb5fcdc1f in QEventDispatche
#7 0xb5f9a3cc in QEventLoop:
#8 0xb5f9a6c1 in QEventLoop::exec (this=0xa51c8228, flags=...) at kernel/
#9 0xb5e85fcc in...
In KDE Bug Tracking System #311871, Simon Andric (simonandric5) wrote : | #26 |
Application: Delovno okolje Plasma Desktop (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/i386-
[Current thread is 1 (Thread 0xb1c09740 (LWP 2534))]
Thread 5 (Thread 0xae360b40 (LWP 2544)):
#0 0xb7731424 in __kernel_vsyscall ()
#1 0xb2a2284b in pthread_
#2 0xb75dcd7c in __pthread_cond_wait (cond=0xb3b2d670, mutex=0xb3b2d658) at forward.c:149
#3 0xb3a1b14d in ?? () from /usr/lib/
#4 0xb3a1b17f in ?? () from /usr/lib/
#5 0xb2a1ed78 in start_thread (arg=0xae360b40) at pthread_
#6 0xb75cf3de in clone () at ../sysdeps/
Thread 4 (Thread 0xa788ab40 (LWP 2545)):
#0 0xb75dcf75 in pthread_mutex_lock (mutex=0xa6f00558) at forward.c:192
#1 0xb2953010 in g_mutex_lock () from /lib/i386-
#2 0xb290f061 in g_main_
#3 0xb290f5a2 in ?? () from /lib/i386-
#4 0xb290f771 in g_main_
#5 0xb5fcdc1f in QEventDispatche
#6 0xb5f9a3cc in QEventLoop:
#7 0xb5f9a6c1 in QEventLoop::exec (this=0xa788a228, flags=...) at kernel/
#8 0xb5e85fcc in QThread::exec (this=0xa54b9f8) at thread/
#9 0xb5f79f0d in QInotifyFileSys
#10 0xb5e88af8 in QThreadPrivate:
#11 0xb2a1ed78 in start_thread (arg=0xa788ab40) at pthread_
#12 0xb75cf3de in clone () at ../sysdeps/
Thread 3 (Thread 0xa51c8b40 (LWP 2548)):
#0 0xb2a21c09 in __pthread_
#1 0xb75dcfc4 in pthread_
#2 0xb2953050 in g_mutex_unlock () from /lib/i386-
#3 0xb290e666 in g_main_
#4 0xb290f4b8 in ?? () from /lib/i386-
#5 0xb290f771 in g_main_
#6 0xb5fcdc1f in QEventDispatche
#7 0xb5f9a3cc in QEventLoop:
#8 0xb5f9a6c1 in QEventLoop::exec (this=0xa51c8228, flags=...) at kernel/
#9 0xb5e85fcc in QThread::exec (this=0xaa35cd0) at thread/
#10 0xb5f79f0d in QInotifyFileSys
#11 0xb5e88af8 in QThreadPrivate:
#12 0xb2a1ed78 in start_thread (arg=0xa51c8b40) at pthread_
#13 ...
In KDE Bug Tracking System #311871, sumski (hrvoje-senjan) wrote : | #27 |
(In reply to comment #18)
> The crash can be reproduced every time.
Please tell us how.
In KDE Bug Tracking System #311871, Simon Andric (simonandric5) wrote : | #28 |
hello!
i appologize...i didnt mean the crash can be reporoduced any time... i meant..the crash happens any time... sometimes right after reboot, sometimes during normal (but random) computer work..
nice day
Simon :)
In KDE Bug Tracking System #311871, Radimx (radimx) wrote : | #29 |
Created attachment 77284
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4
- What I was doing when the application crashed:
I was browsing the web. It crashed several times a day.
-- Backtrace (Reduced):
#7 0x00007f5addd6ebee in QPointer (p=..., this=0x7fff95cf
#8 takeAt (i=1, this=0x24d2068) at ../../src/
#9 QDeclarativeRep
[...]
#11 0x00007f5addeb3b1f in QDeclarativeVis
#12 0x00007f5addd85b1c in QDeclarativeVis
In KDE Bug Tracking System #311871, ronwilhoite (ronwilhoite) wrote : | #30 |
Created attachment 77306
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 using Qt 4.8.3
- What I was doing when the application crashed:
Using Firefox at the moment it happened. Also had Konversation, Kopete, and Thunderbird running. Applications were not affected and the plasma shell restarted itself. Items in the task manager are out of order after plasma restarts, but easily re-arranged.
I can't reproduce it, but it happens maybe once a week.
-- Backtrace (Reduced):
#7 0x00007f85beaa2e0e in QPointer (p=..., this=0x7fff4229
#8 takeAt (i=12, this=0x435c448) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f85bebe7c3f in QDeclarativeVis
#12 0x00007f85beab9d6c in QDeclarativeVis
In KDE Bug Tracking System #311871, Savenger (savenger) wrote : | #31 |
Created attachment 77317
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 using Qt 4.8.3
- What I was doing when the application crashed:
Browsing the web using Firefox
Chatting with aim, gmail contacts in pidgin (Had focus at the time of the crash)
Steam Client running, no game running.
PokerTH running, not being actively used.
-- Backtrace (Reduced):
#7 0x00007f14f9885e0e in QPointer (p=..., this=0x7fff6f6d
#8 takeAt (i=6, this=0x206cc08) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f14f99cac3f in QDeclarativeVis
#12 0x00007f14f989cd6c in QDeclarativeVis
In KDE Bug Tracking System #311871, Radimx (radimx) wrote : | #32 |
Created attachment 77407
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 "release 550" using Qt 4.8.4
- What I was doing when the application crashed:
I was switching the windows in desktop and it crashed again.
-- Backtrace (Reduced):
#7 0x00007f80bd874f59 in memmove (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at /usr/include/
#8 QListData::remove (this=0x2f58388, i=<optimized out>) at tools/qlist.cpp:347
#9 0x00007f80b1645c12 in takeAt (i=1, this=0x2f58388) at ../../src/
#10 QDeclarativeRep
[...]
#12 0x00007f80b178ab1f in QDeclarativeVis
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #33 |
*** Bug 315585 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #34 |
*** Bug 315436 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #35 |
*** Bug 315700 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #36 |
I just checked the Qt 4.8 sources, and it's probably a QtDeclarative bug (again).
Qt developers, however, need a reproducible test case, so if a Plasma developer knows how to create a simple QML test case, please add a comment.
See also https:/
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #37 |
From looking at the comments, it is the notifications applet which is using those QML list models.
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #38 |
*** Bug 315762 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Brunofr (brunofr) wrote : | #39 |
Created attachment 77755
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.00 "release 550" using Qt 4.8.4
- What I was doing when the application crashed: stangely browsing the web ( by changing tabs in Firefox 19)
Also jumping from desktop in and out swapping between Firefox and Konversation.
Using Nivida 310.12 package. openGL and effect on.
-- Backtrace (Reduced):
#7 0x00007f77021b1f59 in memmove (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at /usr/include/
#8 QListData::remove (this=0x5be45d8, i=<optimized out>) at tools/qlist.cpp:347
#9 0x00007f76f5f83c12 in takeAt (i=2, this=0x5be45d8) at ../../src/
#10 QDeclarativeRep
[...]
#12 0x00007f76f60c8b1f in QDeclarativeVis
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #40 |
*** Bug 316164 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #41 |
*** Bug 316568 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Lastique (andysem) wrote : | #42 |
Created attachment 78007
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.1 using Qt 4.8.2
- What I was doing when the application crashed:
I was doing nothing special, just typing a message in Skype. A had similar crashes on Kubuntu 12.10 as well in other situations (also nothing special).
-- Backtrace (Reduced):
#7 0x00007ff99eae312f in QPointer (p=..., this=0x7fffcdb5
#8 takeAt (i=8, this=0x36d0da8) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007ff99ec2bf1f in QDeclarativeVis
#12 0x00007ff99eaf7e49 in QDeclarativeVis
In KDE Bug Tracking System #311871, Ralf Jung (0tlwui8x-post-kj985rvy) wrote : | #43 |
Created attachment 78012
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.1 using Qt 4.8.2
- What I was doing when the application crashed:
The crash happened exactly at the time when Kopete notified me (via sound) that a new chat message arrived. So it may be related to Kopete changing its icon (from the Kopete icon to that spinning thingy).
I had a bunch of other applications running, and the notification area contained:
Veromix, Amarok, Thunderbird, Liferea, Kopete, Networkmanagement
Hidden: Wallet, Klipper, Battery, Device Notifier
-- Backtrace (Reduced):
#7 0x00007fc8b165848e in QPointer (p=..., this=0x7ffff4b6
#8 takeAt (i=1, this=0x4a83a08) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007fc8b179bcdf in QDeclarativeVis
#12 0x00007fc8b166eeac in QDeclarativeVis
In KDE Bug Tracking System #311871, Marcin Janowski (janowski-m) wrote : | #44 |
Created attachment 78028
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.1 using Qt 4.8.3
- What I was doing when the application crashed:
Before crash i scrolling up my mouse on volume plasmoid to volume up.
-- Backtrace (Reduced):
#7 0x00007f52fac7ae0e in QPointer (p=..., this=0x7fff4713
#8 takeAt (i=12, this=0x5768b88) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f52fadbfe6f in QDeclarativeVis
#12 0x00007f52fac91d6c in QDeclarativeVis
In KDE Bug Tracking System #311871, Bugskdeorg (bugskdeorg) wrote : | #45 |
Created attachment 78193
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.1 using Qt 4.8.2
- What I was doing when the application crashed:
Typing a command in Konsole. I may have been moving the mouse at the time.
-- Backtrace (Reduced):
#8 0xb6c2c43c in QPointer (p=..., this=0xbfc19c7c) at ../../include/
#9 takeAt (i=1, this=0xb39dadc) at ../../include/
#10 QDeclarativeRep
#11 0xb6d8e492 in qt_static_metacall (_a=0xbfc19d84, _id=6, _o=0xb39d900, _c=<optimized out>) at .moc/release-
#12 QDeclarativeRep
In KDE Bug Tracking System #311871, U26 (u26) wrote : | #46 |
*** Bug 317181 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Nemo_bis (nemobis) wrote : | #47 |
Created attachment 78490
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.1 using Qt 4.8.4
- What I was doing when the application crashed:
Surfing on chromium (editing a Google Doc)
-- Backtrace (Reduced):
#8 0x42ff2f16 in QPointer (p=..., this=0xbfb8db6c) at ../../src/
#9 takeAt (i=1, this=0xa4570bc) at ../../src/
#10 QDeclarativeRep
#11 0x43155862 in qt_static_metacall (_c=QMetaObject
#12 QDeclarativeRep
In KDE Bug Tracking System #311871, Dima Ryazanov (dima-gmail) wrote : | #48 |
Got this crash again, but the stack trace looks a little longer (with calls to malloc in the middle?..)
Thread 1 (Thread 0x7f4eedd49780 (LWP 3893)):
[KCrash Handler]
#6 0x00007f4efdd47c6e in QMetaObject:
#7 0x00007f4eff944e0e in QPointer (p=..., this=0x7ffff490
#8 takeAt (i=6, this=0x2922178) at ../../include/
#9 QDeclarativeRep
#10 0x00007f4efdd48f8f in QMetaObject:
#11 0x00007f4effa89e6f in QDeclarativeVis
#12 0x00007f4eff95bd6c in QDeclarativeVis
#13 0x00007f4effa8a4a1 in QDeclarativeVis
#14 0x00007f4efdd48f8f in QMetaObject:
#15 0x00007f4effa7e8ff in QListModelInter
#16 0x00007f4eff8c737f in QDeclarativeLis
#17 0x00007f4effa7d4cb in QDeclarativeLis
#18 0x00007f4effa7d5cf in QDeclarativeLis
#19 0x00007f4effa28018 in QDeclarativeObj
#20 0x00007f4effa29c86 in QDeclarativeObj
#21 0x00007f4effa2a5bb in QDeclarativeObj
#22 0x00007f4efae2f0b3 in ?? () from /usr/lib/
#23 0x00007f4efad2b1d0 in ?? () from /usr/lib/
#24 0x00007f4efad082c6 in ?? () from /usr/lib/
#25 0x00007f4ed919a9f8 in ...
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #49 |
*** Bug 317560 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Filippe LeMarchand (gasinvein) wrote : | #50 |
*** This bug has been confirmed by popular vote. ***
In KDE Bug Tracking System #311871, Filippe LeMarchand (gasinvein) wrote : | #51 |
Can it be somehow caused by Firefox? Seems like all the people above were using it. What for me, I used Chromium before and this crash on current KDE version (4.10.1) didn't happen. Sorry for my english.
In KDE Bug Tracking System #311871, Nemo_bis (nemobis) wrote : | #52 |
(In reply to comment #44)
> Can it be somehow caused by Firefox? Seems like all the people above were
> using it. What for me, I used Chromium before and this crash on current KDE
> version (4.10.1) didn't happen. Sorry for my english.
I was using Chromium. Firefox was also open at the same time, though.
In KDE Bug Tracking System #311871, Lastique (andysem) wrote : | #53 |
(In reply to comment #44)
> Can it be somehow caused by Firefox? Seems like all the people above were
> using it. What for me, I used Chromium before and this crash on current KDE
> version (4.10.1) didn't happen. Sorry for my english.
I had crashes when Firefox was not running.
In KDE Bug Tracking System #311871, Ralf Jung (0tlwui8x-post-kj985rvy) wrote : | #54 |
Shouldn't this be marked as regression? After all, it did not happen with the previous notification implementation.
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #55 |
*** Bug 317261 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #56 |
*** Bug 318170 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, O-brian (o-brian) wrote : | #57 |
So do we have any ideas of how to mitigate things until the QtDeclarative architecture is fixed or KDE finds a workaround to not trigger the code path? I'm having it happen both under Nouveau and nVidia's binary driver both. Oddly enough, my work computer has Intel graphics and I don't have the crashes under that and both have Fedora 18 and are at the same software versions.
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #58 |
*** Bug 318381 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #59 |
*** Bug 318410 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #60 |
*** Bug 318440 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #61 |
*** Bug 318542 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #62 |
*** Bug 318715 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, sumski (hrvoje-senjan) wrote : | #63 |
Created attachment 79384
New crash information added by DrKonqi
plasma-desktop (4.10.60 "release 112") on KDE Platform 4.10.60 "release 112" using Qt 4.8.5
- What I was doing when the application crashed:
Just in case someone was wondering, the crash can still occur with latest Qt/4.8 branch, and latest KDE (libs, workspace, etc) master.
@Christoph, unfortunatelly, the problem is that it cannot be reproduced at will. So it'll be a tough one to fix.
-- Backtrace (Reduced):
#6 0x00007f24ee05174e in QPointer (p=..., this=0x7ffff809
#7 takeAt (i=1, this=0x3ee6ff0) at ../../src/
#8 QDeclarativeRep
[...]
#10 0x00007f24ee19783f in QDeclarativeVis
#11 0x00007f24ee0684fc in QDeclarativeVis
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #64 |
*** Bug 318854 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #65 |
*** Bug 318817 has been marked as a duplicate of this bug. ***
abmoraz (abmoraz) wrote : | #1 |
abmoraz (abmoraz) wrote : | #2 |
- log of apport Edit (16.7 KiB, text/plain)
The apport log for the same time period (at least 25 crashes in there)
description: | updated |
description: | updated |
Launchpad Janitor (janitor) wrote : | #3 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in kde-workspace (Ubuntu): | |
status: | New → Confirmed |
In KDE Bug Tracking System #311871, valery (valerymamonov) wrote : | #66 |
Created attachment 79619
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
I was browsing Internet via Google Chrome, and then plasma-desktop had crashed
-- Backtrace (Reduced):
#7 0x000000364af7761e in QPointer (p=..., this=0x7fff9132
#8 takeAt (i=1, this=0x2aaec48) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x000000364b0bcd3f in QDeclarativeVis
#12 0x000000364af8e54c in QDeclarativeVis
Harald Sitter (apachelogger) wrote : | #4 |
Please post the crash handler backtrace regardless.
Changed in kde-workspace (Ubuntu): | |
status: | Confirmed → Incomplete |
summary: |
- plasma-desktop crashes repeatedly since upgrading to 14.04 + plasma-desktop crashes repeatedly |
abmoraz (abmoraz) wrote : | #5 |
- backtrace of plasma-desktop crash Edit (17.3 KiB, text/plain)
I forced another crash (not difficult, I can do it on demand by starting the plasma-desktop and clicking on pretty much any widget) and attached the backtrace.
Timeline:
- Started plasma-desktop from console
- crashed
- plasma-desktop restarted on its own
- the "KDE Crash Handler" ran on its own
- I generated the back trace
- while the backtrace was running (no other applications were clicked or used while it was generating), plasma-desktop crashed again.
- plasma-desktop auto-restarted again (backtrace still generating)
- plasma-desktop crashed again (backtrace still generating)
- plasma-desktop did NOT auto-restart this time
- backtrace completed (but gave the "you need to install debugging symbols" warning)
I have tried to install the debugging symbols no less than a dozen times. They do not seem to install. If you can point me towards a packed/repository that contains them, I will try and manually install them.
abmoraz (abmoraz) wrote : | #6 |
EDIT:
-- I have tried to install the debugging symbols no less than a dozen times. They do not seem to install. If you can point me towards a packed/repository that contains them, I will try and manually install them.
++ I have tried to install the debugging symbols no less than a dozen times. They do not seem to install. If you can point me towards a PACKAGE/repository that contains them, I will try and manually install them.
Changed in kde-workspace (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in kdebase-workspace: | |
importance: | Unknown → High |
abmoraz (abmoraz) wrote : | #67 |
After reading through the duplicate issue that was imported, I decided to disable "Notifications" from my "System Tray" widget in my main panel. Since doing that, I haven't crashed. It's only been 20 minutes, but prior to that, I would crash after ~20-30 seconds.
Seems like a short-term workaround is to disable that portion of the System Tray.
abmoraz (abmoraz) wrote : | #68 |
It's been almost 2 hours and no crashing since disabling "Notifications". If it's not the "Notifications" widget embedded in the "System Tray" widget, then it appears that it has something to do with how plasma-desktop handles that widget.
In KDE Bug Tracking System #311871, O-brian (o-brian) wrote : | #70 |
For the time being my method of "fixing" it is to disable the notifications applet. It's not optimal but keeps kwin from crashing at least.
In KDE Bug Tracking System #311871, valery (valerymamonov) wrote : | #71 |
Created attachment 79655
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
Plasma crashed again while Google Chrome-ing Internet. Steam client and Choqok are active too.
-- Backtrace (Reduced):
#7 0x000000328377761e in QPointer (p=..., this=0x7fff208f
#8 takeAt (i=1, this=0x307ae08) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00000032838bcd3f in QDeclarativeVis
#12 0x000000328378e54c in QDeclarativeVis
In KDE Bug Tracking System #311871, valery (valerymamonov) wrote : | #72 |
Created attachment 79662
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
I had used lastpass.com chrome extension (authorized in my lastpass account) and plasma had crashed
-- Backtrace (Reduced):
#7 0x000000328377761e in QPointer (p=..., this=0x7fff7a0e
#8 takeAt (i=1, this=0x2267208) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00000032838bcd3f in QDeclarativeVis
#12 0x000000328378e54c in QDeclarativeVis
abmoraz (abmoraz) wrote : | #69 |
It has been over 24hours now without crashes (where I was crashing in seconds before). I can confidently say that it was the "Notifications" that was causing the crashes for me. Disabling it from the System Tray Widget is a viable short-term workaround.
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #73 |
*** Bug 319309 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #74 |
*** Bug 319228 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #75 |
*** Bug 319205 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #76 |
*** Bug 319002 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #77 |
*** Bug 318963 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, valery (valerymamonov) wrote : | #79 |
Created attachment 79712
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
launched choqok application to view twitter feeds
-- Backtrace (Reduced):
#7 0x00000036bd37761e in QPointer (p=..., this=0x7fff62bb
#8 takeAt (i=1, this=0x35f5d98) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00000036bd4bcd3f in QDeclarativeVis
#12 0x00000036bd38e54c in QDeclarativeVis
In KDE Bug Tracking System #311871, pier (pier-andreit) wrote : | #80 |
on my opensuse 12.3 with KDE4.10.2 and graphics card = NVIDIA Quadro NVS 3100M and I'm using proprietary 304.88 nvidia drivers from the opensuse nvidia repo, crashes happens also in the other installation on the same pc with nouveau drivers.
after having read this issue I disabled notifications from the system tray, rebooted launched luckybackup and after few minutes the crash happened.
I was running only luckybackup, the crashes happens very often, one week ago I deleted the ~/.kde4 folder, the crashes stopped, but day by day the crashes becomes more frequents, now even just started kde and many times a day, kwin works ok I think becouse beclock works, alt>f2 works well becouse is the only way to interact wit the system
as the crash windows don't works well becouse it says me to click on the install packages but if I click there nothing happen, so I installed all the debug packages and created this backtrace hoping to be useful:
thanx, ciao, pier :-)
Application: Plasma Desktop Shell (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib64/
[Current thread is 1 (Thread 0x7f928287a780 (LWP 1705))]
Thread 20 (Thread 0x7f9261c09700 (LWP 1722)):
#0 0x00007f9281156964 in pthread_
#1 0x00007f92752f2307 in QTWTF::
#2 0x00007f92752f2339 in QTWTF::
#3 0x00007f9271c30764 in ?? () from /usr/X11R6/
#4 0x00007f9281152e0f in start_thread () from /lib64/
#5 0x00007f927fec87dd in clone () from /lib64/libc.so.6
Thread 19 (Thread 0x7f926036f700 (LWP 1723)):
#0 0x00007f9281156964 in pthread_
#1 0x00007f9276e5a2f0 in WTF::TCMalloc_
#2 0x00007f9276e5a329 in WTF::TCMalloc_
#3 0x00007f9271c30764 in ?? () from /usr/X11R6/
#4 0x00007f9281152e0f in start_thread () from /lib64/
#5 0x00007f927fec87dd in clone () from /lib64/libc.so.6
Thread 18 (Thread 0x7f921fa4c700 (LWP 1724)):
#0 0x00007f9281156964 in pthread_
#1 0x00007f9276bd8157 in JSC::BlockAlloc
#2 0x00007f9276e8181e in WTF::wtfThreadE
#3 0x00007f9271c30764 in ?? () from /usr/X11R6/
#4 0x00007f9281152e0f in start_thread () from /lib64/
#5 0x00007f927fec87dd in clone () from /lib64/libc.so.6
Thread 17 (Thread 0x7f92126d2700 ...
abmoraz (abmoraz) wrote : | #78 |
*sigh*
A bunch of KDE updates (including plasma-desktop) came through my system update this morning (via stable channel). I installed them; now the crashes have started all over again :(
Notifications are still off, but I am crashing repeatedly again.
In KDE Bug Tracking System #311871, valery (valerymamonov) wrote : | #81 |
Created attachment 79759
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
plasma crashed while I was watching SMPlayer
-- Backtrace (Reduced):
#7 0x000000387437761e in QPointer (p=..., this=0x7fff2393
#8 takeAt (i=4, this=0x38d2638) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00000038744bcd3f in QDeclarativeVis
#12 0x000000387438e54c in QDeclarativeVis
In KDE Bug Tracking System #311871, M-wege (m-wege) wrote : | #82 |
The crash seems to be reproducible when:
- I am in settings of control panel
and
- a notification appears.
In KDE Bug Tracking System #311871, themroc (rauchweihe) wrote : | #85 |
After upgrading to Kubuntu 13.04 with KDE 4.10.2 plasma-desktop crash randomly on all my Kubuntu PC's. Sometimes on one of the three Kubuntu PC plasma-desktop crashes before the upgrade too. But now plasma-desktop crashes more often and on one PC sometimes permanently.
It is not all times a reproducible action before the crash.
But often either I was before the crash with the Mouse in the lower right corner in the control panel, or often I had click before the crash in the lower right corner in the control panel "show hidden symbols". Or often after a pop up appears and ask for some input (e.g. password).
In KDE Bug Tracking System #311871, themroc (rauchweihe) wrote : | #86 |
Now I found an every time reproducible crash on one of my Kubuntu 13.04 64bit PCs with KDE 10.2:
Opening (clicking) this Desktop-File on Workspace due to an crash off plasma-desktop:
[Desktop Entry]
Icon=text-html
Type=Link
URL[$e]=http://
X-Ubuntu-
Note, the notification appears first after the automatic restart off plasma-desktop.
In KDE Bug Tracking System #311871, themroc (rauchweihe) wrote : | #87 |
(In reply to comment #73)
> Now I found an every time reproducible crash on one of my Kubuntu 13.04
> 64bit PCs with KDE 10.2:
>
> Opening (clicking) this Desktop-File on Workspace due to an crash off
> plasma-desktop:
>
> [Desktop Entry]
> Icon=text-html
> Type=Link
> URL[$e]=http://
> X-Ubuntu-
>
> Note, the notification appears first after the automatic restart off
> plasma-desktop.
Opening (clicking) this Desktop-File on Workspace due all times to an crash off plasma-desktop on all off my Kubuntu (KDE 4.10.2) PCs !
I add an error report.
In KDE Bug Tracking System #311871, themroc (rauchweihe) wrote : | #88 |
Created attachment 79800
plasma-desktop crashes opening an desktop file (see comment from themroc)
In KDE Bug Tracking System #311871, themroc (rauchweihe) wrote : | #89 |
Created attachment 79801
plasma-desktop crashes opening an desktop file (see comment from themroc)
In KDE Bug Tracking System #311871, sumski (hrvoje-senjan) wrote : | #90 |
*** Bug 319498 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, sumski (hrvoje-senjan) wrote : | #91 |
*** Bug 319586 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Ralf Jung (0tlwui8x-post-kj985rvy) wrote : | #92 |
That .desktop file works all right here. It opens the pdf document in Firefox, and that's it. Plasma is not even involved.
Which default browser do you use?
In KDE Bug Tracking System #311871, themroc (rauchweihe) wrote : | #93 |
(In reply to comment #79)
> That .desktop file works all right here. It opens the pdf document in
> Firefox, and that's it. Plasma is not even involved.
NO, my .desktop file open an animated gif.
> Which default browser do you use?
My default browser is Konqueror, but http://
But now I have detect, that this .desktop file doesn't lead to an crash on my Kubuntu 13.10 PC at work.
I think, plasma-desktop crashes if a notification and something else (opening a new application or a window or something else) should happens on same time.
In KDE Bug Tracking System #311871, Ralf Jung (0tlwui8x-post-kj985rvy) wrote : | #94 |
Sorry, of course I meant gif. I changed the default browser (could not get it to launch in Gwenview though), still not crashing here (KDE 4.10.3).
Kubuntu 13.10 is not yet released, in fact that's still 6 months ahead ;-)
In KDE Bug Tracking System #311871, Sparxz (sparxz) wrote : | #95 |
Created attachment 79818
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.2 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
Again, it was full screen Firefox.
This is the second time it has happened.
Plasma restarted Ok, and fairly quickly.
-- Backtrace (Reduced):
#6 0x00007fd3cb957bfe in QPointer (p=..., this=0x7fffc695
#7 takeAt (i=1, this=0x401f588) at ../../src/
#8 QDeclarativeRep
[...]
#10 0x00007fd3cba9caef in QDeclarativeVis
#11 0x00007fd3cb96eb2c in QDeclarativeVis
In KDE Bug Tracking System #311871, themroc (rauchweihe) wrote : | #96 |
(In reply to comment #81)
> Sorry, of course I meant gif. I changed the default browser (could not get
> it to launch in Gwenview though), still not crashing here (KDE 4.10.3).
Forgot my posts: Checking today: No crash on all off my PC.
So, yesterday it was a coincidence.
> Kubuntu 13.10 is not yet released, in fact that's still 6 months ahead ;-)
I'm sorry, I mean 13.04.
In KDE Bug Tracking System #311871, sumski (hrvoje-senjan) wrote : | #97 |
*** Bug 319691 has been marked as a duplicate of this bug. ***
themroc (rauchweihe) wrote : | #83 |
Please look also here:
themroc (rauchweihe) wrote : | #84 |
This bug only happens for me on 64 bit Kubuntu PC!
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #98 |
*** Bug 319765 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #99 |
*** Bug 319599 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #100 |
*** Bug 319831 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #101 |
*** Bug 319910 has been marked as a duplicate of this bug. ***
Luke Johnstone (john-wella) wrote : | #102 |
This happens to me when I use an HTML Plasmoid..
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #104 |
*** Bug 319989 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #105 |
*** Bug 319955 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Adam Maćkowiak (admc) wrote : | #106 |
Can developers do SOMETHING to fix this bug instead of marking duplicates?
In KDE Bug Tracking System #311871, O-brian (o-brian) wrote : | #107 |
So here's what I've found so far. My work laptop has an Intel chipset and a 64-bit install of Fedora 18. I've never had the notification widget crash the desktop there. My home computer has a nVidia card and was a 32-built version of Fedora 18 and was having crashes all the time. I reinstalled with a 64-built Fedora 18 build and still had the issues. The only way I've been able to keep kwin from dying is to disable the system tray notifications widget. I've read elsewhere it's a code path issue in Qt that KDE 4.10+ triggers that wasn't triggered in the past and could require a significant rewrite of Qt to fix. Also doesn't seem to happen on either system with compositing disabled, but I like my eye candy ;)
So for me, it seems to get triggered more often with kwin running compositing on nVidia cards than Intel cards. You guys having issues might try disabling the notification widget. Yeah, notifications can pop in the middle of the screen, but at least the don't bring kwin down with them.
In KDE Bug Tracking System #311871, Ralf Jung (0tlwui8x-post-kj985rvy) wrote : | #108 |
This bug is about a crash in plasma, not kwin. So I assumed you always meant plasma when you said kwin?
Also, I have an Intel card, and I saw this crash a few (3-5) times. It doesn't seem to be driver-dependent (and also, that wouldn't make much sense... whatever that means^^).
Adam Porter (alphapapa) wrote : | #103 |
$ acp plasma-desktop
plasma-desktop:
Installed: 4:4.10.
Candidate: 4:4.10.
Version table:
*** 4:4.10.
500 http://
100 /var/lib/
I upgraded from 4.10.2 to 4.10.3 and rebooted. Now plasma-desktop crashes as soon as it starts. I can't use KDE at all anymore. I should have known better than to upgrade. So much for "bug fixes only." This QML stuff is not ready for primetime. KDE should wait until it's stable before pushing it out on trusting users. Porting to fancy new stuff is not urgent or important. Stability is what matters most.
fsando (fsando) wrote : | #109 |
Ok I've been through a few days of this madness of constant crashes. I finally seem to have fixed it by changing permissions on everything in /var/tmp to 777.
I don't know why this works but there hasn't been even the slightest hint of an issue since (going for 1 day now)
fsando (fsando) wrote : | #110 |
Update:
The crashes continued
I have caught the last crash with strace:
$ strace -ff -tt -v -s 1024 -o odir/ofile.txt plasma-desktop
If the trace files are useful please let me know.
Adam Porter (alphapapa) wrote : | #111 |
fsando, if you can post the traces with the versions you have installed of all the relevant packages, go ahead. Also if you can post your ~/.kde/
In KDE Bug Tracking System #311871, sumski (hrvoje-senjan) wrote : | #112 |
*** Bug 321134 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #113 |
*** Bug 321138 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Futurepilot-0 (futurepilot-0) wrote : | #114 |
This may only be a workaround and not address the actual bug, but I removed ~/.kde/
In KDE Bug Tracking System #311871, sumski (hrvoje-senjan) wrote : | #115 |
*** Bug 321422 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Henry-duc64 (henry-duc64) wrote : | #116 |
Created attachment 80843
New crash information added by DrKonqi
plasma-desktop (4.10.4 "release 10") on KDE Platform 4.10.4 "release 569" using Qt 4.8.4
- What I was doing when the application crashed: Like most reporting this crash, using firefox (21.0)
distribution Opensuse 12.3
-- Backtrace (Reduced):
#6 0x00007f37efe97f99 in memmove (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at /usr/include/
#7 QListData::remove (this=0x4853d78, i=<optimized out>) at tools/qlist.cpp:347
#8 0x00007f37e35aec22 in takeAt (i=3, this=0x4853d78) at ../../src/
#9 QDeclarativeRep
[...]
#11 0x00007f37e36f3aef in QDeclarativeVis
In KDE Bug Tracking System #311871, Adam Maćkowiak (admc) wrote : | #117 |
(In reply to comment #96)
> This may only be a workaround and not address the actual bug, but I removed
> ~/.kde/
> resets all of the plasma settings back to the defaults. I reconfigured
> everything back to the way I had it and I have not had a crash since (3-4
> weeks). It's a big pain but it's better than having plasma-desktop crash
> almost every time I get a notification or switch windows.
Unfortunately that didn't helped me. I'm still getting crashes.
In KDE Bug Tracking System #311871, post-factum (post-factum) wrote : | #118 |
Created attachment 80867
New crash information added by DrKonqi
plasma-desktop (4.10.4) on KDE Platform 4.10.4 using Qt 4.8.4
- What I was doing when the application crashed:
Plasma-desktop crashed suddenly. Yes, Firefox was opened, but I think it's not related. Plasma can crash just while doing nothing.
-- Backtrace (Reduced):
#10 0x00007fa60eb71a9a in qt_assert_x (where=
#11 0x00007fa60021566d in takeAt (i=13, this=0x2349f38) at ../../include/
#12 QDeclarativeRep
[...]
#14 0x00007fa600365fef in QDeclarativeVis
#15 0x00007fa60022ae04 in QDeclarativeVis
ArthurGordon (nsl) wrote : | #119 |
After complete reinstall of 13.04 and adding some custom application, plasma-desktop crashes every time i log in.
same happens, if i restart plasma-desktop manually after the crash occured.
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_
[Current thread is 1 (Thread 0x7fc67a5a97c0 (LWP 4323))]
Thread 6 (Thread 0x7fc65a818700 (LWP 4383)):
#0 pthread_
#1 0x00007fc6732d4e77 in ?? () from /usr/lib/
#2 0x00007fc6732d4ea9 in ?? () from /usr/lib/
#3 0x00007fc66aa681b4 in ?? () from /usr/lib/
#4 0x00007fc66d9cff8e in start_thread (arg=0x7fc65a81
#5 0x00007fc679e91e1d in clone () at ../sysdeps/
Thread 5 (Thread 0x7fc657e29700 (LWP 4384)):
#0 pthread_mutex_lock (mutex=
#1 0x00007fc66d30c5c1 in g_mutex_lock () from /lib/x86_
#2 0x00007fc66d2cc90b in g_main_
#3 0x00007fc66d2cd0fe in ?? () from /lib/x86_
#4 0x00007fc66d2cd304 in g_main_
#5 0x00007fc676a71036 in QEventDispatche
#6 0x00007fc676a4138f in QEventLoop:
#7 0x00007fc676a41618 in QEventLoop::exec (this=this@
#8 0x00007fc676943410 in QThread::exec (this=this@
#9 0x00007fc676a22edf in QInotifyFileSys
#10 0x00007fc676945bec in QThreadPrivate:
#11 0x00007fc66aa681b4 in ?? () from /usr/lib/
#12 0x00007fc66d9cff8e in start_thread (arg=0x7fc657e2
#13 0x00007fc679e91e1d in clone () at ../sysdeps/
Thread 4 (Thread 0x7fc655ffd700 (LWP 4388)):
#0 pthread_
#1 0x00007fc674e6e585 in ?? () from /usr/lib/
#2 0x00007fc674e6e5d9 in ?? () from /usr/lib/
#3 0x00007fc66aa681b4 in ?? () from /usr/lib/
#4 0x00007fc66d9cff8e in start_thread (arg=0x7fc655ff
#5 0x00007fc679e91e1d in clone () at ../sysdeps/
Thread 3 (Thread 0x7fc6002d3700 (LWP 4392)):
#0 0x00007fc66d30c359 in ?? () from /lib/x86_
#1 0x00007fc66d30c5b9 in g_mutex_lock () from /lib/x86_
#2 0x00007fc66d2cc90b in g_main_
abmoraz (abmoraz) wrote : | #120 |
Ok, some more info on this bug:
I was experiencing this bug on my work computer (Intel dual processor with Intel Graphics card) and on my home computer (AMD quad core processor with ATI radeon 4xxx series card using the legacy drivers). I upgraded my ATI card to a radeon 6450 card to get off of the legacy drivers and still experienced the bug.
THEN
I bought a real big honkin' nVidia card (660t) to allow SLI and the bug just stopped. Didin't matter if I used opensource "nv" drivers or the proprietary drivers from nVidia. I can use widgets, notification, etc... with no issue. Has been that wy for almost 2 weeks now. Ever since I replaced the video card.
Seems like the issue maybe with widgets/workspace appearance and graphics accellerators. From the looks of all the other people submitting the bug, I saw a lot of ATI/AMD and Intel cards. I didn't notice if anyone was using nVidia.
ArthurGordon (nsl) wrote : | #121 |
@abmoraz (abmoraz) :
I'm actually using a nvidia graphics card.
01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [NVS 5100M] (rev a2)
ArthurGordon (nsl) wrote : | #122 |
Now i installed Kubuntu 12.04.2 LTS and made the upgrade to Kubutu 13.04.
After the first reboot the plasma-desktop ran without any crashes but began than to crash again.
Therefore i deleted the plasma config files "~/.kde/
In KDE Bug Tracking System #311871, Jacky Alciné (jackyalcine) wrote : | #123 |
Created attachment 80987
New crash information added by DrKonqi
plasma-desktop (4.10.4) on KDE Platform 4.10.4 using Qt 4.8.4
- What I was doing when the application crashed:
I was reading a web page in Chrome and noticed Plasma crashed. I'm assuming that something somewhere (most likely in the System Tray) didn't deref a pointer right and crashed the whole thing :(
-- Backtrace (Reduced):
#7 0x00007fb3b18f297e in QPointer (p=..., this=0x7fffc556
#8 takeAt (i=3, this=0x3837c88) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007fb3b1a3833f in QDeclarativeVis
#12 0x00007fb3b19092bc in QDeclarativeVis
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #124 |
*** Bug 322036 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Lastique (andysem) wrote : | #125 |
Created attachment 81026
New crash information added by DrKonqi
plasma-desktop (4.10.4) on KDE Platform 4.10.4 using Qt 4.8.2
- What I was doing when the application crashed:
I was typing a message in Skype. I did not notice any unusual behavior before the crash.
-- Backtrace (Reduced):
#7 0x00007f26c568012f in QPointer (p=..., this=0x7fffccb9
#8 takeAt (i=9, this=0x3ab5498) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f26c57c8f1f in QDeclarativeVis
#12 0x00007f26c5694e49 in QDeclarativeVis
In KDE Bug Tracking System #311871, valery (valerymamonov) wrote : | #126 |
Created attachment 81383
New crash information added by DrKonqi
plasma-desktop (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.5
- What I was doing when the application crashed:
I was adjusting Kmail and listening music via Amarok. At some time plasma had crashed. Maybe because of appeared notification.
-- Backtrace (Reduced):
#7 0x0000003e9ad6b942 in QPointer (p=..., this=0x7fffedad
#8 takeAt (i=4, this=0x3cc8250) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x0000003e9aeac98f in QDeclarativeVis
#12 0x0000003e9ad80acb in QDeclarativeVis
In KDE Bug Tracking System #311871, PCWinWeb (devlabn) wrote : | #127 |
Created attachment 81504
New crash information added by DrKonqi
plasma-desktop (4.10.5 "release 1") on KDE Platform 4.10.5 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
Idling on IRC - Konversation, Reading tweets, and browsing the web with firefox and preparing to write a blog post in Blogilo
- Custom settings of the application:
Icon theme is 'Iceglass 4.10.1', QtCurve color was 'Wonton Soup'.
-- Backtrace (Reduced):
#7 0x00007fefea946bfe in QPointer (p=..., this=0x7fffb71d
#8 takeAt (i=5, this=0x3825b38) at ../../src/
#9 QDeclarativeRep
[...]
#11 0x00007fefeaa8baef in QDeclarativeVis
#12 0x00007fefea95db2c in QDeclarativeVis
In KDE Bug Tracking System #311871, pier (pier-andreit) wrote : | #128 |
nomore crashes for me from a month and more...:-) :-) :-) :-) :-)
In KDE Bug Tracking System #311871, Sascha Manns (sascha-manns-h) wrote : | #129 |
Good to hear that. In my case i have many crashes each day. Next time i hanging me on the next bridge ;-). Is there any success in this bug?
In KDE Bug Tracking System #311871, Jacky Alciné (jackyalcine) wrote : | #130 |
Created attachment 81567
New crash information added by DrKonqi
plasma-desktop (4.10.5) on KDE Platform 4.10.97 using Qt 4.8.4
- What I was doing when the application crashed:
I was using Konsole in a maximized state as well as Chrome. It should be noted that I'm using QtCurve instead of Oxygen.
-- Backtrace (Reduced):
#7 0x00007f1064e7997e in QPointer (p=..., this=0x7fff0817
#8 takeAt (i=8, this=0x4068858) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f1064fbf33f in QDeclarativeVis
#12 0x00007f1064e902bc in QDeclarativeVis
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #131 |
*** Bug 322737 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #132 |
*** Bug 323076 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #133 |
*** Bug 323209 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Jacky Alciné (jackyalcine) wrote : | #134 |
Created attachment 81658
New crash information added by DrKonqi
plasma-desktop (4.10.97) on KDE Platform 4.10.97 using Qt 4.8.4
- What I was doing when the application crashed:
I was using Plasma with Firefox and Konsole and it crashed.
-- Backtrace (Reduced):
#7 0x00007f703168597e in QPointer (p=..., this=0x7fff9384
#8 takeAt (i=12, this=0x2a4abd8) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f70317cb33f in QDeclarativeVis
#12 0x00007f703169c2bc in QDeclarativeVis
In KDE Bug Tracking System #311871, Andreas K. Hüttel (dilfridge) wrote : | #135 |
Still present in 4.11.0
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #136 |
*** Bug 323583 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Adam Maćkowiak (admc) wrote : | #137 |
Is this fix included in 4.11?
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #138 |
Unfortunately, there is no fix. It is not even clear if the bug is in QtDeclarative, or in the notification applet. The only workaround for now (besides removing the notifications applet) would be to use the applet from KDE 4.9 version, which does not use QtDeclarative.
In KDE Bug Tracking System #311871, Adam Maćkowiak (admc) wrote : | #139 |
Maybe dev should rewrite notification applet to not use QtDeclarative?
In KDE Bug Tracking System #311871, Joshua Kugler (jkugler) wrote : | #140 |
Created attachment 81843
New crash information added by DrKonqi
plasma-desktop (4.11.00) on KDE Platform 4.11.00 using Qt 4.8.2
I was deleting about 6000 messages out of a mail box in KMail
-- Backtrace (Reduced):
#7 0x00007f5f3592812f in QPointer (p=..., this=0x7ffff93c
#8 takeAt (i=15, this=0x30c25c8) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f5f35a70f1f in QDeclarativeVis
#12 0x00007f5f3593ce49 in QDeclarativeVis
In KDE Bug Tracking System #311871, Lastique (andysem) wrote : | #141 |
Created attachment 81945
New crash information added by DrKonqi
plasma-desktop (4.11.00) on KDE Platform 4.11.00 using Qt 4.8.2
- What I was doing when the application crashed:
I was typing something in the kdesvn commit message window.
-- Backtrace (Reduced):
#6 __memmove_
#7 0x00007f0ba9ff8f59 in QListData::remove (this=0x3fbc4c8, i=<optimized out>) at /usr/include/
#8 0x00007f0babd2d153 in takeAt (i=1, this=0x3fbc4c8) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f0babe75f1f in QDeclarativeVis
In KDE Bug Tracking System #311871, Dhaumann (dhaumann) wrote : | #142 |
*** Bug 323558 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Casper-1 (casper-1) wrote : | #143 |
Created attachment 82051
New crash information added by DrKonqi
plasma-desktop (4.11.00) on KDE Platform 4.11.00 using Qt 4.8.2
- What I was doing when the application crashed:
Changing Photon`s setting from stereo mode to 5.1
-- Backtrace (Reduced):
#7 0x00007f4418d0312f in QPointer (p=..., this=0x7fff9b20
#8 takeAt (i=4, this=0x48ad0f8) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f4418e4bf1f in QDeclarativeVis
#12 0x00007f4418d17e49 in QDeclarativeVis
In KDE Bug Tracking System #311871, J-adam-b (j-adam-b) wrote : | #144 |
Created attachment 82127
New crash information added by DrKonqi
plasma-desktop (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.5
Plasma seems to crash at random times. There is no one activity that is suspect. Sometimes, I will be active on the computer. Othertimes, it's sitting idle. Most of the time, Plasma restarts itself. Every once in a while, I have to restart it manually.
-- Backtrace (Reduced):
#6 0x0000003b6bb6b8f2 in QPointer (p=..., this=0x7fffa7ac
#7 takeAt (i=1, this=0x273fd10) at ../../src/
#8 QDeclarativeRep
[...]
#10 0x0000003b6bcac52f in QDeclarativeVis
#11 0x0000003b6bb80a7b in QDeclarativeVis
In KDE Bug Tracking System #311871, Stephan Diestelhorst (syon) wrote : | #145 |
Created attachment 82134
New crash information added by DrKonqi
plasma-desktop (4.11.00) on KDE Platform 4.11.00 using Qt 4.8.2
- What I was doing when the application crashed:
Nothing too particular. Possibly email updated and the notifier popped open?
This is on a clean install of Kubuntu 12.04.3 with KDE 4.11 (from PPA) and then set up mail etc.
-- Backtrace (Reduced):
#6 __memmove_
#7 0x00007f00be46af59 in QListData::remove (this=0x44da888, i=<optimized out>) at /usr/include/
#8 0x00007f00c019f153 in takeAt (i=2, this=0x44da888) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f00c02e7f1f in QDeclarativeVis
In KDE Bug Tracking System #311871, Till Schäfer (till2-schaefer) wrote : | #146 |
Created attachment 82477
New crash information added by DrKonqi
plasma-desktop (4.11.1) on KDE Platform 4.11.1 using Qt 4.8.4
Still present on KDE 4.11.1 and Qt 4.8.4 (Gentoo Packages)
-- Backtrace (Reduced):
#6 __memmove_
#7 0x00007f51aeebbaf1 in QListData::remove (this=0x4a6ff38, i=<optimized out>) at /usr/include/
#8 0x00007f51a13f06fc in takeAt (i=1, this=0x4a6ff38) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f51a153b0ef in QDeclarativeVis
In KDE Bug Tracking System #311871, Matthias Mailänder (mailaender) wrote : | #147 |
Created attachment 82502
New crash information added by DrKonqi
plasma-desktop (4.11.1) on KDE Platform 4.11.1 using Qt 4.8.5
Seems to happen seldomly using KDE 4.11.1 on openSUSE 12.3
-- Backtrace (Reduced):
#7 0xb23a3355 in QPointer (p=..., this=0xbf8a6dfc) at ../../src/
#8 takeAt (i=1, this=0xb7a45f0) at ../../src/
#9 QDeclarativeRep
#10 0xb25031a2 in qt_static_metacall (_a=0xbf8a6f24, _id=6, _o=0xb7a4418, _c=<optimized out>) at .moc/release-
#11 QDeclarativeRep
In KDE Bug Tracking System #311871, Alex Fiestas (afiestas) wrote : | #148 |
*** Bug 325438 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Msirapian (msirapian) wrote : | #149 |
Created attachment 82679
New crash information added by DrKonqi
plasma-desktop (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.6
- What I was doing when the application crashed:
I was browsing the internet with Iceweasel. Plasma-desktop crashed (never happened before 4.10.5)
- Unusual behavior I noticed:
Usually, plasma-desktop restarts, but from time to time, it doesn't, I have to relaunch it manually.
-- Backtrace (Reduced):
#7 0x00007f45ecc07965 in QPointer (p=..., this=0x7fffe013
#8 takeAt (i=3, this=0x29f7780) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f45ecd48d2f in QDeclarativeVis
#12 0x00007f45ecc1caeb in QDeclarativeVis
In KDE Bug Tracking System #311871, Alex Fiestas (afiestas) wrote : | #150 |
#0 0x00007fffef8b23d9 in raise () from /usr/lib/libc.so.6
No symbol table info available.
#1 0x00007fffef8b37d8 in abort () from /usr/lib/libc.so.6
No symbol table info available.
#2 0x00007ffff174c1c4 in qt_message_output (msgType=
buf=0x3e829c8 "ASSERT failure in QList<T>::take: \"index out of range\", file ../../include/
at /home/afiestas/
No locals.
#3 0x00007ffff174c343 in qt_message(
msg=
buf = {static shared_null = {ref = {_q_value = 8328}, alloc = 0, size = 0, data = 0x7ffff1c5b158 <QByteArray:
ref = {_q_value = 695}, alloc = 0, size = 0, data = 0x7ffff1c5b178 <QByteArray:
#4 0x00007ffff174cb15 in qFatal (msg=0x7ffff19188f0 "ASSERT failure in %s: \"%s\", file %s, line %d") at /home/afiestas/
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7fffffff85c0, reg_save_area = 0x7fffffff8500}}
#5 0x00007ffff174bdc3 in qt_assert_x (where=
file=
No locals.
#6 0x00007ffff5a0c81c in QList<QPointer<
n = 0x1d912f0
t = {o = 0x1d912f0}
#7 0x00007ffff5a0c0be in QDeclarativeRep
at /home/afiestas/
item = 0x7fffffff8690
d = 0x1d913b0
#8 0x00007ffff5ba6329 in QDeclarativeRep
at .moc/debug-
_t = 0x1d912f0
#9 0x00007ffff18b25aa in QMetaObject:
at /home/afiestas/
receiver = 0x1d912f0
c = 0x1e1c5b0
last = 0x1e1c5b0
empty_argv = {0x0}
locker = {val = 8205712}
list = 0x1e1f720
sig...
In KDE Bug Tracking System #311871, Alex Fiestas (afiestas) wrote : | #151 |
#0 0x00007fffef8b23d9 in raise () from /usr/lib/libc.so.6
#1 0x00007fffef8b37d8 in abort () from /usr/lib/libc.so.6
#2 0x00007ffff174c1c4 in qt_message_output (msgType=
buf=0x3e829c8 "ASSERT failure in QList<T>::take: \"index out of range\", file ../../include/
at /home/afiestas/
#3 0x00007ffff174c343 in qt_message(
msg=
#4 0x00007ffff174cb15 in qFatal (msg=0x7ffff19188f0 "ASSERT failure in %s: \"%s\", file %s, line %d") at /home/afiestas/
#5 0x00007ffff174bdc3 in qt_assert_x (where=
file=
#6 0x00007ffff5a0c81c in QList<QPointer<
#7 0x00007ffff5a0c0be in QDeclarativeRep
at /home/afiestas/
#8 0x00007ffff5ba6329 in QDeclarativeRep
at .moc/debug-
#9 0x00007ffff18b25aa in QMetaObject:
at /home/afiestas/
#10 0x00007ffff5baaaa7 in QDeclarativeVis
#11 0x00007ffff5a2700f in QDeclarativeVis
at /home/afiestas/
#12 0x00007ffff5bab060 in QDeclarativeVis
at .moc/debug-
#13 0x00007ffff18b25aa in QMetaObject:
at /home/afiestas/
#14 0x00007ffff5b99691 in QListModelInter
#15 0x00007ffff5967a59 in QDeclarativeLis
#16 0x00007ffff5b97786 in QDeclarativeLis
In KDE Bug Tracking System #311871, alvar (alvarq) wrote : | #152 |
Created attachment 82759
New crash information added by DrKonqi
plasma-desktop (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.4
Plasma-Desktop crashes about every two hours . Tried with open source Radeon driver or proprietary fglrx; the behaviour remains the same.
Applications that were open: Firefox, Thunderbird, Konsole.
Additional logging information:
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter:
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter:
QPainter::end: Painter not active, aborted
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x381846e
plasmapackage:
plasmapackage:
plasmapackage:
KCrash: Attempting to start /usr/bin/
-- Backtrace (Reduced):
#7 0x00007fa9ed4a697e in QPointer (p=..., this=0x7fff696e
#8 takeAt (i=2, this=0x4874928) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007fa9ed5ec33f in QDeclarativeVis
#12 0x00007fa9ed4bd2bc in QDeclarativeVis
In KDE Bug Tracking System #311871, themroc (rauchweihe) wrote : | #153 |
For me the last crash from Plasma-Desktop is long time passing. So, for me is the Bug fixed.
In KDE Bug Tracking System #311871, Nico-kruber (nico-kruber) wrote : | #154 |
for me this still happens occasionally (KDE 4.11.2)
very rarely, plasma-desktop even fails to restart itself automatically (which normally happens when DrKonqi is started)
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #155 |
*** Bug 326022 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #156 |
*** Bug 326122 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Byron Hawkins (bhron) wrote : | #157 |
Created attachment 82993
New crash information added by DrKonqi
plasma-desktop (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.4
- What I was doing when the application crashed: I was not actually doing anything, though Evolution was retrieving new messages from my imap account, and that is the application that crashed. All other apps are still running normally.
-- Backtrace (Reduced):
#6 0x00007f0cf8b45971 in QPointer (p=..., this=0x7fff85a5
#7 takeAt (i=3, this=0x2dd3a08) at ../../include/
#8 QDeclarativeRep
[...]
#10 0x00007f0cf8c8b33f in QDeclarativeVis
#11 0x00007f0cf8b5c2bc in QDeclarativeVis
In KDE Bug Tracking System #311871, Arnaud Frézet (arnaudfrezet) wrote : | #158 |
Created attachment 83026
New crash information added by DrKonqi
plasma-desktop (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.4
- What I was doing when the application crashed:
I was using Pidgin. I had Chromium, Firefox, phpStorm, MysqlWorkbench et Pidgin chat window opened. Then Plasma crashed, and then it restarted
-- Backtrace (Reduced):
#8 0xb6be9db3 in QPointer (p=..., this=0xbfe7768c) at ../../include/
#9 takeAt (i=18, this=<optimized out>) at ../../include/
#10 QDeclarativeRep
#11 0xb6d43d52 in QDeclarativeRep
[...]
#13 0xb6d4812d in QDeclarativeVis
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #159 |
*** Bug 326496 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #160 |
*** Bug 326532 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #161 |
*** Bug 326540 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #162 |
Hi, Albert found a possible cause and a way to work around this issue, see https:/
Since this is a pure QML patch, no compilation is required, so please, if possible, test it. As far as I understand, frequent simultaneously appearing/
In KDE Bug Tracking System #311871, Albert Astals Cid (aacid) wrote : | #163 |
Git commit 148dea659dbe358
Committed on 28/10/2013 at 23:16.
Pushed by aacid into branch 'KDE/4.11'.
Fix crash when removing a notification while we are adding one
Reading https:/
78 0x00007f4eff8c5ffb in QDeclarativeLis
and then we end up reentring and doing
16 0x00007f4eff8c737f in QDeclarativeLis
Some of the stuff that depends on the QDeclarativeLis
Acked by Aaron J. Seigo
REVIEW: 113471
FIXED-IN: 4.11.3
M +2 -1 plasma/
M +3 -0 plasma/
http://
Changed in kdebase-workspace: | |
status: | Unknown → Fix Released |
In KDE Bug Tracking System #311871, Guntur-purba-siboro (guntur-purba-siboro) wrote : | #164 |
Created attachment 83196
New crash information added by DrKonqi
plasma-desktop (4.10.5 "release 1") on KDE Platform 4.10.5 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
- I am opening many application, and also wine application (chat messenger LINE)
- I am writing a document.
- Custom settings of the application:
I am using a dark theme.
Note : I often feel that the crash is repeating itself at a certain interval of time regardless of the number and what application I used.
-- Backtrace (Reduced):
#6 0x00007f9b5091fbfe in QPointer (p=..., this=0x7fff9d1b
#7 takeAt (i=1, this=0x3744238) at ../../src/
#8 QDeclarativeRep
[...]
#10 0x00007f9b50a64aef in QDeclarativeVis
#11 0x00007f9b50936b2c in QDeclarativeVis
In KDE Bug Tracking System #311871, Adam Maćkowiak (admc) wrote : | #165 |
Finally! After 10 months devs fixed this annoying bug by adding four lines of code! Good to see it fixed because I already started considering migration to another, more stable DE.
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #166 |
*** Bug 326914 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Cédric Bellegarde (gnumdk) wrote : | #167 |
*** Bug 326370 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, adaptee (adaptee) wrote : | #168 |
*** Bug 327250 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #169 |
Bad news: bug 327770 is against KDE 4.11.3. But to be sure it was not with old plasma still running after update, let's wait if there are more bug reports.
In KDE Bug Tracking System #311871, Asraniel (asraniel) wrote : | #170 |
Created attachment 83640
New crash information added by DrKonqi
plasma-desktop (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.4
- What I was doing when the application crashed:
Nothing in particular. Just a random desktop crash
-- Backtrace (Reduced):
#7 0x00007f1493a45185 in QPointer (p=..., this=0x7fff0a0f
#8 takeAt (i=5, this=0x384dc88) at ../../include/
#9 QDeclarativeRep
[...]
#11 0x00007f1493b84caf in QDeclarativeVis
#12 0x00007f1493a5a32b in QDeclarativeVis
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #171 |
*** Bug 328095 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #172 |
*** Bug 328207 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #311871, Christoph-maxiom (christoph-maxiom) wrote : | #173 |
*** Bug 328410 has been marked as a duplicate of this bug. ***
Rohan Garg (rohangarg) wrote : | #174 |
Fixed in Trusty and Saucy Updates
Changed in kde-workspace (Ubuntu): | |
status: | Confirmed → Fix Released |
In KDE Bug Tracking System #311871, Cfeck (cfeck) wrote : | #175 |
*** Bug 352557 has been marked as a duplicate of this bug. ***
Application: plasma-desktop (0.4)
KDE Platform Version: 4.9.90
Qt Version: 4.8.3
Operating System: Linux 3.7.0-7-generic x86_64
Distribution: Ubuntu 12.10
-- Information about the crash:
- What I was doing when the application crashed: was browsing web using firefox web browser nothing more nothing less
The crash can be reproduced some of the time.
-- Backtrace: 64-linux- gnu/libthread_ db.so.1" .
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_
[Current thread is 1 (Thread 0x7f640dcaf780 (LWP 2087))]
Thread 4 (Thread 0x7f63ef33b700 (LWP 2088)): cond_wait@ @GLIBC_ 2.3.2 () at ../nptl/ sysdeps/ unix/sysv/ linux/x86_ 64/pthread_ cond_wait. S:162 x86_64- linux-gnu/ libQtScript. so.4 x86_64- linux-gnu/ libQtScript. so.4 b700) at pthread_ create. c:308 unix/sysv/ linux/x86_ 64/clone. S:112
#0 pthread_
#1 0x00007f6407280cd7 in ?? () from /usr/lib/
#2 0x00007f6407280d09 in ?? () from /usr/lib/
#3 0x00007f640192ce9a in start_thread (arg=0x7f63ef33
#4 0x00007f640d594cbd in clone () at ../sysdeps/
#5 0x0000000000000000 in ?? ()
Thread 3 (Thread 0x7f63e0faa700 (LWP 2091)): unix/sysv/ linux/poll. c:87 64-linux- gnu/libglib- 2.0.so. 0 context_ iteration () from /lib/x86_ 64-linux- gnu/libglib- 2.0.so. 0 rGlib:: processEvents (this=0x7f63dc0 008c0, flags=...) at kernel/ qeventdispatche r_glib. cpp:426 :processEvents (this=this@ entry=0x7f63e0f a9dd0, flags=...) at kernel/ qeventloop. cpp:149 a9dd0, flags=...) at kernel/ qeventloop. cpp:204 qthread. cpp:501 temWatcherEngin e::run (this=0x30a62c0) at io/qfilesystemw atcher_ inotify. cpp:248 :start (arg=0x30a62c0) at thread/ qthread_ unix.cpp: 338 a700) at pthread_ create. c:308 unix/sysv/ linux/x86_ 64/clone. S:112
#0 0x00007f640d589303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/
#1 0x00007f640122dd84 in ?? () from /lib/x86_
#2 0x00007f640122dea4 in g_main_
#3 0x00007f640a229c16 in QEventDispatche
#4 0x00007f640a1fa2bf in QEventLoop:
#5 0x00007f640a1fa548 in QEventLoop::exec (this=0x7f63e0f
#6 0x00007f640a0fbb10 in QThread::exec (this=<optimized out>) at thread/
#7 0x00007f640a1da9af in QInotifyFileSys
#8 0x00007f640a0feaec in QThreadPrivate:
#9 0x00007f640192ce9a in start_thread (arg=0x7f63e0fa
#10 0x00007f640d594cbd in clone () at ../sysdeps/
#11 0x0000000000000000 in ?? ()
Thread 2 (Thread 0x7f63d97f0700 (LWP 2094)): 64-linux- gnu/libglib- 2.0.so. 0 64-linux- gnu/libglib- 2.0.so. 0 context_ prepare () from /lib/x86_ 64-linux- gnu/libglib- 2.0.so. 0 64-linux- gnu/libglib- 2.0.so. 0 context_ iteration () from /lib/x86_ 64-linux- gnu/libglib- 2.0.so. 0 rGlib:: processEvents (this=0x7f63d40 008c0, flags=...) at kernel/ qeventdispatche r_glib. cpp:426 :processEvents (this=this@ entry=0x7f63d97 efdd0, flags=...) at kernel/ qeventloop. cpp:149 efdd0, flags=...) at kernel/ qeventloop. cpp:204
#0 0x00007f640126a9ba in ?? () from /lib/x86_
#1 0x00007f640126ac29 in g_mutex_lock () from /lib/x86_
#2 0x00007f640122d623 in g_main_
#3 0x00007f640122dcab in ?? () from /lib/x86_
#4 0x00007f640122dea4 in g_main_
#5 0x00007f640a229c16 in QEventDispatche
#6 0x00007f640a1fa2bf in QEventLoop:
#7 0x00007f640a1fa548 in QEventLoop::exec (this=0x7f63d97
#8 0x00007f640a0fbb10 in QThre...