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