=== rudydog is now known as monkeyjuice | ||
=== mamarley_ is now known as mamarley | ||
=== ahoneybu- is now known as ahoneybun | ||
lordievader | Good morning. | 08:42 |
---|---|---|
soee | https://www.digikam.org/node/745 | 10:51 |
yofel | hm, so we'll get qt5 digikam sometime in Q1 16, nice | 10:54 |
BluesKaj | Hiyas all | 12:35 |
allee | soee: wasn't it you how saw this long delay on session login? | 13:34 |
allee | I've redirected stdout/err to journald instead of .xsession-error. And my ~ 25 sec delay is caused by earch akonadi resource need ~ 2 sec to be started by kdeinit5 | 13:35 |
KubuntuSuperBot | <Aaron>: @kubuntubot test | 14:04 |
yossarianuk | hi - logging into wily (kde) I'm getting a message from kwalletd5 | 14:44 |
yossarianuk | Configuration file "//.config/kwalletd5rc" not writable. Please contact your system administrator. | 14:44 |
yossarianuk | sounds like -> https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1504626 | 14:44 |
yossarianuk | but that is for kde4 ? | 14:45 |
yossarianuk | this sounds like it -> https://bugs.kde.org/show_bug.cgi?id=351805 | 14:47 |
ubottu | KDE bug 351805 in general "Configuration file "//.config/kwalletd5rc" not writable. Please contact your system administrator." [Normal,Needsinfo: waitingforinfo] | 14:47 |
soee | allee: one more time, it is akonadi fault ? | 16:16 |
allee | soee: I would say yes. Bit O | 16:22 |
allee | soee: but I remember seeing this with a fresh user too (there are no resources). So should be no delay. I'll try with a virgin user later. | 16:23 |
soee | allee: cool, send me info you you have more details | 16:23 |
allee | modulo typos, timing via: x=/usr/bin/startkde; dpkg-divert --local --rename $x && echo -e "#!/bin/bash\n exec systemd-cat -t plasma5 $x.distrib" > $x; chmod 755 $x # journalctl --user -f | 16:30 |
soee | http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-15.10-More-Tests | 19:02 |
soee | hmm looks like we are slowing down | 19:02 |
allee | soee: it's akonadi startup. I've created a ~/bin/akondiserver fake script that just contains 'exit 0' and now session login is down from ~ 30sec to 4 sec. Yeah! | 21:22 |
allee | Unfortunately I use kdepim quite heavily, so no fast startup for me :-( | 21:23 |
soee | allee: ok but any idea why it needs so may time ? | 21:26 |
soee | Riddell, yofel: can we do somethig about it ? | 21:27 |
yofel | we can as soon as we can answer your first question.. | 21:27 |
soee | yofel: is there some way to debug this ? | 21:29 |
allee | soee: no real idea. I only see that every ~ 2 sec a resource is started. And akonadi resource startup seem to be synchronos. At work I've a trusty system. Then I can check if resource start is asynchronos in kde4 | 21:29 |
soee | is there some channel here on freenode for akonadi devs ? | 21:31 |
soee | ah there is | 21:31 |
allee | soee, yofel: a start would be to find a way to login without akonadi. But even without korgan reminder daemon, akonadi tries to start every resource ;-( | 21:32 |
allee | soee: the a #akonadi channel | 21:32 |
yofel | for that you just need to find out why plasma waits on akonadi. akonadi doesn't start unless something requires it to | 21:33 |
soee | allee: i will try to ask there tomorrow and get some feedbac | 21:33 |
soee | yofel: in a free time could you please take a look at this: http://paste.ubuntu.com/12853087/ It is from the crash when i endabled file indexing on my system | 21:38 |
allee | soee: would be great | 21:38 |
allee | thx | 21:38 |
soee | allee: also thanks | 21:38 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!