[00:32] acheronuk, clivejo: Ping [00:32] BAD RIK. You know it's just apt, not apt-get! [00:32] :P lol [00:33] whats up? [00:33] How mad would you be if I staged Frameworks 5.29? [00:33] (didn't do it, just wondering if I have a goahead) [00:34] I mean just sticking it in Staging isn't a big deal, right? [00:34] Then we can test from there? [00:37] clivejo: So? You ponged? :D [00:43] not my call [00:43] Oh? [00:53] * mamarley would be a proponent of staging 5.29. :) [00:55] OK mamarley, so if I go ahead I can blame it on you? :D [00:55] I have no power here, so no. :) [01:05] I would like to discuss with someone like yofel/santa what to do about pushing to branches if we should do something like that. As at the moment it would involve using zesty archive, so we would losr our ability to push fixes on that that might be needed for FW 5.28 should 5.29 not work out for some reason. [01:06] I would suggest creating a temporary branch for now while we discuss more permanent branches. [01:06] Thoughts on that idea? [01:07] not keen on creating temp branches either [01:07] so I am a -1 for tonight [01:07] OK fair enough [01:07] but open to discussing it and maybe making a plan tomorrow at a more sensible time [01:20] I also forgot about https://trello.com/c/J5w6GdXP/246-cleaning-up-the-road-for-frameworks-5-29 [01:21] Yeah, where's Santa at? :[ [01:21] * acheronuk shrugs [01:26] Absolutely, will do, I'll ping them on IRC in a bit with a Doodle. [02:52] well all is kinda wlel with upgrade, seems every time i try to uninstall something from new discover i crash [02:52] instantly [02:53] discoer program that is [02:53] discover [04:29] !ninjas | bug 1650767 [04:29] bug 1650767 in ubiquity (Ubuntu) "zesty 17.0.4.1 installation fails (2016-12-16 image)" [Undecided,New] https://launchpad.net/bugs/1650767 [04:29] bug 1650767: yofel, clivejo, acheronuk, tsimonq2, santa_: we need your attention! [04:32] 17.0.4.1? [04:33] Yeah I know it's a weird bug title [04:33] But it should be investigated nonetheless [04:44] naturally [05:09] * ahoneybun wakes up from sleeping for 8 hours... [05:09] 4pm to 12am is bad [05:24] valorie: Ping ping ping guess what I just did [05:24] :D :D :D :D :D :D :D [05:25] I now have a working Kubuntu Xenial Daily image with Backports preinstalled [05:25] I did it myself :D [05:25] Now I'm doing a test install in a VM to confirm it works [05:27] http://storage9.static.itmages.com/i/16/1218/h_1482038810_9988444_1b053c1f50.png [05:40] And... it successfully installed! :D :D :D [05:40] And boots! [05:40] Weeeeeeeeeee [05:41] Ok, uploading to [insert random file hosting site here], when it's done I'll post a link, someone please put it in a better place... [05:41] And test if you want! :D [05:41] I'll submit my changes that I made to get this working as a PR tomorrow to pangea-tooling. [05:44] So it look like this will be the link when it's ready: https://mab.to/8ou7Brlgk [05:44] I'm going to go take a shower, it should be done by the time I get back... [07:14] weeee, congratulations, tsimonq2 [10:39] urgh. plasma-discover on xenial backport is indeed crashing on uninstall/install. I thought I had tested that and found it ok [10:39] there is a patch though for appstream, so building with that now [11:03] ok. sorted I think. I can no longer crash it, and fix pushed [12:26] https://www.dennogumi.org/2016/12/killing-the-redundancy-with-automation/ === GuySoft__ is now known as guysoft42 [13:20] looking at Russ answer it seems he has some problem with his setup rather than packaging: https://plus.google.com/110954078302330754910/posts/H4GR6ySAK3a?sfc=true [13:59] Hi folks [15:04] Hello @all [15:05] I asked that question already in #kubuntu but was redirected to here: Currently there are packages from plasma 5.8. I thought they should only in backports-landing cause there are in testing. Did i miss something. Are they considered stable now? [15:06] carcinoma: as answered there it is all fine :) [15:07] soee: ok, thanks [15:07] they are stable and tested but for some users might not work as expected but usually this is the hardware setup problem etc. [15:07] but as always something might be also wrong with packaging as nobody is perfect :) [15:07] if you notice any problems with packaging, please report them [15:54] soee: so, fine. after update the pc is not rebootable. just does nothing if i hit the rebbot button. very stable. [15:55] did you tried to reboot from console and than check that button again ? [15:56] will do that, but normal user will not do so. [16:02] Plasma 5.8 has a lot of chnages and probably also with the reboot/suspend etc. zone [16:02] so new packages might have influence on it [16:02] i had that to in the past [16:05] soee: after reboot the reboot button works. But, the reboot screen is nearly unreadable. everything is transparent but the text and the symbol lines. is that supposed to be that way? [16:06] can you show some screenshot ? [16:06] rq - What's the difference between: https://launchpad.net/~kubuntu-packagers/+git/ and https://launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ [16:07] very similar but not identical (i.e. one of them does not have the KA package). [16:07] DarinMiller: The former is for ANYTHING under our umbrella like pangea-tooling, kubuntu-automation etc. but the latter has just our packaging. [16:08] thanks and gm tsimonq2 o/ [16:08] o/ [16:10] Are they actually 2 separate sets of files/packages? If so, are they mirrored? Or same set of files, just presented with different filters? [16:11] reason I ask, I tried to use my git shortcut git close kp:kubuntu-automation to pull KA, but it does not work. [16:12] If the packages are identical I think I would want to update my gitconfig shortcut to point to the repo that has everything. [16:13] git clone^ (stupid muscle memory kill me on the command line aslo)... [16:17] Yes DarinMiller, different filters. :) [16:21] git fetch DarinMiller [16:23] git add FILE_THAT_BREAKS_EVERYTHING && git commit -am "Oh, harmless little change..." && git push -f origin master [16:24] tsimonq2: stop breaking things! [16:25] and stop teaching others to break stuff! [16:25] soee: i made an image and uploaded it to imgur: http://imgur.com/a/npPEh [16:25] soee: do you know what i mean? [16:31] carcinoma: seems like it missing background image [16:32] try setting it through system settings: http://i.imgur.com/jexkMIZ.png [16:41] soee: the setting seems to be ok: http://imgur.com/a/S74rA [16:47] carcinoma: strange, try purging ~/.cache [16:48] acheronuk: plasma-discover seems to be crashing in zesty unstable, any ideas why? [16:50] Thanks clivejo and tsimonq2, makes sense. Fetch makes more sense for a rookie. I playing with the clone option as that's what specified in section 2.1 in KA README.ng... [16:50] maybe same as in neon, it requires kirigami 2 [16:52] clivejo: because it is 'unstable' maybe? :P [16:53] but it shouldnt be crashing unstable [16:53] just mentally unstable [16:53] clivejo: plasma-discover crashes on my zesty box also... and the running from command line says something about kirigami. [16:53] master branches will crash sometimes [16:53] DarinMiller: yup thats what I'm thinking [16:54] and acheronuk was working on kirigami [16:54] if theres blame, theres a claim :P [16:54] there have been a lot of changes to make it kirigami 2 lately, and maybe not stable yet [16:57] plus maybe also needs a better or different appstream, packagkit etc than is in the zesty archive [16:58] soee: i removed the .cache folder but no change. i also changed the settings to disashow, apply, and back to "Einfarbig". Also, no change. Do you have another idea? [17:00] carcinoma: the nearly transparent logout background is intentional design choice by KDE in 5.8 AFAIK [17:01] carcinoma: this is logout not losck screen? [17:02] if logout than yes, it should be transparent [17:02] here is mine http://i.imgur.com/vgxXgUv.png [17:02] soee: right, logout, not lock [17:02] than it is all fine :) [17:03] soee: but why? with our background it works, but having a website in the background or a terminal this is terrible... [17:04] there is a KDE forum thread or bug I've seen on the issue somewhere I think? [17:04] maybe due to your gpu drivers it isn't blurred enough [17:04] for me it is fne [17:04] * soee afk for a while [17:06] soee: you are right, there is no blur, i will search for that KDE forum thread acheronuk mentioned [17:06] carcinoma: not sure if it was on kde forum itself. I read too many forums to recall exactly :/ [17:07] does widget blur setting affect it? [17:13] carcinoma: also seems here that KDE devs designed it assuming you would have some widget background blur enabled in desktop effects [17:13] e.g. http://i.imgur.com/NIPTakZ.png [17:13] which is probably what soee has set [17:15] acheronuk: seems to work now: i changed that option called "Verblassen" http://imgur.com/a/yYLKa like so: http://imgur.com/a/Y8tB7 (full filled checkbox, whatever the difference is here) [17:18] what could cause an upgrade from 16.04 to 16,10 to not install the latest default kernel 4.8? [17:19] acheronuk: oh, and, btw, when i change the settings back to that partial filled checkbox it still works [17:24] that was fast , latest update fixed discover crash problem when trying to uninstall [17:24] sintre: good :) [17:25] lol yea i installed a bunch of kid games for my nephew to see if any might be ufefull [17:25] i was stuck with some psybrainy game and i couldn't get rid of it lol [17:26] I dont like this new wallpaper :/ [17:26] sintre: there is always muon and synaptic package managers you can install as well as discover, which should be more reliable, if less pretty [17:26] sintre: I personally don't think discover is ready for use yet [17:27] not even in 'unstable' :P [17:27] yea i've got muon , i'll download the synaptic one a bit later and peek around that [17:27] clivejo: it's growing on me a bit now [17:28] sintre: synaptic is a bit of an old school gtk application, but it reliably does the job [17:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #73: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_discover/73/ [17:31] acheronuk: I agree, the plans at akademy sounded great, but I dont think its anywhere near show time [17:33] acheronuk: did you get a chance to test any of those ISOs? [17:41] clivejo: umm. not yet [17:45] clivejo: this still the correct place? http://kci.pangea.pub/job/iso_zesty_unstable_amd64/ws/result/ [17:46] think so [17:54] hmm. looks like our kirigami in KCI is producing KF5Kirigami2Config.cmake but discover still wants the old KF5KirigamiConfig.cmake [17:55] so discover devs need to do some catching up :P [17:55] seems so [17:55] soee: acheronuk: thank you for your help. on another pc thos problems does not occure. [17:56] carcinoma: I think the KDE devs assume certain defaults, and they may not occur depending (a) user set prefs and (b) KDE set defaults based on what it thinks your graphic card can do [17:57] e.g. if your card can do the blur or not [17:57] carcinoma: but glad you got that sorted :) [17:59] clivejo: anything particular to test with this iso? [17:59] if it actually works! [18:00] live session? install? both? [18:00] all! [18:00] happy dance [18:00] * acheronuk tries all the things [18:02] clivejo: are those isos going to go somewhere web accessible that doesn't need a KCIO login? as my DL manager got told to get lost by OpenID [18:03] eventually [18:03] if the stuff works [18:04] ok. trying live session [18:04] you got it downloaded? [18:06] yes [18:06] grrr [18:06] so jealous of fats internets [18:06] fast [18:06] 'fat' pipe [18:07] ok. a slightly old fashioned ubuiquity session flashes up, crashes, a new session tries to start (presumably the live) and that crashes to TTY login [18:08] boot shows some oldish looking purlish theming? maybe using some of the old ubuntu default settings? [18:08] probably [18:08] have you get a screenshot [18:10] logging in to TTY with user ubuntu and black password works [18:10] *blank [18:11] startx (slowly) gets me a decent looking desktop [18:12] Need to tweet the packages we pulling in there [18:13] running desktop: http://i.imgur.com/l51MNgF.png [18:13] looks good ! [18:14] trying an install to HD [18:18] installer crash [18:19] awwww [18:21] then the session crashed before I could note or screenshot that. something with qtquick in it [18:23] give it another go I think. accpeting more of the defaults [18:26] ok. goes ok. even starts copying files in the background. but as soon I click continue on the timezone screen I get this: [18:26] I think the live-cd package was a meta package to pull in all the needed pacakges [18:26] http://i.imgur.com/btCoPtP.png [18:28] On a bright note, that looks very much like: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1650767 [18:28] Launchpad bug 1650767 in ubiquity (Ubuntu) "zesty 17.0.4.1 installation fails (2016-12-16 image)" [Undecided,New] [18:28] which is a general 17.04 issue, and not this KCI iso maybe? [18:29] general kubuntu 17.04 I shoudl say [18:32] hehe [18:32] clivejo: if I Esc into the grub menu, I get: http://i.imgur.com/vscz5gK.png [18:42] but that fails also :/ [18:42] * acheronuk wishes for a text mode installer to come back [19:01] Haha, I am apparently still the author of the most recent changelog entry for Amarok because I just got an email saying that it failed to build on s390x. [19:04] If anyone is actually running Kubuntu on an IBM mainframe, that would make me laugh. [20:02] clivejo, acheronuk: You test my ISO? [20:05] not I [20:37] anyone seen Carlo V around? [20:40] acheronuk: https://rthomsen6.wordpress.com/2016/12/18/introducing-systemdgenie/ [20:54] interesting [20:59] gonna packae it up [21:06] anyone having LP issues? [21:28] What issues? [21:28] cant seem to upload [21:29] well not related to cliv , but everytime i close konsole it gives me a pop up saying applicattion closed unexpectadely [21:29] wether i do something in it or not [21:40] sintre: I have seen that before on older releases, though typically in beta releases. They typically clear up along the way. What version of Kbuntu and are you running backports? [21:41] 16.04 backports [21:41] upgraded everything yesterday [21:42] yea , people seem fast yesterday had a uninstall problem , with disocver update this morning cleared that up [21:42] it still works , but odd it keeps giving me the msg [21:42] thanks i closed it then it tells you it crashed lol :) [21:48] sintre: try closing it by typing exit in the command line. Is the crash still reported? [21:48] sintre: booting over to my 16.04 install to try myself. [21:48] let me try [21:48] yep [21:49] used exit command [21:49] same pop up [21:51] testing testing..... [21:52] nope. no crash notification here [21:52] well no clue maybe i'm unlucky but on my system 100% all the time [21:53] odd [21:53] hmm, no terminal close warning on any of my boxes: 16.04 w/ bp, 16.10 with bp, 17.04 with staging, 17.04 with unstable ppa, neon and neon dev unstable. [21:53] no clue here then [21:53] as everything is updated [21:53] well, no sintre, not unlucky. I could reproduce the discover crash, so could fix it [21:54] sintre: from a terminal type konsole & [21:54] thx for that :) [21:54] exit out of that terminal and see if an error messages is left behind in the original terminal... [21:55] a@na:~$ kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing. [21:55] https://thepasteb.in/p/xGhmnP7YGl2HM [21:55] sintre: click the little sad face in the system tray after the crash if there is one. that may be able to give you a backtrace [21:55] i dn' get a sad face [21:55] sinse upgrade yesterday [21:56] hmmm.. [21:56] https://thepasteb.in/p/nZhlArP8EJpFY [21:56] that full after that command you gave me [21:58] sintre: when you launched konsole from a terminal, did you receive the crash notification when closing the child konsole window? [21:58] if forgot let me try again [21:59] ok now konsole won't even launch [21:59] hmm [22:00] well tried launch another app see if it shook something loose but no go [22:00] brb gonna reboot [22:03] back , so maybe some extra info when trying to reboot system locked up on way out and just sat at a lil clicking line top left corner [22:03] had to force shutdown [22:08] sounds like you might be fighting a plasma issue. I suggest restarting plasma for quicker turnaround: killall plasamshell && plasmashell & [22:08] When you say force shutdown, in what manner? REISUB? [22:08] hit power button [22:09] and hold it [22:09] yep same thing just tried console again [22:09] ahh another enigma hehe [22:09] Are you aware of the REISUB option? It's a little gentler on the OS than holding the power button. [22:09] ? [22:10] is that a command? [22:10] restart? yea used that thats when it locked up [22:11] Its a way to restart your PC assuming the keyboard still works. https://en.wikipedia.org/wiki/Magic_SysRq_key [22:11] ok i did the command again and no when i did it and poped second console up it did not give an error [22:12] https://thepasteb.in/p/JZhp3gjyqPJTg [22:12] same msg i believe [22:12] acheronuk: kirigami seems to have lost its VCS in unstable branch? [22:13] oops closed wrong window there [22:13] :) [22:14] clivejo: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kirigami/tree/debian/control?h=kubuntu_unstable [22:14] sintre: let's continue this conversation on #kubuntu as I think it may be more of a config issue than a packaging problem. [22:14] clivejo: indeed [22:15] ok [22:15] clivejo: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kirigami/commit/?h=kubuntu_unstable&id=9e61884a5c3a26e990d1837f9ca35750dea9bf5f [22:17] * clivejo shrugs [22:18] and now we have Neon changelog entries [22:18] yipppeee [22:20] to be fair, then is via debian [22:20] *that is [22:38] well last trouble shot for the night [22:38] https://thepasteb.in/p/Elh1VkZwYrMfm [22:38] got a sad face with using a guest account [23:16] mamarley, i'm so sorry =) there is no explicit support or work done to have any graphical environment up on s390x [23:16] that's across *buntu [23:30] http://www.omgubuntu.co.uk/2016/12/install-kde-plasma-5-8-lts-ubuntu