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. ***
38 comments hidden Loading more comments | view all 175 comments |
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 |
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 |
129 comments hidden Loading more comments | view all 175 comments |
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...