https://bugzilla.novell.com/show_bug.cgi?id=824805 https://bugzilla.novell.com/show_bug.cgi?id=824805#c0 Summary: kde 4.10.3 'release 1' very slow for essentially all applications Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: kpdere@verizon.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=544025) --> (http://bugzilla.novell.com/attachment.cgi?id=544025) launch of gwenview from a shell console User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 I recently upgraded my KDE distribution from 4.10.2 to 4.10.3. Now, launching anything is very slow. Kmail is very slow in just about all aspects. Clicking a web link in Thunderbird should display that page in Chrome but that takes about forever even when Chrome has already been launched. The whole desktop is nearly unworkable. CPU load is minimal Reproducible: Always Steps to Reproduce: 1. Click on the Kmail icon on the dashboard 2. Run Gwenview either from the launcher for from a shell 3. Launch akregator form the dashboard Actual Results: The application is slow to launch. When kmail is very slow toaccess email, akregator is equally slow. Expected Results: Wait, wait , wait If kmail does not find a certificate for the server of some email information, it will continue sending out messages asking what to do for a long time (20 minutes or so, depending) The messages from the gwenview launch suggest that it is a KDE problem. The odd names for the disk drives are a problem that originated with some version of opensuse from long in the past. I have been using suse/opensuse since version 8.x the fonts bit is something I see a lot of but does not cause any problems Under KDE 4.10.2, I had no such problems. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.