Bug 196399 - KDE 4.3 beta takes 4x the time to start than 4.2.x
Summary: KDE 4.3 beta takes 4x the time to start than 4.2.x
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-13 22:13 UTC by Guillermo Belli
Modified: 2009-11-26 17:13 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guillermo Belli 2009-06-13 22:13:44 UTC
Version:            (using KDE 4.2.90)
OS:                Linux
Installed from:    Ubuntu Packages

I'm running Kubuntu 9.04 AMD64, kernel 2.6.30 and KDE 4.3 beta2 (4.2.90) from Kubuntu ppa packages.

Since I installed the 4.3 beta, KDE takes like 4x the time (compared to KDE 4.2.x) to finish loading plasma and widgets on the panel, and for the desktop to be responsive. The active widgets are: application launcher (classic), task manager, system tray, klipper, kmix, device notifier, battery monitor, digital clock and NM widget.

Also, on startup, I see a checkered pattern on 1/3 of the desktop. Desktop effects are disabled.
Comment 1 Aaron J. Seigo 2009-06-13 22:53:21 UTC
> KDE takes like 4x the time

if you `kquitapp plasma-desktop` and then `plasma-desktop` does it start up quickly or take a very long time?

if that takes a very long time:

* are you using per-virtual-desktop activities?

* can you remove the widgets one by one and repeat the quit/start to see which one (if any) is causing the start up drag

> Also, on startup, I see a checkered pattern on 1/3 of the desktop.

because ksplash isn't running?
Comment 2 Guillermo Belli 2009-06-14 00:06:32 UTC
Doing 'kquitapp plasma-desktop' and then 'plasma-desktop' makes plasma start a lot faster than when starting a KDE session, and it takes 6 seconds, which is still not blazing fast. Here's the console output of 'plasma-desktop':

QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
"KConfigIni: In file /usr/share/kubuntu-default-settings/kde4-profile/default/share/config/kickoffrc, line 3: " Invalid entry (missing '=')
Object::connect: No such slot TaskManager::TaskManager::configureStartup()
Object::connect:  (sender name:   'KDirWatch-2')
Object::connect: No such slot TaskManager::TaskManager::configureStartup()
Object::connect:  (sender name:   'KDirWatch-2')
Object::connect: No such slot TaskManager::TaskManager::configureStartup()
Object::connect:  (sender name:   'KDirWatch-2')
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 18 (X_ChangeProperty)
  Resource id:  0x0
QGraphicsGridLayout::itemAt: invalid index 0
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 7
Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection


When the panel appears, all widgets appear instantly with it. When starting a fresh KDE session, the panel appears, and the widgets appear slowly one by one. I'll do the one by one widget startup later and report back.

And yes, ksplash is not active.
Comment 3 Luis Silva 2009-06-14 13:56:40 UTC
I followed the suggestion to finding this bug. 
* I created a new user and logged in (35 seconds). 
* Launch konsole and stop plasma with kquitapp plasma (0seconds)
* Start plasma from the terminal (16 seconds)
* remove folderview stop and start plasma (14 seconds)
* I get nearly a 1 second improve for each plasmoid removed from the pannel except the "device notifier" plasmoid (12s -> 4s)
* plasma with no pannels and no plasmoids takes 1s to start
* added the device notiffier to the desktop and restart plasma (9s)
in this last case I also get he following errors on the command line:

Unrecognized character: /                                                                                      
Unrecognized character: /                                                                                      
ERROR: syntax error  

I am using kubuntu packages for karmic (kde 4.3 beta 2)
Comment 4 Alessandro Guido 2009-06-15 23:34:37 UTC
I too noticed first time login to be a lot slower. On my system there is a ~10 seconds delay of complete inactivity between the loading of the desktop/bakckground/panels and the "autostarting" of configured applications, like kmix and yakuake. This delay does not happen if I logout and login again.

Like Guillermo, I noticed the following message in the logs, maybe it's worth investigating:
Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection
Comment 5 Aaron J. Seigo 2009-06-16 00:07:51 UTC
"On my system there is a ~10 seconds delay of complete inactivity between the loading of the desktop/bakckground/panels and the "autostarting" of configured applications,"

could be any number of things, really; it's most likely something on d-bus causing a blockage in synchronous calls in kded4. i wonder if it's a knotify related issue? i had those at one point...

"Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while
parsing introspection"

this is harmless, but is caused by something in libkdeui.
Comment 6 G Cohen 2009-06-26 10:13:38 UTC
Same problem here, startup is really slow. I have not added any widgets to the desktop or panels, but startup is painfully slow, the animation in KSplash is not smooth and the after the K icon appears it takes another ~5 seconds until the desktop is shown. 
Just a hunch, and perhaps not related at all, but unlike in KDE 4.2 the Ksplash screen doesn't fade into the desktop. My feeling is it might try to fade into the desktop and waits for some time-out before it just loads the desktop anyway.
Here is my output of plasma-desktop:
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
"KConfigIni: In file /usr/share/kubuntu-default-settings/kde4-profile/default/share/config/kickoffrc, line 3: " Invalid entry (missing '=')
Object::connect: No such slot TaskManager::TaskManager::configureStartup()
Object::connect:  (sender name:   'KDirWatch-3')
Object::connect: No such slot TaskManager::TaskManager::configureStartup()
Object::connect:  (sender name:   'KDirWatch-3')
Object::connect: No such slot TaskManager::TaskManager::configureStartup()
Object::connect:  (sender name:   'KDirWatch-3')
QGraphicsGridLayout::itemAt: invalid index 0
QGraphicsGridLayout::itemAt: invalid index 2
QGraphicsGridLayout::itemAt: invalid index 7
Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection
Comment 7 Aaron J. Seigo 2009-06-27 12:02:33 UTC
"* added the device notiffier to the desktop and restart plasma (9s)"

i looked into this tonight and found at least one of the major culprits (the hotplug engine) and managed to eliminate 80%+ of the time spent in it at startup. the notifier wasn't taking 9s on my system, but it was taking longer than it should.

if any of you are compiling from source and using trunk or the 4.3 branch from svn, try updating kdebase/workspace/plasma/dataengines/hotplug/ and see if that helps any.
Comment 8 Guillermo Belli 2009-06-30 01:46:54 UTC
Well, I finally had the time to time startup removeing all widgets and then adding one by one.

I removed all, except one panel, and the best startup time from kdm login screen to desktop being responsive (that is being able to use alt+f2 or any other keyboard shortcut, and autostarted apps start to load) was ~11 seconds.

The most significant difference was made by "System Tray", which added a little over one second.

With all the widgets, maximum start time is around ~14 seconds from the kdm login screen to desktop being responsive.
Comment 9 Guillermo Belli 2009-07-03 17:15:04 UTC
Aaron: Did the svn changes make it into KDE 4.3 RC1? I ask because startup performace is just as bas as with the beta 2 (~14 seconds).
Comment 10 Luis Silva 2009-07-11 23:31:41 UTC
After upgrading to kde 4.3 rc2 plasma takes much less time to start. It is still not as fast as 4.2 but no longer a minute. Starting plasma from a terminal now takes 9 seconds where it used to take 16 (see above).
Comment 11 S. Burmeister 2009-08-08 00:03:33 UTC
I see this in KDE 4.3 final. Starting plasma-desktop from the konsole takes ~40 seconds. There are some long pauses of ~5-10 seonds, which I have marked in the output.

kquitapp plasma-desktop:
<unknown program name>(4750)/: "Application plasma could not be found using service org.kde.plasma and path /MainApplication."
:~> plasma-desktop   
                                            
QDBusObjectPath: invalid path ""                                                   
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout    

<PAUSE>

Unrecognized character: /                                                          
Unrecognized character: /                                                          
ERROR: syntax error

<PAUSE>

rabauke@linux-fpxk:~> Initialize default_framework extension.
Initialize libxml2_xml_parser extension.
Initialize dbus_script_class extension.
Initialize default_options extension.
Initialize qtwebkit_browser_element extension.
Initialize qt_system_framework extension.
Initialize qt_edit_element extension.
Initialize gst_audio_framework extension.
Initialize gst_video_element extension.
Initialize linux_system_framework extension.
Initialize qt_xml_http_request extension.
Initialize google_gadget_manager extension.
Initialize analytics_usage_collector extension.
Initialize smjs_script_runtime extension.
Warning: missing symbol in libmozjs.so: JS_TriggerAllOperationCallbacks
Initialize qt_script_runtime extension.
Register smjs_script_runtime extension.
Register qt_script_runtime extension.

<PAUSE>

Register default_framework extension.
Register qtwebkit_browser_element extension, using name "_browser".
Register qt_system_framework extension.
Register qt_edit_element extension.
Register gst_audio_framework extension.
Register gst_video_element extension.
Register linux_system_framework extension.
Register dbus_script_class extension.


<PAUSE>


main.js:38: Old JScript grammar: options.defaultValue(names[i]) =... Converted to putDefaultValue()
main.js:40: Old JScript grammar: options.defaultValue(kPetCount) =... Converted to putDefaultValue()
main.js:41: Old JScript grammar: options.defaultValue(kAbandonCount) =... Converted to putDefaultValue()
main.js:245: Old JScript grammar: options(names[index]) =... Converted to putValue()
main.js:253: Old JScript grammar: options(kPetCount) =... Converted to putValue()
main.js:261: Old JScript grammar: options(kAbandonCount) =... Converted to putValue()

<PAUSE>

QColor::setNamedColor: Unknown color name '4279505682'
QTextHtmlParser::applyAttributes: Unknown color name '4279505682'
Comment 12 Beat Wolf 2009-08-25 10:57:45 UTC
After some research i found out that you use the google gadgets flower pot.

Could you also, like other before, try to remove all plasmoids and read one by one and measure startup time? 40 seconds seems a little excessive..
Comment 13 S. Burmeister 2009-08-25 11:17:06 UTC
It's not the flower pot it's bug 203058
Comment 14 Beat Wolf 2009-08-25 11:48:01 UTC
ok great. so is the startup time for 4.3 back to normal? i know that its not impresingly fast, but is it at least back to the 4.2 level? if yes this bugreport can be closed
Comment 15 Beat Wolf 2009-11-26 15:18:33 UTC
please reopen if this is still a valid bug with 4.3.3
Comment 16 Guillermo Belli 2009-11-26 17:13:31 UTC
I´m now using KDE 4.3.3 (Kubuntu 9.10), and it loads very fast. I would say this bug is now fixed.

Thank you.