[07:26] <lordievader> Good morning
[09:28] <amichair> Riddell: Thanks for all your great work and leadership with Kubuntu during the past decade (?), it is much appreciated by lots of people whom you've never met :-)
[09:28] <amichair> Riddell: Good luck with your future endeavors, I'm sure you'll do many more great things!
[09:29] <yossarianuk> hi - is this bug -> https://bugs.kde.org/show_bug.cgi?id=354230  The cause of a really slow login to kde on 15.10 ?
[09:30] <yossarianuk> takes about 30 - 40 secs to get a usable desktop from login on 15.10 (didn;t happen on 15.04)
[09:30] <yossarianuk> just wanted to ensure it was this bug (as that looks fixed upstream)
[09:31] <amichair> yossarianuk: I have that bug, and it depends on what you mean by login....
[09:32] <amichair> yossarianuk: it happens after the actual login screen, when some of the other stuff already appaers (including partial panel)
[09:32] <yossarianuk> i.e after logging in to sddm 
[09:32] <amichair> yossarianuk: but then it hangs for ~50 secs (in my case) until the panel is completely drawn and responsive
[09:32] <yossarianuk> until its fully loaded the taskbar locations of clock, etc are wrong also 
[09:32] <yossarianuk> sounds very similar.
[09:32] <amichair> so yes, it's probably that
[09:32] <yofel> there's more than one reason for a slow plasma login, but in ~2h or so I could wrap up a test package with above fix
[09:33] <yossarianuk> I assume the fix will be in the normal updates at some point?
[09:33] <yossarianuk> yofel: I'll happily test the package (when im back home)
[09:34] <yossarianuk> so far though the slow login is the only real issue with 15.10, apart from that it seems better than 15.04.
[09:34] <yofel> the fix is in Plasma/5.4, so it should be part of 5.4.3
[09:34] <amichair> yofel: any idea when that will be released and available in kubuntu updates?
[09:35] <yofel> .3 is due in ~3 weeks
[09:35] <yofel> we can cherry-pick that patch before that if it really does help
[09:42] <amichair> yofel: personally I don't log in/out too often, so a 3 weeks wait is fine. I'd think the ubiquity bug that causes the upgrade to 15.10 to crash is far more critical.
[09:44] <yofel> erm, what bug? (ubiquity is the live-installer, and has nothing to do with upgrading)
[09:45] <amichair> yofel: oh, then someone pointed me to report a bug in the wrong place, perhaps
[09:45] <yossarianuk> yofel: login bug - its not exactly critical however would give bad impressions to someone checking out how plasma5 is getting along. maybe add to known 15.10 issues on the release notes ?
[09:46] <yofel> amichair: I guess update-manager would be more correct. I think I remember someone talking about a crash there
[09:47] <yofel> yossarianuk: hm, we could maybe add a generic message about that. There seems to be at least the bluez issue and an issue with akonadi that cause that
[09:47] <amichair> yofel: bug #1509655
[09:48] <amichair> yofel: there was also bug #1509653 which was scary (saw it on two systems), but doesn't actually prevent the upgrade from succeeding, so not that critical
[09:49] <amichair> yofel: but the former bug just crashed the upgrade and left people with a broken system. discussed it with two other guys on #kubuntu the other day who also suffered from it.
[09:50] <yofel> yeah, I know about the kdeinit5 one. But no idea what to do about that
[10:01] <soee_> yossarianuk: allee was thinking that the loading system lag problem could be caused by akonadi
[10:03] <yofel> I think he pretty much proved that his problem is akonadi
[10:04]  * yofel wonders if the pyqt5 API changed...
[10:04] <allee> Yes. Unfortunately dvratil could not reproduce with master :-(
[10:05] <allee> yofel: is there a description how to pick e.g. only KDEPIM from CI  (to test if the problem goes away with master pkgs)
[10:06] <yofel> no, your best bet would be to add the repository and selectively upgrade the packages you're interested in
[10:49] <BluesKaj> 'Morning folks
[10:57] <sgclark> morning
[11:01] <ahoneybun> o/
[11:03] <BluesKaj> nothing in the pipe for 4 days , that's unusual for a new release, still plenty of unsolved issues 
[11:17] <d_ed> can you guys look at https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1509334 I've linked to a patch, if you could backport it, that'd probably be useful
[11:23] <yofel> d_ed: on my todo list, thanks for the bug link
[11:24] <yossarianuk> d_ed: cheers - thats affecting me
[11:24] <d_ed> it's in 5.4.3, which is ETA mid Nov
[11:26]  * ahoneybun has a ssd so he is not feeling that
[11:26] <d_ed> actually, you have bluetooth so you're not feeling that
[11:27] <d_ed> we just sit idle for 30s doing nothing
[11:27] <ahoneybun> ?
[11:27] <BluesKaj> yeah , but removing NM from the panel is not a solution here, since I use vpn a lot , and I have no intentions of trying to configure openvpn and server in network interfaces
[11:28] <d_ed> well, that's why we fixed it :D
[11:30] <BluesKaj> d_ed, I must be missing a repos because nothing upgrades here
[11:31] <d_ed> ah.. When I say "we" I mean KDE upstream
[11:31] <d_ed> I'm here liasoning.
[11:36] <clivejo> yofel: seems to be on the case :)
[11:44] <clivejo> yofel: do you create a quilt patch for plasma-nm and put it in the packaging?
[11:45] <clivejo> to patch libs/handler.h and libs/handler.cpp
[11:45] <yofel> clivejo: yes, do you want do prepare the SRU? I probably won't get to it until the evening
[11:46] <clivejo> yofel: never done it before so unsure of the process
[11:46] <clivejo> trying to follow what you do to fix it
[11:46] <yofel> hm, then it'll have to wait until later. Then I can tell you what needs to be done
[11:47] <clivejo> does the patch go into debian git?
[11:47] <clivejo> and if so what branch, now that wily is release?
[11:48] <yofel> yes, but you also need to branch of kubuntu_xenial_archive, put the patch there first, then prepare a similar upload with different version in kubuntu_wily_archive, update the bug with the SRU information and get things uploaded
[11:48] <clivejo> eak
[11:49] <clivejo> the prepare wily version is were I think you lose me
[11:50] <clivejo> version numbers still confuse me
[11:50] <clivejo> yofel: maybe give me a shout when you are free, Id like to go through it with you if thats ok
[11:51] <yofel> well, here it's easy. Say you have -0ubuntu1 in wily now, xenial would get -0ubuntu2, wily-updates -0ubuntu1.1
[11:51] <yofel> sure, will have to wait until after work, so in ~6h
[11:52] <clivejo> is there a script you run to start all the new xenial branches?
[11:53] <clivejo> or are they done manually as needed?
[11:53] <yofel> good question.. no idea right now. I think manually is fine for now
[11:54] <yofel> Riddell: what was the process for vivid->wily back then? ^
[11:55] <Riddell> sitter had a script somewhere I think
[11:55] <Riddell> manually is also fine
[11:57] <clivejo> Riddell: would you show me the script?
[11:57] <Riddell> when I say somewhere it's because I don't remember where :)
[11:58] <clivejo> where is sitter these days, havent seen him about?
[11:59] <ahoneybun> Riddell: how is that docs.kubuntu.co.uk server?
[11:59] <clivejo> when does development on xenial official start?
[12:00] <yofel> once the toolchain upload is done. There'll be an announcement somewhere (ubuntu-devel ML I think?)
[12:01] <Riddell> sitter said he was away on friday, I guess he's taking a long weekend
[12:01] <Riddell> ahoneybun: still doing fine :)
[12:02] <ahoneybun> Riddell: could you update it :)
[12:02] <Riddell> ahoneybun: update what about it?
[12:02] <BluesKaj> saw something about the toolchain for Oct 29th
[12:02] <ahoneybun> the content?
[12:03] <ahoneybun> https://github.com/ahoneybun/kubuntu-manual
[12:03] <ahoneybun> make it like this: http://192.254.78.155/
[12:04] <yofel> oh, that came out really nice :)
[12:05] <ahoneybun> thanks yofel :)
[12:05]  * ahoneybun flys off to work
[12:06] <yofel> and me to lunch
[12:06] <yofel> bbl
[12:06] <Riddell> ahoneybun: feel free to update it, not my responsibility any more I'm afraid
[13:04] <mhall119> hi, does anyone here involved in plasma mobile want to host a session talking about it for the convergence track of UOS 15.11?
[14:16] <yofel> clivejo: actually, I just noticed that #ubuntu-devel says "Archive: open" - so xenial is already open for dev
[14:18] <clivejo> yofel: Im trying to find the scripts sitter used
[14:19] <clivejo> not having much luck
[14:19] <yofel> shadeslayer: do you know where those are ^
[14:19] <clivejo> Riddell: suggested the channel logs
[14:20] <clivejo> but cant find anything yet
[14:20] <Riddell> he may have just put it in a pastebin
[14:20] <yofel> not sure I would find anything there either. I believe the CI repo is on Alioth, but I don't remember how it's called
[14:20] <yofel> OTOH, scripting creation of a branch in all repos is something you can do with a 5-line bash script or so..
[14:21] <clivejo> I been looking at logs after the 23rd April 2015
[14:21] <clivejo> would hardly be done before it?
[14:22] <yofel> very unlikely, right
[14:24] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/applications/amor.git/log/?h=kubuntu_wily_archive
[14:24] <clivejo> does it log when the wily archive was started?
[14:25] <clivejo> that period of time looks like sgclark was working on it
[14:30] <Riddell> ach it's just one command, just do it by hand
[14:37] <yofel> considering our workflow, santa_'s new scripts should probably have a failsafe check that makes sure the branch exists before it tries to check it out
[14:38] <yofel> so just leave it for now and just create the branch you need by hand
[15:11] <pursuivant> muon (master) v5.4.2-137-gcdc24d3 * Aleix Pol: discover/qml/PageHeader.qml
[15:11] <pursuivant> Fix margins in the page header
[15:11] <pursuivant> Only leave them on the side
[15:11] <pursuivant> http://commits.kde.org/muon/cdc24d3516b565bbdbe906147ee6cdd8480ccd0b
[15:12] <pursuivant> muon (master) v5.4.2-138-g1e8f40a * Aleix Pol: discover/qml/SourcesPage.qml
[15:12] <pursuivant> Fix sources page display
[15:12] <pursuivant> http://commits.kde.org/muon/1e8f40a82e577dfb9428579e817132936d75426b
[16:25] <sgclark> clivejo: all by hand, I did not have a magic script.
[16:32] <kustodian> I noticed that Telepathy auth for Google Hangouts has been changed, so now you have to login with your google account and than it justs uses the auth token
[16:33] <kustodian> but the problem is that it doesn't work
[16:33] <kustodian> after I login into google without any errors, when I try to go online it doesn't work
[16:33] <kustodian> tries for a few seconds and than it stops without any errors
[16:33] <kustodian> I'm on 15.10
[16:33] <kustodian> upgraded today
[16:49] <marco-parillo> kustodian: Can you go to you GMail, and see if you have an e-mail about some kind of insecure, deprecated access attempt?
[16:49] <clivejo> sgclark: wow, you must be very patient!
[16:51] <yofel> you may imagine a world without the automation scripts :P
[16:51] <sgclark> heh yes
[16:51] <sgclark> also had to do all the debian merges at the same time
[16:52] <yofel> hm, we have to do those too, right..
[16:52] <sgclark> yeah
[16:52]  * yofel imagines a 300-or-so long todo list
[16:52] <yofel> someone motivate me...
[16:52] <sgclark> I am working on trusty and vivd backports right now, can after though.
[16:52] <santa_> yofel, clivejo: what you are trying to do? creating new branches for xenial?
[16:53] <yofel> santa_: that was the original topic, yes
[16:53] <clivejo> yes, automatically
[16:53] <santa_> for frameworks/plasma/apps for example?
[16:53] <clivejo> all of them
[16:54] <yofel> FWIW, as scarlett said, we have to do that anyway when we merge, so the point is moot in some sense
[16:55] <santa_> clivejo, yofel: give me a couple of minutes and I will send a terminator to the rescue
[16:55] <santa_> actually an early version of its firmware
[16:55] <yofel> XD
[16:56] <kustodian> marco-parillo: I didn't receive an email like that
[16:57] <kustodian> I checked in the list of allow applications and "KDE Online Accounts" is there and it has access to a lot of stuff
[17:09] <santa_> yofel: https://gitlab.com/kubuntu-clones/kubuntu-automation
[17:09] <santa_> in the automation-ng branch I have the first version of git-clone-all and do-all
[17:10] <santa_> so you can do this
[17:10] <santa_> $ mkdir ~/kde-all/
[17:10] <santa_> $ cd ~/kde-all/
[17:11] <santa_> $ git-clone-all
[17:11] <santa_> $ do-all "git checkout kubuntu_wily_archive"
[17:11] <santa_> $ do-all "git branch kubuntu_xenial_archive"
[17:12] <santa_> $ do-all "git push origin kubuntu_xenial_archive"
[17:12] <santa_> and I think that should do the thing if that's what you want to do
[17:12] <yofel> that page says 504, gitlab, what's wrong with you..
[17:13] <santa_> sigh
[17:13] <santa_> let me create a clone in github then
[17:18] <santa_> yofel: https://github.com/jmsantamaria/kubuntu-automation-work
[17:19] <yofel> thanks, I'll try it out when I'm home
[17:19] <yofel> ~2h
[18:06] <clivejo> yofel: will you please have a wee look at https://launchpad.net/~clivejo/+archive/ubuntu/wily/+build/8193598 when you get time
[18:06] <clivejo> or even santa_ ^^
[18:13] <clivejo> think the version number is wrong :(
[18:14] <clivejo> needs to be 4:5.4.2-0ubuntu1.1 for wily?
[18:15] <clivejo> BluesKaj: ping
[18:19] <Riddell> yes use 1.1 for wily-updates
[18:19] <clivejo> Riddell: cant you check that over for me please :)
[18:19] <clivejo> can you
[18:23] <clivejo> I used the xenial packaging, to test build and upload to my PPA, do I need to push in wily archive too, with a different version number?
[18:25] <Riddell> sorry I'm about to go out, but yes push it to wily_archive with the 1.1 version
[18:25] <clivejo> with the 1.1 version number
[18:25] <Riddell> yes
[18:25] <clivejo> thanks :)
[18:31] <BluesKaj> clivejo, pong
[18:31] <clivejo> fancy testing plasma-nm for me?
[18:40] <soee> clivejo: this build contains teh fix for the 30 sec lag 
[18:40] <soee> ?
[18:40] <soee> or it was related to different package ?
[18:40] <clivejo> I believe so
[18:40] <clivejo> if I have done it right
[18:41] <soee> ;D
[18:41] <clivejo> but the version number is wrong
[18:41] <clivejo> Im trying to fix that now
[18:51] <clivejo> eak, 1.1 version is pending for 2 hours
[19:22] <yofel> clivejo: thanks for preparing plasma-nm, a few comments though
[19:23] <yofel> - please always commit with UNRELEASED unless the version has been uploaded to the primary archive
[19:23] <yofel> - the patch is either kubuntu_* -> origin: vendor, OR upstream_* -> origin: upstream. In this case, you'll want latter
[19:25] <yofel> - The changelog message is actually rather good, but slightly wrong:
[19:25] <yofel>  "will be applied upstream" is "from upstream" - it's already been committed. 
[19:25] <yofel> The parentheses around the patch name don't really make sense. 
[19:26] <yofel> you indicate an upload fixing a bug with: LP: #0000000 - which is usually at the end of your changelog message. (That will then auto-close the bug once uploaded)
[19:47] <soee> yofel: is it save to test it https://launchpad.net/~clivejo/+archive/ubuntu/wily/+build/8193870 ?
[19:48] <yofel> soee: yes
[19:50] <soee> rebooting
[19:51] <soee> back
[19:51] <soee> yofel: interesting, system loads now in ~8 sec
[19:51] <soee> so no lag as before
[19:52] <yofel> ok, so you did have the bluez issue. At least we know that it works fine :)
[19:52] <yofel> thanks for testing
[19:52] <soee> yofel: one more reboot, just to be sure
[19:53] <soee> yup, confirmed
[19:53] <soee> system loads in ~ 8 sec now
[19:54] <soee> clivejo: gret work with the package
[19:54] <soee> allee: so in my case the lag was caused by bluez
[19:55] <soee> yofel: what bug numer/link was it ?
[19:55] <yofel> lp 1509334
[20:03] <soee> yofel: just poted small info about it on G+, hope it wasn't to early :)
[20:04] <soee> now there are 2 annying bugs left imo.
[20:05] <soee> first: missing plasma-pa icon in systray 
[20:05] <soee> second: baloo indexer crash after system boot
[20:05] <yofel> I don't have the second, but I've seen the first one - but it's a bit random..
[20:10] <soee> yofel: http://paste.ubuntu.com/12973455/
[20:17] <soee> oh and: https://plus.google.com/+JakobHarz/posts/h39zc6U85hc
[20:26] <clivejo> yofel: thanks, nice to know all those
[20:26] <clivejo> so kubuntu_ patch is only for something affecting us?
[20:27] <yofel> is only for stuff either created by us or stuff specific to us
[20:27] <clivejo> I see, I thought it was for a patch added by the kubuntu packagers
[20:28] <clivejo> I commited xenial as UNRELEASED and wily with WILY, is that wrong?
[20:30] <clivejo> regarding the patch name, should it be upstream_redhat_* to show where the patch came from?
[20:30] <yofel> no, just upstream_
[20:30] <yofel> unless you got that from some RHEL repository or so
[20:30] <clivejo> KDE commit
[20:31] <clivejo> I used quilt import *.diff
[20:31] <yofel> right, so just upstream_ (i.e. it came from the repository that the source itself came from)
[20:32] <clivejo> so at the end of my changelog I should put "* Fixes LP: #1509334" and LP will mark it as fixed?
[20:33] <yofel> drop the "* Fixes"
[20:33] <yofel> a) it belongs the the message above, b) the syntax already says that it fixes it
[20:35] <soee> https://plus.google.com/110954078302330754910/posts/EYpzxwHXPG8
[20:35] <clivejo> should I make those changes in git?
[20:35] <clivejo> yofel: also, have I broken KCI ?
[20:36] <yofel> please do the changes
[20:36] <yofel> as for CI, it's been rather red lately... haven't looked at it
[20:40] <clivejo> do I put LP: #000000 on a new line?
[20:41] <yofel> that's up to you.. I usually only do that if the line gets too long
[20:42] <clivejo> and my patch file should be .patch?
[20:42] <yofel> that again doesn't matter, just keep what you have now
[20:43] <yofel> regarding UNRELEASED, always use that unless you uploaded to the primary archive (or the target one)
[20:43] <yofel> doesn't matter if it's dapper or xenial
[20:43] <clivejo> can I ommit an extension?
[20:43] <clivejo> just call it - upstream_fix_making_bluez_asynchronous
[20:43] <yofel> I believe yes, but that's rather unusal..
[20:43] <clivejo> what is usual standard
[20:44] <clivejo> have to change the name anyways, might as well get it right :)
[20:44] <yofel> I think .diff is what I've seen most, but I also saw .patch or nothing
[20:45] <clivejo> Ill use .diff
[20:51] <yofel> okay, what do you actually want from us...
[20:52] <yofel> oh right, the patch will cause a build failure
[20:52] <soee> ;]
[20:52] <clivejo> oh?
[20:53] <yofel> well, you took a patch from upstream git, now you're building upstream git and applying an already applied patch -> BOOM
[20:56] <clivejo> ah, that makes sense
[20:56] <clivejo> how does one fix that?
[20:56] <clivejo> remove the patch in git?
[20:57] <yofel> yes, in the _unstable branch once we're done
[20:57] <clivejo> ok I pushed those changes
[20:57] <yofel> thanks
[20:57] <clivejo> has the package been tested?
[20:58] <clivejo> the one in my PPA?
[20:58] <yofel> soee said that it fixed his problem
[20:58] <soee> clivejo: yup, rebooted twice to confirm it. system loads now in ~8seconds (before it was ~ 30)
[20:58] <clivejo> should I redo a ppa2 with the new changelog?
[20:59] <yofel> would be useful yes, then we can copy that to the updates ppa once it's done building
[20:59] <yofel> then we can point people there
[21:02] <yofel> ok, now let me upload that and fill out the paperwork
[21:03] <clivejo> yofel: can you explain?
[21:03] <yofel> !sru
[21:03] <yofel> see "Procedure"
[21:04] <clivejo> you have to write an essay on why the update should go into the archive?
[21:05] <yofel> yep
[21:05] <yofel> hence "paperwork" :P
[21:06] <yofel> the procedure comes from the very early ubuntu days where some X11 "quick fix" broke most of the user systems as an update
[21:09] <clivejo> is it public?  can I have a read, just for curiosity?
[21:09] <yofel> what?
[21:09] <clivejo> the paperwork you submit
[21:09] <yofel> sure, it goes into the bug description
[21:09] <yofel> but I'll do that after the upload
[21:10] <yofel> which comes after I testbuild - which I do once my xenial chroot creation is done ^^
[21:10] <yofel> all the stuff you have to do to fix stuff - that's why you don't break it in the first place :P
[21:14] <clivejo> only way I learn is to do it :)
[21:14] <clivejo> and that usually means breaking it and then trying to fix it
[21:15] <clivejo> so you are currently building for xenial?
[21:16] <yofel> yep
[21:18] <clivejo> I guess I should create a xenial pbuilder-dist image
[21:18] <clivejo> and a xenial PPA 
[21:18] <yofel> not sure why you need a seperate PPA, but the chroot you should do
[21:18] <yofel> or well, create it when you need it
[21:21] <soee> http://tanglu.org/blog/2015/10/tanglu-40-dasyatis-kuhlii-alpha-released/
[21:27] <yofel> xenial uploaded
[21:28] <clivejo> yipppeee
[21:29] <yofel> wily uploaded
[21:31] <soee> any idea if there are some decisions for Martin's proposal @ Plasma bugfix releases ?
[21:42] <yofel> don't we already have those?
[21:42] <yofel> or what do you mean?
[21:43] <yofel> clivejo: so, done updating the bug
[21:43] <yofel> now we have to wait
[21:43] <clivejo> wait on what?
[21:43] <clivejo> for it to land in main archive?
[21:44] <yofel> for someone from ~ubuntu-sru to approve the update and an archive admin to accept the upload
[21:44] <yofel> then the package has to be tested and tagged verification-done
[21:45] <yofel> once that's done and at least 7 days have passed the update can go into -updates
[21:51] <soee> yofel: Martin proposed on #plasma releases like: 1 week, 1 week, 2 weeks , 4 weeks etc.
[21:51] <clivejo> eakk
[21:51] <soee> to get faster bug releases for users
[21:51] <clivejo> such a load of fafff
[21:52] <clivejo> have you put it in a kubuntu_testers PPA?
[21:52] <soee> [11:12:40 CET] <mgraesslin> Riddell: I was thinking about how we can get our bug fixes faster to the user and had the idea of doing fibonaci releases
[21:52] <soee> [11:13:01 CET] <mgraesslin> that is: 1 week, 1 week, 2 weeks, 3 weeks and then depending whether we have bug fixes even more
[21:53] <yofel> hm... that does make sense actually..
[21:53] <yofel> so I wouldn't mind