Bug 350255

Summary: KMix, Owncloud infinite loop on start
Product: [Frameworks and Libraries] frameworks-frameworkintegration Reporter: Andrea Scarpino <scarpino>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED DUPLICATE    
Severity: grave CC: jjm, kde
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: KMix console output

Description Andrea Scarpino 2015-07-15 17:14:26 UTC 
When starting kmix I get an "infinite loop", cpu goes to 100% and after some minute the kernel kills it.



Reproducible: Always

Steps to Reproduce:
1. Start KMix

Actual Results:  
CPU goes to 100%


KMix 15.04.3
KDE Frameworks 5.12.0
Qt 5.5.0
Comment 1 Andrea Scarpino 2015-07-15 17:14:46 UTC 
Created attachment 93601 [details]
KMix console output
Comment 2 Andrea Scarpino 2015-08-07 00:23:16 UTC 
This seems due to the fact 'statusnotifierwatcher' is disabled. If I enabled it, then KMix starts.

This also happens with owncloud. It's probably some KDE Frameworks thing.
Comment 3 David Edmundson 2015-08-07 13:49:29 UTC 
> This seems due to the fact 'statusnotifierwatcher' is disabled. If I enabled it, then KMix starts.

So did you disable it?
Comment 4 Andrea Scarpino 2015-08-07 18:13:50 UTC 
(In reply to David Edmundson from comment #3)
> So did you disable it?

Yes, and I do expect the applications still work (without systray of course).
Comment 5 David Edmundson 2015-08-08 01:08:35 UTC 
Sure, I was just seeing if it was a bug many people are likely to encounter or not.
Comment 6 Andrea Scarpino 2015-08-31 16:21:14 UTC 
Update, with KMix 15.08.0 and KDE Frameworks 5.13.0 the log is changed, I get this message infinite times:
[kmix(4276)/(default) unknown: QSystemTrayIcon::setVisible: No Icon set
Comment 7 Andrea Scarpino 2015-09-19 06:40:47 UTC 
This also happens when you don't have plasma-workspace installed (because the statusnotifierwatcher doesn't exist).
Comment 8 Jonathan Marten 2015-09-19 07:19:45 UTC 
Marking as duplicate of later bug, because backtrace/analysis there.

*** This bug has been marked as a duplicate of bug 350785 ***