Bug 368757

Summary: quanta+ hangs at startup with 100% CPU-usage
Product: [I don't know] kde Reporter: Martin Wolf <mw>
Component: generalAssignee: Unassigned bugs <unassigned-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: grave CC: cfeck
Priority: NOR    
Version First Reported In: 4.14.1   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Martin Wolf 2016-09-13 19:12:19 UTC 
quanta+ worked fine until my Fedora 21. Now I upgraded to Fedora 24 ... and now quanta+ is not starting anymore. Only the splash-screen is visible and it hangs with 25% CPU-Usage (I've got a Core-i5-2500 with 4 kernels).
Because I updated the system from Fedora 21, I too another, fresh harddisk and installed a complete new Fedora 24: Same here.
(btw: Where is the component kdewebdev/quanta here in this bugtracker?)
Best regards
Martin

Reproducible: Always

Steps to Reproduce:
1. Start quanta+
2.
3.

Actual Results:  
It hangs/freezes at startup

Expected Results:  
Should start ;-)

$ kde-open --version:
Qt: 4.8.7
KDE: 4.14.22
KIO-Client: 2.0

$ quanta
kbuildsycoca running...
DCOP Cleaning up dead connections.
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:186
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:187
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:188
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:189
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:190
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:191
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:192
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:193
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:194
Invalid entry (empty key) at /usr/share/apps/quanta/doc/php.docrc:224
Comment 1 Christoph Feck 2016-09-14 16:02:37 UTC 
Quanta+ is long unmaintained. Are you sure recent Fedora offers packages for Quanta+? If yes, you should report this to the bug tracker of your distribution.