Bug 380014

Summary: QObject::startTimer: Timers cannot be started from another thread
Product: [Plasma] plasmashell Reporter: Hering2007
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde, notuxius, simonandric5
Priority: NOR Keywords: triaged
Version: 5.9.5   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: plasma-org.kde.plasma.desktop-appletsrc
comment-5-plasma-org.kde.plasma.desktop-appletsrc

Description Hering2007 2017-05-19 15:00:01 UTC
I am seeing some 

"plasmashell[848]: QObject::startTimer: Timers cannot be started from another thread"

in my journal. Not sure why it is happening though or what might cause it.
Comment 1 David Edmundson 2017-05-25 11:54:16 UTC
Can you include your plasma-framework version and if this still happens.

Also can you attach your ~/.config/plasma-org.kde.plasma.desktop-appletsrc files 

Then reset this bug status to unconfirmed.

Thanks
Comment 2 Hering2007 2017-06-01 08:05:57 UTC
The version is 5.9.5 and yes it still happens from time to time. The file is attached.

What I realized is that the file contains lots of old stuff which doesn't exist anymore like shortcuts, wallpapers and even widgets...
Comment 3 Hering2007 2017-06-01 08:06:25 UTC
Created attachment 105813 [details]
plasma-org.kde.plasma.desktop-appletsrc
Comment 4 Hering2007 2017-06-01 08:07:25 UTC
Changing status
Comment 5 Alexander Mentyu 2017-08-24 09:16:48 UTC
Can't reproduce/no similar log info for me in:

Distribution: KDE neon Developer Edition Unstable Branches
KDE Plasma Version: 5.10.90
KDE Frameworks Version: 5.37.0
Qt Version: 5.9.1
Kernel Version: 4.10.0-32-generic
Comment 6 Alexander Mentyu 2017-08-24 09:18:27 UTC
Created attachment 107494 [details]
comment-5-plasma-org.kde.plasma.desktop-appletsrc
Comment 7 Christoph Feck 2017-09-20 00:06:11 UTC
Could you check if removing ThermalMonitor from https://store.kde.org/p/998915/ helps to resolve this issue?
Comment 8 Christoph Feck 2017-10-05 00:44:02 UTC
If you can provide the information requested in comment #7, please add it.
Comment 9 Christoph Feck 2017-10-18 11:13:39 UTC
To further investigate this issue, KDE developers need the information requested in comment #7. If you can provide it, or need help with finding that information, please add a comment.
Comment 10 Andrew Crouthamel 2018-09-28 02:41:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Andrew Crouthamel 2018-10-28 03:25:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!