[00:18] valorie: Now that you mention it, Dropbox was not running. Not sure how long it has not been running. [00:22] I just stated Dropbox from my shell script, and it looks like it has not run since sometime between 4/13 and 4/28. [00:23] So nothing to do with the plasma upgrade. [00:25] sgclark: fixed a few apps, but need sleep. I don’t understand PIM or marble so I might have to leave them to someone more knowledgeable [00:29] clivejo: sleep well. I will look at those tomorrow for you. [00:29] thanks [00:29] and of course tel, you how to fix :) [00:29] there are a few oranges I can fix [00:30] looks like symbols [00:30] yeah there were tons of symbols updates [00:30] pim I think has more split out packages tbh [00:31] I am giving another attempt at fixing stable CI since we don't use namespaces it is really breaking things. [00:38] testing landing on xenial for a day, everything works well, thank you :) [00:45] ;] [04:54] finished the YY upgrade (staging-plasma, frameworks) and then removed them, and did auto-clean & auto-remove, then the shutdown choice wouldn't work [04:55] not sure it's important [04:59] https://www.dropbox.com/s/q07h2ic8ga0ja8a/error%20upgrade%20with%20staging-plasma%20%26%20frameworks?dl=0 - one error message [04:59] warnings after removing the PPAs, etc.: https://www.dropbox.com/s/ttmxczgg8716mbq/warnings%20after%20removing%20staging%20%26%20cleaning?dl=0 [06:00] Good morning. [09:30] * clivejo yawns [09:30] Morning clivejo [09:30] o/ Rick === greyback is now known as greyback|bbiab [10:23] Riddell: my membership of kubuntu-ninjas-yellow-belts expires in 7 days, do I need to get that renewed? LP email says to contact you :P [10:25] clivejo: hmm probably not, I just used that team to keep track of people I'd given training to [10:26] yofel: got any use for that team or shall I kill it? [10:26] we should probably keep it [10:27] its like handing out coloured stars to children :P [10:27] sense of achievement [10:31] weee :) [10:31] i have my PC + 2 screens at home now [10:32] tomorrow SSD + Kubutnu 16.04 on it [10:41] sgclark: any idea why krdc is missing from apps PPA? [10:52] * clivejo sees why, cant apply the patch! [11:11] Riddell: I agree with clive that we should keep it, even if I'm not really using it either right now [11:12] Riddell: btw. could you make a snapshot of weegie sometime in the near future so we can attempt to upgrade that thing onto a non-EOL release? [11:14] yofel: voila, I made kubuntu-council owner of team [11:14] thanks! [11:14] yofel: yes making it get set up with chef and moving to a new release is on my todo [11:14] ok thanks [11:15] Re Yellow belts [11:15] I have the Dojo starting next week [11:16] Would Yellow Belts be useful for that ? [11:17] who had this problem with windows going underpanel ? [11:17] mparillo I think soee [11:18] mparillo: ping [11:29] Hey folks [11:29] I could replicate that panel bug in VBox [11:36] @Sick_Rimmit: Well, it's currently just a badge-collection team with not practical purpose. If you can think of one feel free to suggest it [11:36] I think it could be very useful for that very purpose [11:37] yofel: give people a sense of achievement [11:37] well yes, that's why I said badge-collecting and why I said to keep the team :P [11:37] Really I am picking up on the work done by Riddell: and Sitter: the Dojo is based on their original Wiki posting [11:37] well, KC is owner now, so any KC member can add people [11:37] ie the first step at becoming a might ninja [11:37] mighty [11:38] It would be good if I had some access to add LP users, [11:38] Part of Dojo is getting em setup on LP, and I could put them into Yellow belts [11:38] We can sort the details later, just hang on to it 😃 [11:38] yofel: it's not just badge collecting, it was to help my memory on who had started package training too [11:39] ah, well, that too [11:39] @Sick_Rimmit: now you can [11:39] Riddell: do you have a link to that KDE components chart, ie how all the packages fit together? [11:39] Awesome !! Cool I will take a look later [11:40] whats the min level for LP git access? [11:40] ninjas [11:40] or member [11:40] is there a way to allow for limited access? [11:41] LP tells me I can dput to the ppas [11:41] ie the yellow belts could do an actual commit, but it would have to be reviewed before going in? [11:41] clivejo: only ones I know are at https://gitlab.com/siduction-tools/pkg-kde-graphs/tree/master [11:41] no. But we could use the team for forked repositories that the students would be able to commit to (as a team), and then file merge requests against the real ones [11:42] which is essenitally what you just said just worded in LP terminology [11:42] I think KCI is great tool for learning [11:42] ie fixing minor packaging issues [11:42] and you get to see the results pretty soon [11:42] I would still prefer a manual review *somewhere* [11:43] if we make a cronjob that would auto-merge into kubuntu_unstable (would be possible), then we would need to change staging-upload to include a manual review of each merge [11:44] or we make the script add some kind of needs-review marker, that makes the package appear read on the QA page [11:44] until someone reviewed the merge and removed the marker [11:44] that would take the load off of the intial uploader [11:45] *appear red [11:45] I still think the CI bot should have it's own channel [11:45] ahoneybun: it does [11:45] #kubuntu-ci [11:46] problem was that nobody payed attention to it there [11:46] but it does not put it's output there [11:46] sure it does [11:46] it does [11:46] but its gets more attention here :) [11:46] kinda bad to have all the red here [11:47] why? [11:47] we want to know about the red [11:47] people might be thrown off [11:47] by the red [11:47] well that's kind of the point. Show it here so that people feel like they need to fix it [11:47] uhm, this is a CI, that's how a CI works... [11:48] if Im not doing much, or notice a package in the red that I know about, it reminds me to go fix it [11:48] can take a few days to see the results [11:48] cause KCI seems to be constantly busy [11:50] soee_: you need to become a yellow belt [11:51] and acheron88 and I few others who my brain wont remember right now [11:51] * clivejo needs help with PIM [11:52] I have no idea about that [12:05] yofel: would you give me a quick how-to regarding copying a git repo from Debian to LP? [12:06] Git clone --mirror [12:06] Git push --mirror [12:06] well, got the 4.6 kernel and plasma 5.6.4 installed and all is well so far on both Xenial and Yakkety [12:06] clivejo: I heard you need packages sponsored ? [12:06] that, + edit the remote in between [12:06] clivejo: yellow belt? this? http://kubuntu.org/news/kubuntu-dojo-ninja-developer-training/ [12:06] rm origin and set it up to LP? [12:07] yes, its like the first step [12:07] and you get a little team icon on your LP page :) [12:07] https://launchpad.net/~kubuntu-ninjas-yellow-belts [12:08] I expire soon [12:09] shadeslayer: yes, Scarlett put a shout out on the ML [12:09] Link to tars plz [12:12] clivejo: ah. would need to set up another LP ID for that if I did. [12:13] shadeslayer: Im not sure how that all works [12:13] sgclark can upload existing packages, but new ones need sponsorship [12:13] And I'm asking for a link to what needs uploading :P [12:14] so I dont know if they are in some pending queue somehwere [12:14] I doubt it [12:14] You need to be MOTU to upload to approval queue last I checked [12:14] and I dont know how it works with our workflow [12:15] clivejo: you clone git, checkout the tag she crated, build a package, upload that to people.ubuntu.com or wherever so that he can dget it [12:15] Uhm OK, will wait for sgclark then [12:16] there are four packages need sponsorship - plasma-integration, kactivitymanagerd, breeze-plymouth, breeze-grub [12:16] clivejo: is LP done under Ubuntu One account still? [12:16] acheron88: I believe so [12:16] hence why I was stuck with my aol email address [12:17] clivejo: yeah but I have no clue where they are packaged xD [12:17] Or how to get them :P [12:17] So if you give me dsc's that's the best [12:17] clivejo: have one, but under a random name, so would probably need to set up a fresh one. [12:18] acheron88: maybe best to get a fresh one [12:18] you can change the ID as long as you don't have any PPA's IIRC [12:18] acheron88: Rick should be explaining all that in the Dojo session [12:19] * clivejo cant even remember doing it [12:20] a fresh one sounds better all round in long run, but I'll have a look [12:20] yofel: when Scarlett run the upload script doesnt it mod git and do what it needs to do? [12:23] clivejo: that's why I said check out the tags that the script created [12:23] then you'll get the same packages she generated [12:23] (that's what the tag is for...) [12:24] I have to go for a bit, but I need to learn this, never done it before === rdieter_ is now known as rdieter_work [13:34] soee_: Were you asking about https://bugs.kde.org/show_bug.cgi?id=362105 [13:34] KDE bug 362105 in Panel "Taskbar options 'autohide'/'windows can cover' not functional" [Major,Reopened] [14:54] ovidiuflorin: could you maybe wire the telegram<>trello integration to the dev channel? I don't think it makes much sense to keep it in offtopic [14:54] (probably just got forgotten?) [15:04] yofel: Theres a new package called kdepim-apps-libs available from download.kde.org, but it builds package called kf5-kdepim-apps-libs [15:04] how do I tell KA about it [15:04] Yofel, I tried [15:05] I shall try again [15:06] integram was added by: ovidiuflorin [15:09] clivejo: is that a renamed source or just the binary name? [15:10] seems to be just binary [15:10] the end package [15:10] @integram info [15:11] It's dead here [15:12] clivejo: then just add the source name to the application list (the list update script should've already done that?!?) [15:13] yofel: I dont know, Im working on apps [15:13] I assumed Scarlett would do that? [15:13] did she upload apps? [15:14] not ready yet [15:14] in staging [15:14] yes, I meant to staging [15:14] http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html [15:14] Im been trying to fix that I can [15:15] what [15:15] ok, so I don't understand what your original question was about? [15:16] kdepim has been divided out into new packages [15:16] yes [15:16] Im copying those from debian git to LP [15:16] okay? [15:16] and want to monitor build issues on qa [15:17] right [15:17] but they need added to the package lists [15:17] ok, but this should've been done before staging-upload was run [15:17] so you know what packages are new [15:17] and to update the list [15:17] I know, but obviously wasnt [15:18] ok, then run the list updater now [15:18] but this package kdepim-apps-libs available from download.kde.org, will be built and monitored on the build page as kf5-kdepim-apps-libs [15:20] so run ./package-name-list -d yakkety -r applications -v 16.04.1? [15:23] probably, readme should say how [15:25] but how do I point kdepim-apps-libs ==> kf5-kdepim-apps-libs so the build page can see it? [15:28] the build page cares about source names? [15:28] I thought it did [15:29] thats waht we had to map discover to plasma-discover? [15:29] yes [15:30] * clivejo is confused [15:32] well what's the source name? and what's the upstream tarball name? [15:32] (I did not look at the ppa) [15:33] the upstream tarball is kdepim-apps-libs [15:34] amd64 build of kf5-kdepim-apps-libs 4:16.04.1-0ubuntu1~ubuntu16.10~ppa1 [15:34] how the hell has it an epoch [15:34] FFS [15:37] why?!? [15:37] http://anonscm.debian.org/cgit/pkg-kde/applications/kdepim-apps-libs.git/tree/debian/changelog [15:38] my head hurts too much, need a break [16:38] yofel: where are we with backports ? [16:38] Done from a technical POV I believe, now it depends on what people say about how well it runs [16:39] all testers say its fine :) [16:40] i would say .. release the kraken [16:49] test [16:49] plasma 5.6.4 coming out????????????? [16:50] hiho darwin_ [16:50] darwin_: soon [16:51] cool [16:52] thx [17:43] !info kf5-kdepim-apps-libs [17:43] Package kf5-kdepim-apps-libs does not exist in yakkety [17:43] Scarlett said this pim is pretty hard :/ [17:46] !info libkf5kaddressbookgrantlee5 [17:46] Package libkf5kaddressbookgrantlee5 does not exist in yakkety [18:07] clivejo: sorry internet was down. looks like PIM needs a new package for libgravatar [18:07] hi sgclark [18:07] need to update you on what Ive done [18:07] so I run the package updater script [18:08] and there are lot of new packages by the looks of it [18:08] Ive been mirror cloning from debian and bringing them over to LP [18:09] but Ive run into a few problems [18:09] http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html [18:10] very end of that page are the "missing" packages [18:10] however some of them arent missing, just got different names [18:11] for example kdepim-apps-libs ==> kf5-kdepim-apps-libs [18:11] mirror cloning? [18:12] baloo-widgets ==> baloo-widgets5 etc [18:12] do you know how to fix that mapping in KA? [18:12] git clone --mirror [18:12] what did you do, why are so many apps missing now? [18:13] run the package-name-list script [18:14] it grabs all the tarball package names and compares them [18:14] on your own, I do not know what that is sorry [18:14] its part of the KA scripts [18:15] we supposed to run that before staging [18:15] so we can see removed or new packages [18:16] well that has never been told to me. [18:17] In short I cannot help you with itl. [18:17] all the apps were there and now they gone missing [18:17] dont think its mattered much in the past, it only cause there has so much code moved about to new packages [18:18] gone missing? [18:18] oh all those are new? [18:19] well kinda [18:19] some are actually in the PPA [18:19] but I cant figure out how to map them [18:20] I also dont understand how brand new packages have epochs [18:20] map them? I think they just need to be added to package list somewhere? [18:20] they are in the package list [18:20] dunno then [18:20] but there is a way to map them [18:21] for example KDE call the source tar discover, but we call it plasma-discover [18:21] in folder build-status-conf those files are updated? [18:22] thats to do with the status page? [18:22] yes [18:22] well I assume so with the build-status in the folder name [18:23] Im thinking its something to do with https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/upstream-names.json [18:23] my guess with the epochs is the package was copied from another package that had an epoch [18:24] sorry in several conversations, what to do with what?? [18:24] cause thats where the discover thing is mapped [18:24] "plasma-discover": "discover", [18:25] Im thinking if I added [18:25] "kf5-kdepim-apps-libs":"kdepim-apps-libs" to that file it might work? [18:25] sounds reasonable [18:25] try it :) [18:26] I dont wanna break it! [18:26] I'm having an issue with apt-get build-dep [18:26] sudo apt-get build-dep qtbase5-dev [18:26] Reading package lists... Done [18:26] Picking 'qtbase-opensource-src' as source package instead of 'qtbase5-dev' [18:26] well it is already broken, can't get worse haha [18:26] E: Unable to find a source package for qtbase5-dev [18:26] on xenial [18:26] with apt search I can find the package qtbase5-dev [18:26] !info qtbase5-dev [18:27] I think its a virtual package [18:27] qtbase5-dev (source: qtbase-opensource-src): Qt 5 base development files. In component main, is optional. Version 5.5.1+dfsg-16ubuntu10 (yakkety), package size 911 kB, installed size 12339 kB [18:28] sudo apt-get build-dep qtbase-opensource-src [18:28] Reading package lists... Done [18:28] E: Unable to find a source package for qtbase-opensource-src [18:28] am I missing something? [18:28] https://launchpad.net/ubuntu/+source/qtbase-opensource-src [18:29] so, do I just install that? [18:30] what are you looking for? [18:30] doing this: http://kfunk.org/2016/02/16/building-kdevelop-5-from-source-on-ubuntu-15-10/ [18:31] I think qtbase5-dev is a virtual package that installs all of the base dev packages [18:32] apt-get -y build-dep qtbase5-dev is what I use in my dockerfile for kde-ci [18:32] but it is still wily, maybe something changed? let me try in my chroot [18:33] I'm on xenial [18:33] worked fine for me in xenial chroot [18:34] ovidiuflorin: you know you can build kdevelop from source using kdebuild-src right? [18:35] oh that is whaht it is doing nm [18:39] that does not bring in all dependencies [18:40] right [18:40] sorry I don't know. wfm [18:40] I might me missing some ppas [18:41] maybe missing something in sources [18:41] 'apt-get build-dep qtbase5-dev' work here on xenial as well [18:41] no no ppas in my chroot [18:42] https://paste.kde.org/ptwe8t6ln [18:45] eakk "libkf5.*-dev" [18:45] just install whats listed in the build dep list for the main package [18:46] fixed it [18:47] source code wasn't checked in software manager [18:55] yofel: ping [19:23] just install whats listed in the build dep list for the main package [19:23] there's no kdevelop 5 package yet [19:23] easy [19:23] kfunk: was ovidiuflorin was asking [19:24] he didnt have sources enabled [19:46] kfunk add clang to the list of dependencies [20:01] and I recall it was a specific clang before I could get it to work [20:01] don't recall which though :( [20:13] well I added two to the upstream-names.json file and they wont appear on the build status page [20:40] does anyone here understand kubuntu-automatic? [20:40] automation [20:43] clivejo: ssup [20:43] I haven't looked at it in a while [20:43] hi shadeslayer [20:43] but I might be able to help [20:44] Ive added a few new packages but the upstream (KDE) name and package names are different [20:45] for example KDE tarball is discover which maps to plasma-discover [20:46] I have KDE tar called kdepim-apps-libs which maps to kf5-kdepim-apps-libs [20:46] uh huh? and? [20:46] I need it to appear here http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html [20:46] where's the code for this? [20:47] https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/ [20:47] might make sense to normalize the names btw [20:47] used to be in bzr [20:47] right [20:48] https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/upstream-names.json [20:48] yes, I added the bottom two [20:48] but still wont work [20:49] baloo-widgets5 is here https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+build/9768185 [20:49] but the page wont pick it up [20:49] https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+packages?field.name_filter=kdepim-apps-libs&field.status_filter=published&field.series_filter=yakkety [20:49] there is no https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+packages?field.name_filter=kdepim-apps-libs&field.status_filter=published&field.series_filter=yakkety [20:49] er [20:49] there is no kdepim-apps-libs [20:50] upstream call it that [20:50] then why is it looking for that [20:50] http://download.kde.org/stable/applications/16.04.1/src/kdepim-apps-libs-16.04.1.tar.xz [20:50] (see end of the qa link ) [20:50] and git is same name [20:51] but the source package is called kf5-kdepim-apps-libs [20:52] there is some way to map it [20:52] for example KDE source is called discover [20:52] but source-package is plasma-discover [20:52] and I thought upstream-names.json was the file that did the mapping [20:53] when in doubt grep is your friend [20:53] hes not being very friendly [20:54] package-name-lists/applications-yakkety [20:54] looks important [20:54] it is [20:55] ok, give me a moment to read how this works [20:55] it holds the list of all the app packages in yakkety === aaron is now known as Guest50006 [20:55] actually, I think Ive just found something === Guest50006 is now known as ahoneybun [20:55] hm? [20:55] in package-name-list [20:56] packagesRenamedFromUpstram = [20:56] ah indeed [20:56] why isn't that json parsed from that list [20:56] that looks like a more logical mapping [20:56] why are there 2 lists :P [20:56] there's also a type [20:56] *typo [20:56] shadeslayer: your guess is as good as mine! [20:57] to the blame machine! [20:57] 45c86cb5 (Jonathan Riddell 2015-06-29 13:29:58 +0200 13) packagesRenamedFromUpstram = {"kwallet": "kwallet-kf5", [20:57] *backs away slowly* [20:57] its Scottish! [20:57] Stream translates to Stram [20:58] :P [20:58] not only is the script in python, var names are in Scottish :D [21:00] indeed [21:00] great fun this packaging lark [21:01] right, lets see if that works! [21:02] I cant seem to get the logical in these scripts [21:02] and when it says upstream is the debian or KDE [21:03] well debian is now LP [21:03] now have to wait for the cron job on weegie [21:04] more scotish slag! [21:04] slang [21:07] soee: hows the testing going? [21:07] clivejo: testing what? [21:07] plasma 5.6.4 [21:07] clivejo: it is tested pretty solid. all fine [21:08] imo. we could push it to backports [21:08] how many testers are using it? [21:08] ~8 [21:08] some on severl machines [21:08] i have it on 2 also (laptop and PC) [21:08] any install issues? [21:08] nope [21:09] i did today upgrade on my PC from 5.5.5 [21:09] and can you see everything in Polish? [21:09] ;D [21:10] are you actually in Poland? [21:10] yes [21:10] interesting [21:11] is it safe to install kernel 4.5 in Xenial? [21:11] no idea [21:11] * clivejo is on Yakkety [21:13] 4.5 from where? [21:14] 24hrs on plasma 5.6.4, and not crashed it yet :) [21:17] * clivejo high-fives shadeslayer [21:17] ^5 [21:18] they are appearing http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html [21:18] gosh ... ** (appstreamcli:15884): WARNING **: Exception: Unable to get write lock on /var/cache/app-info/xapian/default: already locked [21:18] clivejo: would recommend perhaps making it so that it loads that json fole [21:18] I wonder do we also have to map it back again in upstream-names [21:19] brb reboot [21:20] in maps "spectacle": "kde-spectacle" in package-name-list, then "kde-spectacle": "spectacle" in upstream-names [21:20] so weird [21:22] clivejo: clearly key/values are switched [21:22] so it needs changing in the code logic too [21:22] to make it all consistent [21:22] so I need both? [21:25] oh I can kinda see the logic now [21:26] that script is querying depot [21:26] for all the packages listed in application 16.04.1 [21:27] so when it finds spectacle, thats mapped to our package name kde-spectacle [21:27] and the upstream-names.json file maps it back again! [21:38] ok, I'm off for the day [21:38] sgclark: clivejo if you email me a link with the tars to upload, I can sponsor them [22:36] * clivejo yawns [22:37] this is soee bored! [22:37] :< [22:37] Kubuntu does not like me [22:37] boring even [22:37] why you think that? [22:37] i can update packages list [22:37] if freezes and doing nothing :< [22:38] xenial? [22:39] yes [22:39] come help me package apps :) [22:39] then it will love you [22:39] and again ** (appstreamcli:10695): WARNING **: Exception: Unable to get write lock on /var/cache/app-info/xapian/default: already locked [22:39] fuuu xapian [22:40] never seen that before [22:40] clivejo: the only one who knows it enough is yofel or sgclark (the apps package stuff) :( [22:41] soee_: you can learn how to do some of the more routine stuff [22:41] takes the pressure off them to deal with other stuff [22:42] soee_: you coming to the party tomorrow [22:43] soee_: Does lsof show whats using it? [22:45] i killed whole /var/cache content [22:45] is tarted to work now [22:54] sgclark: ping [22:58] clivejo: whats up? [22:58] did you see shadeslayer offer to sponsor those new packages? [22:58] * sgclark scrolls [22:58] ah ok [22:59] are you ok with me tottering away at these apps? [23:00] btw soee autohide and cover work in 5.6.4 with intel [23:00] please do. I have no time [23:00] have not tried nvidia yet [23:01] can [23:01] if you ever got a chance, would you add the new packages into KCI? [23:01] im on new 367 driver [23:01] can't reboot atm trying to work on my app in QML [23:01] mm [23:01] apt update is stopping [23:01] never finishing [23:01] ScottK: you around? [23:01] even apt-get [23:01] Looks like some appstream issue, they are discussing it in #ubuntu right npw [23:02] yea on #kubuntu user already reported it [23:02] oh the apt issue? [23:02] Yep [23:02] clivejo: can you email me a list of what needs to be added I am sgclark at kubuntu [23:03] sgclark: Sort of. [23:03] in an LTS thats [23:03] that's bad [23:03] ah the apps are in https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma would that work? [23:03] ScottK: ^ [23:03] no staging-apps? [23:04] sgclark: Which packages and you've reviewed them? [23:04] they have been in testing and no I have not personally reviewed them [23:04] I am going into retirement [23:04] OK. [23:05] I'll upload them if some Kubuntu dev says they are OK but I don't have time to review them. [23:05] ok shadeslayer said he would. thank though for the offer :) [23:06] OK. [23:29] Have an error in 5.6.4 when clicking on an recent document/item in kicker/kickoff recent docs/history [23:30] Some upstream bug? [23:31] "Could not find any application or handler" for the document path, plasma error message popup [23:31] in VM and real machine [23:32] marcinsago: could not find bugs.kde [23:32] just going to check in another distro VM for 5.6.4 [23:34] OK. bug not present in chakra plasma 5.6.4 VM [23:38] reproducible in a yakkety VM with plasma 5.6.4 as well [23:41] acheron88: same here [23:41] any ideas what might be wrong? [23:41] * soee has to uninstall mainline kernel [23:42] actually I fibbed about chakra. it's on 5.6.3. I'll see if I can update that to double check against their 5.6.4 [23:43] I can confirm acheron88. Can you create a bug? and link it so I can confirm [23:44] error is generated by this I think? http://api.kde.org/frameworks-api/frameworks5-apidocs/kio/html/krun_8cpp_source.html [23:44] sgclarke: can someone else? Not got around to making new LP ID yet [23:45] I see. I do not have time I am afraid. [23:47] at moment trying to work out if it's kde bug, or a packaging one, anyway [23:49] for those that use chromium/vivaldi + intel gpu: there is some bug that makes screen blinking/flickering. As a workaround add to chromium/browser startup command: --disable-gpu-driver-bug-workarounds --enable-native-gpu-memory-buffers [23:49] acheron88: on chakra what frameworks are installed? [23:50] !info kio-dev [23:50] kio-dev (source: kio): Resource and network access abstraction.. In component universe, is optional. Version 5.18.0-0ubuntu1 (yakkety), package size 153 kB, installed size 1035 kB [23:51] but plasma 5.6.4 was built against 5.22 [23:53] chakra package naming is not very familiar to me, but - http://i.imgur.com/eBPify8.png [23:54] looks like a mix of 5.19 and 5.21 [23:54] which is odd [23:55] with as I said, plasma 5.6.3. thought they had 5.6.4, but clearly not yet [23:55] acheron88: would you ask in #kde-neon [23:56] OK. I did have a kde-neo VM, but wiped it. annoyingly [23:57] Id be interested to know if its there [23:57] they are using FW5.22 and Plasma 5.6.4 [23:59] Neon folks are EU based so might be a while before someone answers [23:59] unless a user tries it