[Bug 204757] Start-up delay when no Internet access
mkkot
marcinkocur at op.pl
Mon Aug 24 21:14:16 BST 2009
https://bugs.kde.org/show_bug.cgi?id=204757
mkkot <marcinkocur at op.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |NEW
Resolution|WAITINGFORINFO |
Ever Confirmed|0 |1
--- Comment #3 from mkkot <marcinkocur op pl> 2009-08-24 22:14:13 ---
Hi again, sorry for delay, this time mine delay, not kde's ;]
It's a new installation, I have set few things here but wasn't making big
changes within desktop yet, so I have only one icon cointainer with home
directory and trash bin and on the panel standard applets + logging out button.
Another interesting thing, I also needed to set NO splash screen in
systemsettings because of ANOTHER delay (jupp, that's a second bug). This delay
takes place independently of the bug reported above. It happens at the moment
when the desktop is just shown (desktop = plasmoids + wallper + panel) while
starting the environment (please remember: splash screen set to none). And so,
desktop is shown, all buttons and icons are operable, I wait about 5 seconds
with no disc activities and then in the tray there are appearing: notification
icon, kmix icon and klipper, right after that I can hear log in welcome music.
Just checked what will happen when I only log out and log in from kdm (no
system reboot) - same delay.
When I had default splash screen set, this delay was appearing on the last
splash screen icon. I could click LMB and the desktop appeared fully operable
but anyway I had to wait for tray's icons and welcome music. When I didn't
click, I had to wait when those tray icons were fully loaded and in that moment
splash screen disappeared, playing welcome music.
I hope you can understand someting from this description as I'm not an English
Master of Universe ;]
Please feel free to ask about anything if you need.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list