/srv/irclogs.ubuntu.com/2015/10/18/#kubuntu-devel.txt

=== rudydog is now known as monkeyjuice
=== mamarley_ is now known as mamarley
=== ahoneybu- is now known as ahoneybun
lordievaderGood morning.08:42
soeehttps://www.digikam.org/node/74510:51
yofelhm, so we'll get qt5 digikam sometime in Q1 16, nice10:54
BluesKajHiyas all12:35
alleesoee: wasn't it you how saw this long delay on session login?13:34
alleeI'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 test14:04
yossarianukhi - logging into wily (kde) I'm getting a message from kwalletd5 14:44
yossarianukConfiguration file "//.config/kwalletd5rc" not writable. Please contact your system administrator.14:44
yossarianuksounds like -> https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/150462614:44
yossarianukbut that is for kde4 ?14:45
yossarianukthis sounds like it -> https://bugs.kde.org/show_bug.cgi?id=35180514:47
ubottuKDE bug 351805 in general "Configuration file "//.config/kwalletd5rc" not writable. Please contact your system administrator." [Normal,Needsinfo: waitingforinfo]14:47
soeeallee: one more time, it is akonadi fault ?16:16
alleesoee: I would say yes.  Bit O16:22
alleesoee: 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
soeeallee: cool, send me info you you have more details16:23
alleemodulo 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 -f16:30
soeehttp://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-15.10-More-Tests19:02
soeehmm looks like we are slowing down19:02
alleesoee: 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
alleeUnfortunately I use kdepim quite heavily, so no fast startup for me :-(21:23
soeeallee: ok but any idea why it needs so may time  ?21:26
soeeRiddell, yofel: can we do somethig  about it ?21:27
yofelwe can as soon as we can answer your first question..21:27
soeeyofel: is there some way to debug this ?21:29
alleesoee: 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 kde421:29
soeeis there some channel here on freenode for akonadi devs ?21:31
soeeah there is21:31
alleesoee, 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
alleesoee: the a #akonadi channel21:32
yofelfor that you just need to find out why plasma waits on akonadi. akonadi doesn't start unless something requires it to21:33
soeeallee: i will try to ask there tomorrow and get some feedbac21:33
soeeyofel: 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 system21:38
alleesoee: would be great21:38
alleethx21:38
soeeallee: also thanks 21:38

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!