[09:28] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kio build #176: STILL FAILING in 3 min 45 sec: https://kci.pangea.pub/job/artful_unstable_kio/176/
[09:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #591: STILL FAILING in 4 min 14 sec: https://kci.pangea.pub/job/xenial_unstable_kio/591/
[09:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kio build #90: FAILURE in 5 min 31 sec: https://kci.pangea.pub/job/bionic_unstable_kio/90/
[09:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kio build #177: STILL FAILING in 3 min 41 sec: https://kci.pangea.pub/job/artful_unstable_kio/177/
[09:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #592: STILL FAILING in 4 min 11 sec: https://kci.pangea.pub/job/xenial_unstable_kio/592/
[09:40] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kio build #91: STILL FAILING in 4 min 44 sec: https://kci.pangea.pub/job/bionic_unstable_kio/91/
[09:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2106: SUCCESS in 52 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2106/
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2106: SUCCESS in 1 min 9 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2106/
[09:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2106: SUCCESS in 3 min 50 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2106/
[10:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #593: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/xenial_unstable_kio/593/
[10:35] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kio build #178: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/artful_unstable_kio/178/
[10:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #594: STILL FAILING in 2 min 41 sec: https://kci.pangea.pub/job/xenial_unstable_kio/594/
[10:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kio build #179: STILL FAILING in 2 min 42 sec: https://kci.pangea.pub/job/artful_unstable_kio/179/
[11:00] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:00] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kio build #92: FIXED in 28 min: https://kci.pangea.pub/job/bionic_unstable_kio/92/
[11:47] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #105: FAILURE in 4.1 sec: https://kci.pangea.pub/job/merger_amarok/105/
[11:53] <BluesKaj_> Hi folks
[12:00] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #106: STILL FAILING in 4.1 sec: https://kci.pangea.pub/job/merger_amarok/106/
[12:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:08] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #107: FIXED in 9.5 sec: https://kci.pangea.pub/job/merger_amarok/107/
[12:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #34: STILL FAILING in 4 min 1 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/34/
[12:13] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #46: STILL FAILING in 5 min 1 sec: https://kci.pangea.pub/job/artful_unstable_amarok/46/
[12:14] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #108: FAILURE in 4.6 sec: https://kci.pangea.pub/job/merger_amarok/108/
[12:16] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #46: STILL FAILING in 7 min 48 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/46/
[12:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #35: STILL FAILING in 3 min 53 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/35/
[12:24] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #47: STILL FAILING in 5 min 47 sec: https://kci.pangea.pub/job/artful_unstable_amarok/47/
[12:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:26] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #109: FIXED in 12 sec: https://kci.pangea.pub/job/merger_amarok/109/
[12:27] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #47: STILL FAILING in 5 min 40 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/47/
[12:31] <acheronuk> mparillo: if you have been trying frameworks 5.44, please comment on this if you can: https://bugs.launchpad.net/ubuntu/+source/plasma-framework/+bug/1754825 
[12:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #36: STILL FAILING in 4 min 47 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/36/
[12:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #48: STILL FAILING in 4 min 55 sec: https://kci.pangea.pub/job/artful_unstable_amarok/48/
[12:31] <acheronuk> ^^ ditto for blaze, mamarley DarinMiller etc
[12:32] <mamarley> Done. :)
[12:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #48: STILL FAILING in 5 min 48 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/48/
[12:33] <acheronuk> ty :)
[12:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #37: STILL FAILING in 2 min 53 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/37/
[12:41] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #49: STILL FAILING in 4 min 38 sec: https://kci.pangea.pub/job/artful_unstable_amarok/49/
[12:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #49: STILL FAILING in 5 min 31 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/49/
[13:03] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #110: FAILURE in 4.1 sec: https://kci.pangea.pub/job/merger_amarok/110/
[13:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:06] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #111: FIXED in 10 sec: https://kci.pangea.pub/job/merger_amarok/111/
[13:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #38: STILL FAILING in 3 min 56 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/38/
[13:12] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #50: STILL FAILING in 5 min 57 sec: https://kci.pangea.pub/job/artful_unstable_amarok/50/
[13:13] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #50: STILL FAILING in 6 min 55 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/50/
[13:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #39: STILL FAILING in 3 min 53 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/39/
[13:22] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #112: FAILURE in 3.7 sec: https://kci.pangea.pub/job/merger_amarok/112/
[13:23] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #51: STILL FAILING in 5 min 36 sec: https://kci.pangea.pub/job/artful_unstable_amarok/51/
[13:23] <mparillo> So many VMs with BB Beta1 testing. I cannot remember which (if any) had FW 5.44. Looking now.
[13:24] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #51: STILL FAILING in 5 min 41 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/51/
[13:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:24] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #113: FIXED in 9.4 sec: https://kci.pangea.pub/job/merger_amarok/113/
[13:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #40: STILL FAILING in 3 min 43 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/40/
[13:29] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #52: STILL FAILING in 4 min 56 sec: https://kci.pangea.pub/job/artful_unstable_amarok/52/
[13:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #52: STILL FAILING in 5 min 43 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/52/
[13:35] -kubuntu-ci:#kubuntu-devel- Starting build #125 for job mgmt_pause_integration (previous build: ABORTED)
[13:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #41: STILL FAILING in 3 min 54 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/41/
[13:41] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #53: STILL FAILING in 6 min 38 sec: https://kci.pangea.pub/job/artful_unstable_amarok/53/
[14:13] <mparillo> I added my successful test results to: https://bugs.launchpad.net/ubuntu/+source/plasma-framework/+bug/1754825 and updated https://phabricator.kde.org/w/kubuntu/packaging/status/ for FW 5.44 in the staging PPA column.
[14:14] <acheronuk> mparillo: Qt 5.9.5?
[14:16] <acheronuk> thanks :)
 @nggraham please comment if you can on https://bugs.launchpad.net/ubuntu/+source/plasma-framework/+bug/1754825
[14:34] <mparillo> acheronuk: It will take me a bit to get back to that VM, so I will double check.
[14:34] <mparillo> but I will double check.
[14:35] <mparillo> This was a clean install for Beta1 testing, only adding ppa:kubuntu-ppa/staging-frameworks
[14:36] <mparillo> Others may have enabled proposed or added another PPA. Anyway, shutting down this laptop to go to the other.
[14:51] <mparillo> Sorry, Typo: s/Qt 5.9.5/Qt 5.9.4/
[14:52] <acheronuk> mparillo: figured it must be. thanks
[14:53] <mparillo> It would be nice if the text in kinfocenter was easier to copy and paste
[14:54] <mparillo> And if there were some kind of Virtual Box version of open-vm-tools-desktop.
 wait Muon instead of Discover? I thought Muon was dead?
 some guy is still semi-maintaining it
 I need to hug that guy
 https://cgit.kde.org/muon.git/
 Múon became discover no ?
 @tomazcanabrava, that's what I thought since it was called "Muon Discover"
 mostly. It doesn't do package management, while Muon does/did
 Discover is apps only
 While I do know that I think that’s a broken design in the sense that a user that’s used to discover will not be able to install a library that’s missing for an app plugin to work .-.
 can you give me an example?
 Of course :)
 generally issues like that are packaging bugs that should be resolved by the developers or apckagers themselves
 Not if the package is marked as “optional”
 if a package is markes optional but the app doesn't work without it, that's a packaging bug
 You misunderstood me
[15:35] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #114: FAILURE in 13 sec: https://kci.pangea.pub/job/merger_amarok/114/
 User installs digikam from discover, digikam is working
 The “plugins” are empty because kipi-plugins is optional
 User can’t install the kipi plugins from discover
 lp frameworks 5.44 bug report commented.
 then we need to give kipi-plugins some appstream metadata so that you can
 again, a packaging bug :)
 But kipi is not an application
 Discover absolutely allows you to install app plugins from within itself. Search for Gedit, for example:
 (Photo, 1052x966) https://irc-attachments.kde.org/aCnWo3xk/file_5132.jpg
 anything with appstream metadata gets displayed in Discover
 (Btw this is an exemplar that I don’t know if it’s working or not, just something I tougth now )
 if you give a plugin some appstream metadata, Discover can install it
 that UI that you see for Gedit? Digikam could show the same thing if we packaged the pieces properly
 same with Gwenview. Basically what I'm hearing here is that kipi-plugins isn't packaged right so it doesn't appear in Discover like it should
 let me go file a bug for that
 maybe fix it too
 Maybe a “also install development packages related to this software” could be a good option
 https://bugs.kde.org/show_bug.cgi?id=391669
 This already work for Okular, for example
 (Photo, 1052x1178) https://irc-attachments.kde.org/5wr5MaRC/file_5134.jpg
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2107: SUCCESS in 51 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2107/
[15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2107: SUCCESS in 1 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2107/
 Oh
 Can we remove the help texts ?
 The “adds support for reading” in every line is making the screen quite busy
 Perhaps a tooltip with the text ?
 that would require a bug to Okular
[15:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2107: SUCCESS in 3 min 44 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2107/
 not sure we can omit them in Discover; look again at the Gedit screenshot
 Or in a smaller font
 sure, file a bug on Discover and I'll take a look
 I'm always up for little UI improvements
 I’ll try to hack that
[17:17] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #115: STILL FAILING in 8.7 sec: https://kci.pangea.pub/job/merger_amarok/115/
 building amarok 2.9.0 for the hell of it
[17:23] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:23] -kubuntu-ci:#kubuntu-devel- Project merger_amarok build #116: FIXED in 13 sec: https://kci.pangea.pub/job/merger_amarok/116/
 @acheronuk, 👍🏼
 this KDE4 packaging isn a PITA
[18:18] -kubuntu-ci:#kubuntu-devel- Project mgmt_pause_integration build #125: ABORTED in 4 hr 43 min: https://kci.pangea.pub/job/mgmt_pause_integration/125/
[18:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #53: STILL FAILING in 59 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/53/
 what makes kde4 enviro so challenging?  Lack of KCI infrastructure or too many old depends no longer available in current DE?
 I'm more used to KF5 now, and much of the KDE4 stuff has not been updated in years
 it's just a bit crusty and old
 :)
[19:10] <IrcsomeBot2> * DarinMiller hands Rik a pair of gloves and some hipboots.
 contemplating upgrading intel laptop to 18.04 unless anyone knows a reason to wait...
[19:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #42: STILL FAILING in 5 min 37 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/42/
[19:13] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #54: STILL FAILING in 5 min 55 sec: https://kci.pangea.pub/job/artful_unstable_amarok/54/
 not heard any screams from intel users so far
[19:14] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #54: STILL FAILING in 6 min 44 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/54/
 just wanted to avoid the cart in front of the horse issue like when qt 5.9.4 was stuck in proposed(?) but was needed for the lasted fw/plasma.
[19:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #55: STILL FAILING in 58 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/55/
 nothing essential is stuck in proposed right now. it should all run fine
 GERONIMO.... 18.04 on it's way. :)
[19:23] <IrcsomeBot2> * acheronuk hopes he was right!
[19:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #43: STILL FAILING in 4 min 53 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/43/
 :) easy to fix if something was missed.
[19:24] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_amarok build #55: STILL FAILING in 5 min 41 sec: https://kci.pangea.pub/job/artful_unstable_amarok/55/
[19:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #44: STILL FAILING in 4 min 52 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/44/
[19:37] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #56: STILL FAILING in 5 min 35 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/56/
[19:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_amarok build #45: STILL FAILING in 5 min 48 sec: https://kci.pangea.pub/job/xenial_unstable_amarok/45/
[19:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #57: STILL FAILING in 58 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/57/
[21:51] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #190: STILL FAILING in 4 min 46 sec: https://kci.pangea.pub/job/mgmt_tooling/190/
[21:51] -kubuntu-ci:#kubuntu-devel- Rik Mills: amarok kf5 now master branch
[21:51] -kubuntu-ci:#kubuntu-devel- Failed tests:
[21:51] -kubuntu-ci:#kubuntu-devel- PangeaDPutTest.test_run: https://kci.pangea.pub/job/mgmt_tooling/190/testReport/junit/junit/(root)/PangeaDPutTest/test_run
[21:51] -kubuntu-ci:#kubuntu-devel- KCIBuilderTest.test_puts_log: https://kci.pangea.pub/job/mgmt_tooling/190/testReport/junit/junit/(root)/KCIBuilderTest/test_puts_log
 Well that was an adventure.  If the upgrade says process says it failed to upgrade, it's not kidding. :)
 Lesson learned: don't reboot until after resolving the upgrade issues.
[22:02] <valorie> oh gosh, what happened?
 Who knew grub menu access key changed from "shift" to "Esc"? And empty resolv.conf files are not effective for connecting to the servers for finishing failed installs....
[22:03] <valorie> ewwww
 "sudo apt dist-upgrade -d" from 17.10 laptop to 18.04 was unsuccessfull.
 has anyone seen apt stuck at 0%?  I think apt tripped over itself when it upgraded its own apt-compat file.
 ouch!
 not a problem.  I can easily recover. But I like the adventure of tring to recover.  Google search suggest an apt clean might help.
[22:10] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #58: STILL FAILING in 6 min 40 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/58/
[22:21] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #59: STILL FAILING in 5 min 57 sec: https://kci.pangea.pub/job/bionic_unstable_amarok/59/
[22:32] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_juk build #212: FIXED in 14 min: https://kci.pangea.pub/job/xenial_unstable_juk/212/
[22:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_juk build #90: FIXED in 15 min: https://kci.pangea.pub/job/bionic_unstable_juk/90/
[22:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_juk build #101: FIXED in 15 min: https://kci.pangea.pub/job/artful_unstable_juk/101/
 Here's irony for you: my recovery attempt keeps stopping on "Setting up apt (1.6~beta) ...".  I have to REISUB to restart the recovery process.  Issue happens even with apt-get.  Next attempting to remove "apt" via dpkg...and then re-install if setup recovery succeeds.
[22:38] <IrcsomeBot2> * acheronuk takes comfort in fact apt packaing is nothing to do with him
 :)
[22:40] <valorie> @DarinMiller -- use pkcon?
[22:41] <valorie> sudo pkcon refresh && sudo pkcon update is pretty awesome.....
 pkcon, dpkg, apt-get and apt fail to uninstall apt.  I will test pkcon refresh and update after my next REISUB as I am stuck at 0% again.
 pkcon fails to contact packagekit... may have to try bigger hammers...
[23:18] <valorie> yowza
[23:18] <valorie> time for a fresh install?
 it's about time for a fresh install. I can't get dpkg to configure apt.  Fortuneatley, I have a separate partitions for root and home so not a big deal.  I like to spin through the recovery process on occasion incase I can help someone who does not have separate root & home partitions.
[23:30] <valorie> yeah, me too
[23:31] <valorie> fortunately nearly all of my upgrades were successful
 Learned several things to today:  Esc is now the grub interupt key, ctrl-z works when ctrl-c fails, the recovery "drop to root" is no longer read only (yeah!) but if it is ro use "mount -o rw,remount /."
[23:37] <valorie> what is control z?
[23:38] <valorie> also you should blog about these things
 Suspend process (I rarely use it so I always forget about it).
 you can suspend and resume (fg or bg to resume in foreground or background resp).
[23:43] <valorie> cool
 does anybody know off the top of their head what the file is that contains the command used to start plasmashell?
 never mind, found it: /etc/xdg/autostart/org.kde.plasmashell.desktop
 cool, good find.