[00:42] <mparillo> could not read control file from URL http://cdimage.ubuntu.com/kubuntu/daily-live/current/bionic-desktop-amd64.iso.zsync
=== simonquigley is now known as tsimonq2
=== DarinMil- is now known as DarinMiller
=== BionicMac-i386 is now known as BionicIBM-i386
=== Mirv_ is now known as Mirv
[08:34] <valorie> I ran most of the tests again, including the minimal install although we have no test case for that
[08:36] <acheronuk> :)
[08:36] <acheronuk> I'll do some later
[08:45] <valorie> do me a favor and look for that bug I filed about "encrypt home" being offered when it only throws an error
[08:45] <valorie> too tired to do another
[08:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2156: SUCCESS in 45 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2156/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2156: SUCCESS in 1 min 16 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2156/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2156: SUCCESS in 4 min 11 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2156/
[09:21] <BionicIBM-i386> valorie: i386 testing in progress. I put together this old machine for testing purposes. Live Session complete. I'll start Install to hard drive tests soon.
[09:59] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_krita build #168: STILL FAILING in 2 min 56 sec: https://kci.pangea.pub/job/xenial_stable_krita/168/
[09:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #297: STILL FAILING in 3 min 34 sec: https://kci.pangea.pub/job/xenial_unstable_krita/297/
[10:09] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_krita build #169: STILL FAILING in 1 min 16 sec: https://kci.pangea.pub/job/xenial_stable_krita/169/
[10:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #298: STILL FAILING in 1 min 33 sec: https://kci.pangea.pub/job/xenial_unstable_krita/298/
=== kfunk_ is now known as kfunk
[11:17] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #181: STILL FAILING in 2 hr 21 min: https://kci.pangea.pub/job/artful_unstable_kopete/181/
[11:18] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kopete build #118: STILL FAILING in 2 hr 9 min: https://kci.pangea.pub/job/artful_stable_kopete/118/
[11:20] -kubuntu-ci:#kubuntu-devel- Project artful_stable_krita build #220: STILL FAILING in 1 hr 24 min: https://kci.pangea.pub/job/artful_stable_krita/220/
[11:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_krita build #234: STILL FAILING in 1 hr 24 min: https://kci.pangea.pub/job/artful_unstable_krita/234/
[11:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #182: STILL FAILING in 5 min 32 sec: https://kci.pangea.pub/job/artful_unstable_kopete/182/
[11:23] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kopete build #75: STILL FAILING in 2 hr 14 min: https://kci.pangea.pub/job/bionic_stable_kopete/75/
[11:29] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kopete build #117: STILL FAILING in 2 hr 33 min: https://kci.pangea.pub/job/bionic_unstable_kopete/117/
[11:43] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kopete build #50: STILL FAILING in 2 hr 34 min: https://kci.pangea.pub/job/xenial_stable_kopete/50/
[12:00] -kubuntu-ci:#kubuntu-devel- Project artful_stable_krita build #221: STILL FAILING in 39 min: https://kci.pangea.pub/job/artful_stable_krita/221/
[12:00] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_krita build #235: STILL FAILING in 39 min: https://kci.pangea.pub/job/artful_unstable_krita/235/
[12:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #258: STILL FAILING in 3 hr 10 min: https://kci.pangea.pub/job/xenial_unstable_kopete/258/
[12:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kopete build #118: STILL FAILING in 39 min: https://kci.pangea.pub/job/bionic_unstable_kopete/118/
[12:53] <BluesKaj> Howdy all
[13:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #259: STILL FAILING in 56 min: https://kci.pangea.pub/job/xenial_unstable_kopete/259/
=== perezmeyer is now known as lisandro
[14:01] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_krita build #81: FAILURE in 4 hr 5 min: https://kci.pangea.pub/job/bionic_stable_krita/81/
[14:29] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Bionic Beta 2] has been marked as ready
[14:29] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop i386 [Bionic Beta 2] has been marked as ready
[14:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_trojita build #192: STILL FAILING in 3 min 48 sec: https://kci.pangea.pub/job/artful_unstable_trojita/192/
[14:55] <blaze> acheronuk: https://code.launchpad.net/~blaze/kubuntu-packaging/+git/k3b/+merge/342738
=== himcesjf_ is now known as him-cesjf
[15:02] <acheronuk> blaze: why is that patch conflicting?
[15:02] <blaze> because of my upstream changes
[15:03] <acheronuk> blaze: oh they landed? kool
[15:04] <acheronuk> blaze: I need to fix some of those missing files in the bionic archive build, so maybe update that merge when I've done that
[15:05] <blaze> ok
[15:18] <IrcsomeBot> <nggraham> `
[15:21] <IrcsomeBot> <acheronuk> ’
[15:22] <IrcsomeBot> <tsimonq2> °
[15:25] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2157: SUCCESS in 46 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2157/
[15:26] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2157: SUCCESS in 1 min 14 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2157/
[15:29] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2157: SUCCESS in 4 min 10 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2157/
[15:33] <IrcsomeBot> <nggraham> haha sorry guys, my daughter got ahold of my computer there for a minute!
=== phoenix_firebrd is now known as phoenix_firebrd_
=== phoenix_firebrd_ is now known as phoenix_firebrd
[15:56] <pereira_alex> hi... i am new in kde phabricator, can i just post a message commenting on an item on kubuntu workboard ?
[16:16] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_k3b build #191: STILL FAILING in 38 sec: https://kci.pangea.pub/job/artful_unstable_k3b/191/
[16:17] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_k3b build #85: FAILURE in 1 min 6 sec: https://kci.pangea.pub/job/bionic_unstable_k3b/85/
[16:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #230: FAILURE in 1 min 11 sec: https://kci.pangea.pub/job/xenial_unstable_k3b/230/
[16:22] <IrcsomeBot> <nggraham> yes, feel free
[16:25] <pereira_alex> btw i saw your "QA Tester / Release Reviewers" task, I am testing kubuntu 18.04 with stable kubuntu CI. how can i help ?
[16:26] -kubuntu-ci:#kubuntu-devel- Project artful_stable_k3b build #171: STILL FAILING in 10 min: https://kci.pangea.pub/job/artful_stable_k3b/171/
[16:27] <IrcsomeBot> <nggraham> read this: http://iso.qa.ubuntu.com/qatracker/milestones/387/builds/167653/buginstructions
[16:27] <IrcsomeBot> <nggraham> BTW thanks for helping out!
=== phoenix_firebrd is now known as phoenix_firebrd_
[16:27] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_k3b build #89: FAILURE in 11 min: https://kci.pangea.pub/job/xenial_stable_k3b/89/
[16:30] <pereira_alex> thanks .. i am more or less new to ubuntu, always used gentoo and latelly arch ( getting old :P )
[16:30] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_k3b build #73: FAILURE in 14 min: https://kci.pangea.pub/job/bionic_stable_k3b/73/
[16:31] <pereira_alex> ok filling bug on "ubuntu-bug systemsettings", but it doesn't seem to be official package
[16:35] <acheronuk> pereira_alex: the packages in our CI PPAs are not official. only ones in the main archive are
[16:42] <pereira_alex> ohh
[16:42] <pereira_alex> i made a video of the bug, it happened before adding kubuntu ci packages : https://youtu.be/yawL0q4EXOE
[16:46] <acheronuk> odd
[16:48] <pereira_alex> i am not on wayland or anything special
[16:49] <pereira_alex> actually between gentoo, opensuse with git packages, arch, its the first time it ever happened in here
[16:55] <acheronuk> could be a result of using kirigami git master with stable branch plasma
[16:57] <pereira_alex> is that also present in normal kubuntu 18.04 packages ?
[16:57] <pereira_alex> ( meaning the use of kirigami git master ) ?
[16:57] <acheronuk> no. we have frameworks 5.44
[16:58] <pereira_alex> weird. let me fire up virtualbox and test kubuntu 18.03 beta iso again to make really sure
[17:00] <acheronuk> ohhh. seems to be in that also
[17:01] <IrcsomeBot> <acheronuk> @nggraham is that issue one of the ones you have been fixing?
[17:03] <pereira_alex> acheronuk: yep , also happens on livedvd ( just tested it on virtualbox )
[17:17] <acheronuk> pereira_alex: how about if you switch to breeze dark?
[17:23] <IrcsomeBot> <nggraham> No, I haven't seen that issue before. Also pereira_alex, does it reproduce if you set the language to English?
=== phoenix_firebrd_ is now known as phoenix_firebrd
[17:31] <IrcsomeBot> <acheronuk> @nggraham the highligt colour of the top item seems to be white, as is the text.
=== phoenix_firebrd is now known as phoenix_firebrd_
=== phoenix_firebrd_ is now known as phoenix_firebrd
[17:33] <pereira_alex> yes, in english also happens ( actually tested it in english )
[17:33] <pereira_alex> testing now with breeze dark
[17:35] <pereira_alex> well , with breeze dark it happens and it doesnt
[17:35] <pereira_alex> with breeze dark, the text does not disappear now, but its still not selectable ( the blue highlight of selection doesn't appear )
[17:36] <pereira_alex> this does not happen if systemsettings only has one sidepane ( small systemsettings window )
=== phoenix_firebrd is now known as phoenix_firebrd_
=== phoenix_firebrd_ is now known as phoenix_firebrd
[18:31] <acheronuk> pereira_alex: https://bugs.kde.org/show_bug.cgi?id=392547
[18:31] <ubottu> KDE bug 392547 in sidebarview "The first option in SystemSettings uses white color for the text" [Normal,Resolved: downstream]
[18:32] <acheronuk> https://bugzilla.redhat.com/show_bug.cgi?id=1562614
[18:32] <ubottu> bugzilla.redhat.com bug 1562614 in plasma-systemsettings "The first option of the SideBarView of the SystemSettings is white on a light background." [Low,New]
[18:35] <acheronuk> I note fedora 27 also has Qt 5.9
[18:36] <acheronuk> Neon and tumbleweed have 5.10
[18:38] <blaze> can't reproduce
[18:41] <acheronuk> blaze: what are you testing on? Vm or real machine?
[18:42] <blaze> real machine
[18:42] <acheronuk> hmmmmmm........
[18:53] <IrcsomeBot> <acheronuk> @nggraham even before that 'glitch', I had half a mind to propose this: https://phabricator.kde.org/T8443
[18:57] <IrcsomeBot> <nggraham> unfortunately a bug in icons mode interacts poorly with the double-click setting we also set: https://bugs.kde.org/show_bug.cgi?id=377309
[18:57] <ubottu> KDE bug 377309 in general "When Dolphin icons are set to double-click mode, systemsettings inappropriately uses the same behavior in icon view" [Normal,Reopened]
[18:57] <blaze> it's definitely color theme
[18:57] <IrcsomeBot> * acheronuk likes tree view
[18:57] <blaze> reproduced with the deafault
[18:57] <IrcsomeBot> <nggraham> I kind of forgot about it after the sidebar view was introduced and made the default
[18:57] <blaze> *default lol
[18:59] <IrcsomeBot> <acheronuk> shoot that idea down in flames if you like :D
[18:59] <IrcsomeBot> <nggraham> the problem with Tree View is that it opens to a really dated-looking welcome page
[18:59] <IrcsomeBot> <nggraham> also its navigation is not exactly fun for non-experts
[19:00] <IrcsomeBot> <acheronuk> it would help if it remebered the state you left it in, but it collapses back to a small root tree
[19:21] <blaze> ah, not the color theme, first item is not selectable
[19:28] <IrcsomeBot> <nggraham> FWIW I can't reproduce the sidebar issue in today's ISO
[19:29] <IrcsomeBot> <nggraham> (Photo, 634x403) https://irc-attachments.kde.org/7Y0mkz9O/file_5547.jpg
[19:30] <blaze> you didn't select the first item
[19:30] <IrcsomeBot> <nggraham> If you want the sidebar headers to look nicer, you could cherry-pick my patch: https://cgit.kde.org/systemsettings.git/commit/?h=Plasma/5.12&id=5de538d0df406973f130b3d1aa3c2555effbe59c
[19:30] <IrcsomeBot> <nggraham> though it'll be in the next 5.12.x release
[19:30] <IrcsomeBot> <nggraham> Looks fine with the first item selected too
[19:30] <IrcsomeBot> <nggraham> (Photo, 634x403) https://irc-attachments.kde.org/l9BuGB3c/file_5549.jpg
[19:31] <blaze> navigate more
[19:32] <IrcsomeBot> <nggraham> oh whoa, there it is
[19:32] <blaze> right :)
[19:32] <IrcsomeBot> <nggraham> filing a bug upstream
[19:33] <IrcsomeBot> <nggraham> can't reproduce in 5.12.4 on Kubuntu 17.10 via backports
=== phoenix_firebrd is now known as phoenix_firebrd_
[19:36] <blaze> it has fw 5.43
=== phoenix_firebrd_ is now known as phoenix_firebrd
[19:39] <IrcsomeBot> <nggraham> if you click on the bold header of the main category list, the affected subcategory item suddenly looks find again...
[19:39] <IrcsomeBot> <nggraham> really weird
[19:54] <IrcsomeBot> <nggraham> https://bugs.kde.org/show_bug.cgi?id=392775
[19:54] <ubottu> KDE bug 392775 in sidebarview "Kubuntu 18.04: second subcategory list you navigate to has incorrect colors for the top entry" [Normal,Unconfirmed]
[20:15] <IrcsomeBot> <nggraham> lol here's a fun new bug: both the left and right buttons in the installer slideshow do the same thing, and advance the view to the right
[20:15] <IrcsomeBot> <nggraham> (today's daily ISO)
[20:23] <IrcsomeBot> <nggraham> https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1761592
[20:23] <ubottu> Launchpad bug 1761592 in ubiquity-slideshow-ubuntu (Ubuntu) "Kubuntu bionic slideshow's left and right arrow buttons use the same transition" [Undecided,New]
[20:35] <IrcsomeBot> <nggraham> got a couple more last-minute suggestions, if possible
[20:35] <IrcsomeBot> <nggraham> https://phabricator.kde.org/T8445
[20:35] <IrcsomeBot> <nggraham> https://phabricator.kde.org/T8444
[22:14] <pereira_alex> sorry, had to leave the computer
[22:15] <pereira_alex> nggraham thanks for filling the bug report
[22:15] <pereira_alex> btw ... why do you talk by the ircsomebot ?
[22:16] <IrcsomeBot> <nggraham> because I'm logged in with Telegram instead of using IRC
[22:16] <pereira_alex> oh
[22:16] <IrcsomeBot> <acheronuk> yep
[22:16] <pereira_alex> do ppl here talk more in telegram ? i do have a telegram account
[22:17] <IrcsomeBot> <nggraham> doesn't really matter
[22:17] <IrcsomeBot> <nggraham> in general, I think IRC is preferred for philosophical reasons
[22:17] <IrcsomeBot> <nggraham> and we're trying to move to replacing Telegram with Matrix in the near future
[22:18] <pereira_alex> heh :) also have a matrix account
[22:18] <pereira_alex> don't tell me that after that will move matrix to mastodon :P
[22:18] <IrcsomeBot> <nggraham> haha
[22:19] <IrcsomeBot> <nggraham> and after that we'll move to facebook chat, and after that wechat, and after that, there's an amazing chat service that this Cambridge Analytica company is working on... :p
[22:21] <acheronuk> kde git is down?
[22:21] <pereira_alex> ohh such a nice telegram chat app
[22:22] <pereira_alex> what ? no google plus ?
[22:23] <acheronuk> cgit is down anyway
[22:23] <pereira_alex> btw which channel is it ? not kubuntu or kubuntu support ? ( only ones i found )
[22:58] <nauticalnexus> valorie: hi
[22:58] <valorie> hey nauticalnexus
[22:59] <nauticalnexus> I'm here now.
[22:59] <nauticalnexus> Where's the cake
[22:59] <valorie> haha
[22:59] <nauticalnexus> You promised cake
[23:00] <nauticalnexus> :3
[23:00] <valorie> nauticalnexus is interested in supporting PPC
[23:00] <valorie> err, something close to that
[23:00] <nauticalnexus> indeedly do
[23:00] <nauticalnexus> ppc64, not el
[23:00] <wxl> which is also not ppc
[23:00] <nauticalnexus> I have an iMac G3(not plugged in) and a PowerMac G5
[23:00] <nauticalnexus> last I checked, yes, ppc64 is ppc
[23:00] <wxl> the g3 is ppc
[23:01] <nauticalnexus> it's just 64-bit ppc
[23:01] <wxl> oic
[23:01] <tsimonq2> Find someone who's willing to port all the compilation tool.s
[23:01] <nauticalnexus> Another fun fact: the G3 can run 64-bit applications, iirc
[23:01] <valorie> @nggraham is the bug with Dolphin fixed now that allows a person to do the first review of an application?
[23:01] <valorie> it wasn't fixed in bionic yet....
[23:02] <nauticalnexus> gcc is on ppc64, make is on ppc64.. everything in build-essential is on ppc64
[23:02] <valorie> tsimonq2: shouldn't there already be compilation tools since ubuntu and debian have long supported ppc?
[23:02] <nauticalnexus> What compilation tools are not? :)
[23:02] <nauticalnexus> There are.
[23:02] <valorie> they might need updating in time, but should be current now
[23:03] <tsimonq2> valorie: Is support for ppc64 merged in upstream GCC and QEMU and libc?'
[23:03] <nauticalnexus> My box runs 17.10 so, pretty up to date.
[23:03] <valorie> tsimonq2: I have no clue, but you and nauticalnexus might between the two of ya
[23:03] <tsimonq2> ¯\_(ツ)_/¯
[23:04] <valorie> or in #ubuntu-devel some people might know
[23:04] <valorie> I don't know who used to do that support
[23:04] <nauticalnexus> according to https://gcc.gnu.org/onlinedocs/gcc/RS_002f6000-and-PowerPC-Options.html
[23:04] <valorie> and bowed out
[23:04] <nauticalnexus> If they have a gigantic webpage dedicated to it
[23:04] <nauticalnexus> why wouldn't it be in upstream
[23:07] <valorie> afaik the only diff between the PPC images and others are some fiddly bits
[23:07] <nauticalnexus> ppc(again, not el) is a little different than amd64
[23:08] <valorie> of course that's the key -- having someone step up and be responsible for making those bits work -- and finding people to test
[23:08] <nauticalnexus> it's big endian, and amd64 is little endian(which is what ppc64el is)
[23:08] <nauticalnexus> basically if there's a list of numbers from 1 to 5, amd64 does 1 2 3 4 5, ppc64 does 5 4 3 2 1
[23:09] <valorie> I understand, and my "fiddly bits" is just over-simplification
[23:09] <nauticalnexus> heh, yeah it is
[23:09] <valorie> I don't have a PPC and dunno if I've ever actually seen one
[23:10] <nauticalnexus> didn't you have some sort of Macintosh? Was that before the ppc times?
[23:10] <valorie> a mac SE 20
[23:10] <valorie> looooong ago
[23:10] <nauticalnexus> Oh yeah that's a 68000
[23:16] <valorie> hmmm, reading the discussion in #ubuntu-release it sounds like there may be a respin and delay until tomorrow for the beta2
[23:16] <tsimonq2> Not really.
[23:16] <tsimonq2> Lubuntu's issue.
[23:17] <tsimonq2> But, they can't answer the question of "why in the heck is it just Lubuntu?"
[23:17] <tsimonq2> They're trying, and if anyone sees them in person, buy them beer.
[23:17] <tsimonq2> But, this won't result in a Kubuntu respin.
[23:18] <tsimonq2> If anything, it'll just mean a delay in the release time.
[23:18] <valorie> ok
[23:18] <valorie> had not finished reading
[23:18] <tsimonq2> :)
[23:18] <valorie> do you have a clue yet as to why it is just lub. ?
[23:19] <tsimonq2> Where they're at is slightly over my head.
[23:19] <tsimonq2> So, no clue.
[23:19] <tsimonq2> I have hunches that are wild shots in the dark, but otherwise nothing much.
[23:38] <valorie> sounds like fish-or-cut-bait time in there
[23:44] <tsimonq2> Yep.