[06:10] <claydoh> ok, ray burke is back on the mailing list, and as usual  does not remember things he's been told about many times in the past, email-wise
[06:11] <claydoh> so anyone offering aid please take that into considersation. He needs specific,  step-by-step hand-holding
[06:13] <claydoh> Mamarok: :  and valorie I've already responded to his usual email-all-the-addresses-possible off-list, and bcc'd you both
[06:14] <valorie> thank you claydoh
[06:14] <valorie> perhaps he's senile or so?
[06:14] <claydoh> perhaps, it has been tis way for years
[06:14] <claydoh> many years
[06:15] <valorie> I admin quite a few genealogy lists, and am used to clueless old windows users
[06:15] <claydoh> he can't follow an email thread, which of course with multiple people assistng confuses him
[06:16] <valorie> many of them I just moderate full-time, and only allow the few on-topic posts
[06:17] <valorie> does he do better on a forum, claydoh?
[06:17] <claydoh> he would, but I  have not been ablle to get him to go there, or he has been, but is quite easily confused
[06:18] <valorie> poor old thing
[06:18] <valorie> but tiresome to the helpful folks
[06:18] <claydoh> unlike steve vollum, who is an elderly gentleman who may be in a home, but has done sooo much better there
[06:20] <valorie> well, everyone ages differently
[06:21] <valorie> my mother had alzheimers, and grew paranoid
[06:21] <valorie> my dad is very senile, and just seems peaceful
[06:21] <valorie> hardly speaks anymore, and is now forgetting how to swallow
[07:12] <soee> hiho
[08:02] <aseques> Hello, after upgrading to kubuntu willy backports I have to different audio mixers
[08:03] <aseques> I've both kmix, and sound volume
[08:03] <aseques> Which one is the default with current releases?
[08:05] <aseques> 'sound volume has a nice osd display, but not sure if it's kde's default
[08:07] <valorie> yes, you can remove the one you don't want
[08:07] <valorie> unfortunately, both have features the other one doesn't
[08:07] <valorie> still
[09:01] <soee> valorie: but plamsa-pa is developed so i suggest using it
[09:02] <soee> in Plasma 5.6 it will also have option to controll various sound sources like kmix
[09:03] <soee> so it will be pretty the same (without widow with shortcuts to some caonfigurations etc. but this can be done through System Settings -> Multimedia anyway)
[09:05] <valorie> soee: right now I just leave them both
[09:07] <soee> ;o
[09:08] <soee> :)
[09:08] <soee> valorie: can you test 5.5.4 ? are you on Xenial ?
[09:09] <soee> i would liek to have 10 people that will test stuff before release :}
[09:15] <valorie> is it the ppa landing you want tested?
[09:15] <valorie> and yes, I can
[09:16] <soee> valorie: staging-plasma
[09:16] <soee> it has been tested already by 4 people
[09:19] <valorie> if you want more testers, call for them
[09:21] <yofel> moin
[09:21] <yofel> soee: while it's in staging please use WIP, once it's in landing use LANDING
[09:21] <yofel> and please don't do public tester calls for staging
[09:22] <valorie> hmm, so what should I do?
[09:22] <valorie> it's my travel laptop, so I'm ok with testing with it
[09:22] <valorie> that's what I use it for when I"m not traveling
[09:23] <yofel> I'll copy it to landing
[09:23] <yofel> not sure why clive didn't do that, I did tell him to copy it
[09:23] <valorie> ok
[09:26] <yofel> copied, you'll get it once the publisher is done
[09:26] <yofel> now to fix the topic again
[09:29] <valorie> thank you yofel
[09:45] <soee> yofel: ok. i thought people here can test it as they know what they are doing :) 
[09:47] <valorie> ok, my xenial updates are about done, so I just add back the ppa-landing? 
[09:47] <yofel> soee: well, as long as it's here, ~ok. I just don't like people using staging directly because I don't intend to tell anyone when I upload something there that might make a mess
[09:47] <valorie> what I mean is, is the move done
[09:47] <yofel> and landing is what's supposed to be used for testing
[09:47] <soee> yofel: right :)
[09:49] <soee> so atm. we have only apps 15.12.1 not done
[09:49] <soee> and what about 5.5.4 backport - are we doing it ?
[09:49] <yofel> sure
[09:55] <valorie> added, now updating
[10:09] <Mirv> now Qt 5.6 is moved to March
[10:09] <yofel> *sigh*
[10:09] <Mirv> indeed
[10:14] <snele> and they don't want to do one more qt 5.5 bugfix release... 
[10:14] <soee> Mirv: where i can see some announcement ?
[10:15] <snele> soee: https://wiki.qt.io/Qt-5.6-release
[10:17] <snele> yofel: is it possible to have patches from qt 5.6 backported to ubuntu's qt 5.5? for example for missing icons in systray at boot 
[10:18] <soee> but no info why it is postponed ?
[10:20] <Mirv> soee: the wiki page indeed, I suspect there was a release meeting earlier this week but the notes from it haven't been posted
[10:20] <yofel> snele: we can certainly look at them
[10:21] <Mirv> snele: sure, there are _lots_ of backported patches from Qt 5.6 already in qtbase and qtdeclarative
[10:22] <Mirv> soee: remaining bugs. Qt is a bit notorious with late releases.. the 5.6 was postponed from October to December already in the planning phase to have a "realistic" goal of releasing it in December. and then 5.7 was supposed to happen in April.
[10:22] <Mirv> or maybe it's also that all projects seem notorious with late releases when compared to Ubuntu :)
[10:22] <soee> well but in teh end better to have stable release than early buggy product
[10:23] <Mirv> yeah, good release planning would help though. somehow it gets too unstable during their development cycle, even though they have lots of CI.
[10:23] <soee> the biggest minus here is taht 5.6 probably wont make it into 16.04
[10:24] <Mirv> of course Qt is a huge project too, abstraction of everything on every platform is not the easiest job
[10:24] <soee> true
[10:25] <soee> maybe better way would be to add less features but make releases faster
[10:26] <soee> this way people can test what was released and report issues and than quicker fixes would be released
[10:41] <valorie> soee: my xenial upgrade was totally smooth and wonderful
[10:49] <soee> valorie: COOL, THANK YOU
[10:49] <soee> sorry for UC
[11:17] <mparillo> Plasma 5.5.4 is in ppa:kubuntu-ppa/ppa-landing ?
[11:18] <mparillo> For Xenial?
[11:19] <soee> mparillo: yes
[11:22] <mparillo> It looks as if some apps were upgraded also. Including kate, and Muon Update Manager.
[11:23] <mparillo> Downloading now.
[11:35] <clivejo> yofel: I wanted to test it myself before copying
[11:36] <clivejo> then I got tired and went to bed!
[11:36] <yofel> ah ok, very reasonable decision :)
[11:37] <yofel> sorry for storming in
[11:37] <clivejo> seems to be stable though
[11:37] <clivejo> dont be sorry, you didnt know!
[11:37] <clivejo> not a mind reader
[11:38] <clivejo> well I hope not :P
[11:38] <clivejo> you might interfer with my plans for galactic domination
[11:39] <mparillo> Updates completed. Time to re-boot.
[11:42] <clivejo> my death star will be powered by Mycroft and Kubuntu
[11:44] <mparillo> Kinfocenter reports Plasma 5.5.4. No immediate obvious breakage in krunner, konsole, konversation either. Well done clivejo and yofel.
[11:45] <mparillo> Plus this time, after applying updates, my kicker (which also seems to work after the re-boot) I was able to use it for the shutdown, without a sudo poweroff.
[11:45] <clivejo> yofel: has there been a call for testing?
[11:45] <mparillo> Assumming it is not worthy of a kubuntu.org news post, I would be happy to put it on the wire.
[11:45] <yofel> not yet
[11:46] <mparillo> When you are feeling comfortable.
[11:46] <yofel> the news post comes with the backports
[11:46] <clivejo> I think thats over 10 people now
[11:46] <yofel> and the shutdown issue only happens for major version updates, not bugfixes
[11:46] <yofel> which is annoying enough
[12:13] <BluesKaj> Hiyas all
[12:15] <clivejo> hi BluesKaj
[12:15] <BluesKaj> Hi clivejo
[12:15] <clivejo> mind testing plasma 5.5.4?
[12:15] <clivejo> on xenial
[12:16] <BluesKaj> clivejo, ok 
[12:16] <clivejo> its in the landing PPA
[12:18] <BluesKaj> I had to roll back to 5.4.3 due to a kserver error 2 days ago
[12:19] <clivejo> oh right
[12:19] <clivejo> never mind
[12:19] <BluesKaj> so I had to ppa-purge the ci/stable and landing ppas
[12:21] <BluesKaj> clivejo, is that server error fixed, if so I'd be willing to try the landing ppa again
[12:28] <acher88> BluesKaj: not had that here at any stage testing the ppas
[12:39] <clivejo> BluesKaj: probably cause you used the KCI PPA's?
[12:39] <clivejo> KCI will have breakages
[12:43] <soee> clivejo: ping
[12:45] <BluesKaj> acher88, yeah I noticed the error was hone after purging the ci ppa, but got spooked and purged the landing as well
[12:45] <BluesKaj> gone
[13:08] <BluesKaj> ok, got plasma 5.5.4 
[13:12] <mparillo> For some reason (maybe 5.5.4), now krunner autocompletes Okular again, and dolphin opens PDFs using Okular. Big improvement over yesterday.
[13:45] <sgclark> morning
[13:45] <soee> hiho :)
[13:46] <soee> sgclark: do you have time to start 5.5.4 backport ?
[13:51] <sgclark> me? nope, so very behind :( so sorry
[14:02] <clivejo> hi soee
[14:05] <soee> clivejo: would you be interested in in packaging tomahawk ?
[14:05] <clivejo> no idea what that is
[14:06] <clivejo> !info tomahawk
[14:06] <clivejo> !info tomahawk xenial
[14:08] <morphis> anyone know who would responsible for a failing build of kwin due to a new libhybris update in xenial?
[14:10] <mgraesslin> morphis: Ubuntu for having a fork of libhybris in the archive
[14:10] <sitter> http://cdnimg3.webstaurantstore.com/images/products/extra_large/45500/241884.jpg
[14:10] <morphis> mgraesslin: there is a reason for having a "fork"
[14:10] <morphis> but that is changing
[14:11] <morphis> things are moved out of hybris and its becoming more or less a direct import from upstream, but that will take time
[14:11] <mgraesslin> please note that I don't care about why or why not there is a fork
[14:11] <morphis> that is fine :-)
[14:12] <morphis> mgraesslin: however kwin is failing to build now: mgraesslin: basically https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-012/xenial/amd64/k/kwin/20160128_122444@/log.gz
[14:12] <mgraesslin> shrug
[14:12] <morphis> now sure how you are going to handle this but hybris will become more or less just a dlopen/dlsym wrapper rather than providing any abstracted APIs
[14:14] <soee> clivejo: some days ago tomahawk devs wanted some packager
[14:14] <bshah> is it against git master libhybris?
[14:14] <bshah> morphis: ^ (build failure)
[14:14] <clivejo> where is the packaging?
[14:14] <morphis> bshah: which git master do you mean? upstream?
[14:14] <clivejo> https://launchpad.net/~tomahawk
[14:14] <clivejo> yofel: you own this team?
[14:15] <bshah> that error in kwin, what is libhybris being used?
[14:15] <morphis> bshah: https://git.launchpad.net/~libhybris-maintainers/libhybris/+git/libhybris/ is what we're currently going to land
[14:15] <morphis> its not in par with upstream yet but very close
[14:17] <morphis> bshah: as I already mentioned above you should also expect us to drop the hwcomposer wrapper at all at some point
[14:18] <bshah> morphis: well thing is, for plasma mobile we use https://github.com/libhybris/libhybris directly
[14:19] <bshah> with packaging from : https://github.com/plasma-phone-packaging/libhybris (upstream forked at some point)
[14:20] <morphis> bshah: I see
[14:22] <yofel> soee: someone else is already trying to update tomahawk
[14:22] <yofel> clivejo: I do, but haven't touched it in months
[14:23] <clivejo> Stefan Ahlers?
[14:26] <morphis> bshah: however then kwin in the archive should have hybris support disabled
[14:26] <bshah> morphis: yes.. it is good idea
[14:26] <bshah> however I don't have access to things.. :)
[14:26] <mgraesslin> morphis: or maybe Ubuntu renames libhybris in the archive, so that it doesn't get picked up and breaks the build
[14:26] <morphis> mgraesslin: why should we rename it?
[14:27] <mgraesslin> because it's a fork
[14:27] <morphis> mgraesslin: as I said, that is changing
[14:27] <morphis> mgraesslin: count it on history and pressure but that is how things are
[14:28] <mgraesslin> sure, just if one forks and doesn't rename it's causing problems
[14:28] <mgraesslin> of course version numbers in libhybris would also help
[14:29] <morphis> sure, but I can not cleanup everything at once
[14:30] <morphis> and version numbers include some kind of API stability which hybris doesn't have yet :-)
[14:56] <morphis> mgraesslin, bshah: so who can disable the hybris support in kwin in the ubuntu archive?
[14:56] <mgraesslin> morphis: no idea, I'm the upstream maintainer
[14:57] <bshah> morphis: maybe yofel/clivejo/sgclarck can help you there
[14:57] <morphis> mgraesslin, bshah: ok
[14:58]  * yofel thought that was disabled
[14:58] <yofel> checking
[14:59] <yofel> clivejo: Stefan, right
[15:00] <yofel> OH
[15:01] <yofel> mgraesslin, bshah, morphis: Ok, looks "libhybrids-dev [armhf]" crawled into the build-deps through the last debian merge
[15:01] <yofel> fixing
[15:01] <morphis> yofel: awesome!
[15:01] <mgraesslin> well on Debian doesn't make sense either
[15:02] <morphis> mgraesslin: debian might still have an older hybris version
[15:02] <mgraesslin> no, they don't have one at all
[15:02] <bshah> thx :)
[15:02] <yofel> maxyz_: ^
[15:02] <morphis> mgraesslin: ah :-)
[15:02] <mgraesslin> would make my life easier if they had ;-)
[15:04] <yofel> ok, I read the git log wrong, this seems to be entirely out fault. hybris was simply never *fully* removed
[15:04] <yofel> maxyz_: unping
[15:23] <maxyz_> unpong
[17:48] <soee> and no sound again :<<<
[17:50] <soee> and soud back after reboot
[17:50] <soee> i think this has something to do with sddm and failing logins
[17:51] <soee> i had sddm greeter in window and no sound, after reboot login was fine (first attempt) and i have sound
[17:59] <soee> guys some comments about backports: http://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/848483-plasma-5-5-3-kde-frameworks-5-18-backported-to-kubuntu-15-10
[18:06] <soee> yofel: can we somehow get this patch in Xenial just for test https://git.reviewboard.kde.org/r/126923/ ?
[18:06] <sgclark> nothing we can really do until we get some ubuntu core devs to push sru's to archive.
[18:07] <soee_> sgclark: why they dont give you or yofel access to do it ?
[18:08] <sgclark> we have to go through the same process as everyone else.
[18:09] <soee_> sgclark: what do you think about this patch to test ?
[18:09] <sgclark> which I will be working on soon. Time is always an issue, as usual. I need to clone myself.
[18:10] <sgclark> soee_: sorry I have no clue what that is or what it is for. Perhaps yofel does.
[18:11] <soee_> sgclark: it should probably fix teh bug i reported  - when the updates notification stays active in systray when there are no any update sleft
[18:12] <BluesKaj> that's an old one, been around for ages
[18:13] <soee_> BluesKaj: yes but finall we might have fix for it :)
[18:13]  * BluesKaj doesn't bother with active notifiers\, update and upgrade every day anyway
[18:13] <BluesKaj> soee_, you hope  :-)
[18:23] <yofel> sgclark: that's just a discover patch to fix the forkbombing
[18:23] <yofel> soee_: I'll apply it later, unless clivejo isn't faster
[18:23] <sgclark> ok col
[18:23] <sgclark> err cool
[18:26] <yofel> hm, if the sound issue is sddm related, then this might be indeed a logind permission issue somewhere
[18:27] <soee_> yofel: thank you
[19:50] <tybaut> Hello
[19:50] <tybaut> I'm with xenial
[19:50] <tybaut> With plasma 5.5.4
[19:51] <tybaut> It's working fine
[19:53] <tybaut> I have only one problem. When i want use krunner (alt+F2), when I write the applications name, there isn't autocomplete and I can't launch the application (for ex. konsole) with enter touch
[19:54] <sgclark> hmmm. works for me. anyone else experience this?
[19:54] <soee_> also here works fine
[19:54] <soee_> tybaut: open krunner settings and check if all options are selected
[19:55] <tybaut> For information I have this problem for some days (plasma 5.5.3)
[19:58] <tybaut> soee:all options are selected ->  http://humeurlibre.fr/divers/captureKrunner.png
[20:04] <clivejo> working for me too
[20:07] <soee_> tybaut: try restarting krunner
[20:38] <mparillo> I earlier had a problem with autocomplete in krunner for Okular, but it went away this morning when I upgraded to -staging.
[22:41] <soee_> yofel: did you found time to add this patch to notifier ?
[23:15] <tybaut> sooe: well, same thing after restarting  - http://humeurlibre.fr/divers/krunner_restart.png
[23:16] <tybaut> I shall do new test tomorrow
[23:16] <tybaut> Good night