[02:45] <JanC> cbreak: you can remove the dock in default Ubuntu (it's just a Gnome shell extension)
[02:46] <JanC> also, not sure what's different about the virtual desktops?
[02:47] <JanC> possibly you want some extension to customize these too...  :)
[02:49] <JanC> also the dock can autohide, if you prefer
[04:31] <lotuspsychje> good morning
[04:46] <noel> ok i'm here
[04:46] <lotuspsychje> noel: its 6h46 here
[04:46] <noel> 6 pm?..
[04:47] <lotuspsychje> my country doesnt do am/pm
[04:47] <lotuspsychje> so 6 in the morning
[04:48] <noel> so, what you will doing, hmm my buddy heh
[04:48] <lotuspsychje> im having coffee first, read some linux news
[04:49] <noel> waw i like coffe + chocolate, are know about python language broo?.
[04:50] <lotuspsychje> im more a hardware guy noel
[04:52] <noel> what's your name broo?..can you tell me?. hehe
[04:53] <lotuspsychje> lotuspsychje :p
[04:54] <noel> haha i see in screen,it private right, sorry my bad english man
[04:55] <lotuspsychje> whats your native language noel
[04:56] <noel> i mean my language, im not study eng language
[04:56] <marcoagpinto> Hello!
[04:56] <noel> bakayaroo
[04:56] <noel> haha
[06:03] <sdfgsdfgs> konoyaroo
[08:57] <cbreak> JanC: I can assign programs to the virtual desktops somewhat easily. And when I log out and back in, the programs (at least some of them) get restarted and put into the right spot.
[08:57] <cbreak> I can arange the virtual desktops in a grid, not just a line
[08:57] <cbreak> there are keyboard shortcuts to get a grid overview of all desktops, and all windows on a desktop. And to move between desktops in various ways
[08:58] <lotuspsychje> im using the workspaces to dock extension, ill be curious to test gnomes new workspaces system
[08:58] <cbreak> when I'm using then when I hold a window, the window moves to the new desktop too, which is nice
[08:58] <cbreak> overall, the plasma thing seems a lot more customizable, and more like I'm used from MacOS
[08:59] <cbreak> there's even a small extension that moves full-screen windows to new desktops, but I'm struggling with making this work properly
[09:00] <cbreak> in addition to the virtual desktops, there are workspaces
[09:00] <lotuspsychje> !info gnome-shell-extension-workspaces-to-dock
[09:00] <lotuspsychje> this is what im using ontop 20.04
[09:00] <cbreak> "activities"
[09:00] <lotuspsychje> nicely configurable
[09:00] <cbreak> not sure what the point of those are yet
[09:00] <lotuspsychje> i never liked activities much
[09:01] <lotuspsychje> too much clicks to do what you want
[09:01] <cbreak> it seems kind of functionally overlapping with virtual desktops
[09:02] <cbreak> I already have tabs in many applications, windows, and virtual desktops, three levels of hierarchy are enough for me :)
[09:02] <cbreak> maybe I find out what they're good for eventually
[09:02] <lotuspsychje> cbreak: https://imgur.com/a/rVxHbNb mine
[09:02] <cbreak> anyway, plasma is nice
[09:03] <cbreak> lotuspsychje: yeah, I know gnome had virtual desktops too. I used them a lot. They are nice.
[09:04] <cbreak> the auto-creation is nice too
[09:04] <cbreak> but not being able to bind applications to them is annoying slightly
[09:04] <lotuspsychje> im not using it default, installed the extension from repos
[09:05] <lotuspsychje> works differently then activities/dynamic workspaces
[09:05] <cbreak> I have one virtual desktop for firefox, one for thunderbird, with split screen for mail and calendar
[09:05] <lotuspsychje> cool, sounds organised
[09:05] <cbreak> one for my main kitty terminal, some more for additional terminals and VSCode
[09:05] <cbreak> and the first for what ever other thing I do
[09:06] <cbreak> I really liked dynamically creating them in gnome, but assigning apps that are restarted on login is more important
[09:23] <cbreak> an other advantage of plasma over gnome is the file manager. Although it's only slightly better
[09:27] <cbreak> the only useful file manager I found that has miller columns was ranger. It's nice, but has its own disadvantages :)
[09:37] <cbreak> now I just have to find a way to transfer all my settings to my computer at work... :D
[15:23] <geomarcin> hello
[15:23] <geomarcin> anybody can help me with bluetooth dongle please
[15:24] <Mekaneck> geomarcin: ask in #ubuntu not here
[15:24] <Mekaneck> and please don't cross post
[15:24] <geomarcin> aske dthere they forward me here
[15:24] <Mekaneck> thanks in advance
[15:24] <Mekaneck> geomarcin: no one forwarded you here
[15:24] <Mekaneck> it was for nikolam and his rant about firefox snap
[15:24] <geomarcin> wrote me with link to here
[15:24] <Mekaneck> nope
[15:25] <geomarcin> same like here is #ubuntu
[15:25] <Mekaneck> read again
[15:25] <Mekaneck> discuss is not for support
[15:25] <Mekaneck> so keep it in #ubuntu
[15:26] <Mekaneck> and again nikolam refuses to join discuss... always the same
[15:27] <TJ-> my biggest issue with snaps is there is no standard way to get the exact source used to build the binaries
[15:27] <TJ-> how in hell is "snap reboot" a thing but not "snap source" ?
[15:29] <ravage> im totally fine with snaps for skype, discord or whatever
[15:29] <ravage> they have no source anyway
[15:29] <ravage> but a default browser should be part of the regular ubuntu archives
[15:29] <ravage> just my opinion
[15:30] <ogra> TJ-, most snaps ship their snapcraft.yaml ... thats the full build receipe and usually includes all links to all sources a snap is built from
[15:30] <TJ-> but that is a massive regression to "apt-get source" and being confident of getting the exact same source.
[15:31] <TJ-> shouldn't have to look for a yaml file and hope
[15:31] <ravage> it just feels like getting the microsoft store forces on my like in windows
[15:31] <ravage> *forced
[15:32] <ravage> and i always hated that piece of software deeply
[15:33] <ogra> well, mozilla asked for it ... was not an ubuntu/canonical decision (though indeed nobody opposed to it simply because it frees 1-2 fulltime devs to actually fix desktop ssues instead of working on the deb)
[15:34] <ravage> cant wait for new ads in firefox that will be enabled by default in the new snaps :
[15:34] <ravage> too late to take back control about that then
[15:35] <ogra> well, its a joint package ... it isnt like ubuntu devs have no control
[15:35] <ravage> we will see. i have a little more time until 22.04
[15:36] <ogra> make sure to file bugs if you hit things that dont work as expected 🙂
[15:36] <ravage> im on 20.04. everything is perfectly fine in my world yet :P
[17:33] <lotuspsychje> ravage: im going early 22.04 as soon as we have an iso
[17:39] <Mekaneck> lotuspsychje: helping during the dev cycle?
[17:39] <lotuspsychje> yeah Mekaneck always on LTS releases : )
[17:39] <Mekaneck> cool :)
[17:39] <lotuspsychje> blueskaj pinged me toolchain already launched
[17:40] <lotuspsychje> but maybe bit more patience for a daily iso
[17:42] <Mekaneck> wow, things go fast
[17:42] <lotuspsychje> yeah indeed
[17:42] <ravage> i could try early 22.04 on my private notebook for sure
[17:42] <ravage> for work i prefer a stable system
 the ubuntu jammy 22.04 LTS toolchain is already uploaded ...just switched over with 350 successful upgrades...sed'd my sources.list and changed /etc/hosts and hostname to reflect the change on my system.
[17:43] <lotuspsychje> will look like 21.10 a lot at this stage for a while
[17:43] <Mekaneck> i know
[17:43] <lotuspsychje> but still the kind of package updates will flow in fast
[17:55] <ogra> yeah, the queue-ot i #ubuntu-release is pretty busy these days (announing uploads ad syncs to jammy)
[18:02] <lotuspsychje> cool ogra
[18:20] <ogra> geez ... "the queue-bot in" ...
[18:20]  * ogra glares at his fingers
[22:16] <TJ-> Here's some impressive speed-up/size-reductions, for initramfs. https://paste.ubuntu.com/p/fJXmnyS9mr/
[22:17] <jluc>  /join #gandi
[22:17] <TJ-> 102MiB > 27MiB (26.5s > 8.1s)
[22:22] <daftykins> login required to view these days eh, boo
[22:24] <TJ-> daftykins: https://termbin.com/wexh
[22:25] <TJ-> According to Colin Watson, viewing was supposed to allowed anonymously if the post was from a logged-in account; but when using pastebinit that won't work so it is login + login
[22:26] <daftykins> aww
[22:28] <TJ-> this kernel patch I developed (4 lines) leads to 20MiB reduction in initrd size https://termbin.com/ebsp
[22:30] <daftykins> wow, what's getting messed up?
[22:30] <TJ-> how do you mean?
[22:30] <daftykins> is it correcting a mistake?
[22:31] <TJ-> no, PRUNE and FIRMWARE_LOADED allow the initramfs-tools scripts to tailor to the active system by leaving out modules and lots of firmware not required to boot
[22:31] <daftykins> ah i see
[22:32] <TJ-> Without the kernel patch there's no way to know which firmware is loaded. With it, and enabling FIRMWARE_LOADED=true the kernel log is grepped for "Firmware loaded:" lines and no other firmware is included
[22:35] <TJ-> without that, PRUNE=true can still do quite well but needs shell functions tailored to each module. In my case the amdgpu module lists 474 firmware files but only uses about 12. My filter_amdgpu() function determines the AMD GPU codename and only includes firmware files with the codename in.
[22:35] <TJ-> I've also got conditional code to disable the framebuffer hooks that include loads of VERY old legacy video drivers, and the plymouth hooks that pull in EVERY GPU and firmware files they require
[22:36] <TJ-> I've never understood why this isn't standard because there's no need for everything in the initrd unless it is a portable install on a USB device or whatever
[22:36] <daftykins> i recommend nicknaming this "speedstripes"
[22:37] <TJ-> hehehe why stripes?
[22:37] <daftykins> a bit like folks would do to their cars :)
[22:37] <TJ-> I'm about to post my initramfs-tools patches to Debian
[22:37] <sdfgsdfgs> jluc, gandi ? you mean Ganbbu ?
[22:37] <TJ-> oh!
[22:38] <sdfgsdfgs> actually Gganbu 간부  lol
[22:38] <TJ-> I need to do some boot tests in qemu/kvm too, to see how long it takes to load/decompress the various sized initrds
[22:38] <TJ-> I'm going to try and get the 'Firmware loaded:' patches into mainline kernel
[22:39] <TJ-> I'll need to add patches to dracut too; not dived into that code yet
[22:40] <daftykins> very neat, nice work!
[22:40] <daftykins> i've often begun to think that there's a lot of cruft in Linux land
[22:40] <daftykins> but i wouldn't want to go full gentoo ricer to trim things down
[22:41] <sdfgsdfgs> why u need to do all those things
[22:41] <TJ-> the code is very minimal and non-invasive so shouldn't be too difficult to get included, with these kind of benefits
[22:41] <tomreyn> TJ-: lovely. but, you'll probably be asked to answer this question next: how will you support the "user rips out graphics card 1, installs graphics card 2" sceanrio, though?
[22:42] <TJ-> tomreyn: It's up to the user; these options will be off by default
[22:42] <tomreyn> ok, you win ;)
[22:43] <TJ-> tomreyn: that won't stop the regular vga driver from operating in initrd
[22:43] <TJ-> or efifb or whatever
[22:43] <tomreyn> how about wireless :)
[22:43] <TJ-> how about it?
[22:44] <tomreyn> if i have this usb wireless dongle which needs firmware a, then replace it by usb wireless dongle which needs firmware b
[22:44] <tomreyn> okay, that's a bit of a corner case, i guess
[22:44] <cbreak> you're network booting off of wlan?
[22:44] <daftykins> eh you'd be safe in the knowledge that you know what you've done with your own system :)
[22:45] <TJ-> that's totally orthogonal really, unless it needs wifi in initrd, in which case you've got a lot more customisation needed to achieve that
[22:45] <tomreyn> oh right this is just about booting, ok ok
[22:45] <TJ-> right
[22:45] <TJ-> now that initrd.img sizes are exceeding 100MiB and hitting limits that break things
[22:46] <TJ-> I've been using these patches for a while but decided to modularise and update them today
[22:46] <TJ-> Bug #1931024
[22:46] <tomreyn> will you submit them against debian?
[22:46] <TJ-> ^^^ that's one I dealt with recently
[22:47] <TJ-> tomreyn: yes
[22:47] <TJ-> I want to get the kernel patch upstream
[22:47] <tomreyn> 😍
[22:48] <tomreyn> thanks!
[22:51] <ogra> daftykins, uh, going from gentoo and trimming things down sounds like an awful direction, you should rather go from yocto and build things up with only the bits you need 😉 way more effective
[22:51] <daftykins> those are not things i do, i think you misunderstood
[22:52] <ogra> i think i understood, just wanted to make a snarky comment 😉
[22:53] <daftykins> seems like it was wasted
[22:54] <ogra> yeah, thats my destiny 🙂
[22:54] <TJ-> now to look at the remaining files list and see what else I can leave out! See if I can get it down to 12MiB
[22:54] <ogra> TJ-, hah ... awesome
[22:54]  * ogra remembers times where we considered 2MB to big for the initrd
[22:56] <ogra> people seem to have forgotten that the initrd has exactly one purpose ... find your disk ... nothing more ... all the rest should be done from the rootfs
[22:57] <leftyfb> it is nice to have ssh access during said process for multiple reasons
[22:57] <ogra> all the time ?
[22:58] <ogra> just have a special debug initrd if you need one ... 99% of users would never need ssh access in the initrd
[22:59] <TJ-> ow! looks like all the kernels ever installed haven't completely cleaned out their /usr/lib/modules/XXXX/ directories, and the remnants of every one have been included in the initrd!
[22:59] <ogra> lol
[23:00] <ogra> initramf-tools usually only pics the versioned dir ... did that change since i looked last ?
[23:00] <TJ-> hmmmph - anyone else see this kind of thing? https://termbin.com/edf0
[23:01] <TJ-> (this is on the root-fs)
[23:01] <ogra> 34 dirs here ...
[23:02] <TJ-> arggh, I was wrong, it's not in the initrd. I just prefixed a path with / after extracting the initrd and looked at the root-fs not the initrd content!
[23:02] <ogra> most likely the modules.dep and aliases files
[23:02] <TJ-> there's no reason to keep those around is there? should be purged
[23:02] <ogra> if you do "dpkg -l linux-image" you'll see an rc entry for each of them i guess
[23:03] <ogra> kernels arent purged, just removed
[23:03] <ogra> i guess thats the issue
[23:04] <ogra> err dpkg -l | grep linux-image indeed 🙂
[23:04] <daftykins> i always purge old ones to keep the list nice and lean :)
[23:04] <daftykins> really helps for those VPSs where you have a small virtual disk
[23:05] <ogra> i occasionally do that on my machines ...
[23:40] <TJ-> what on earth is going on with apt-cache!? trying to grep output and fails to match. then tried manually "apt-cache policy nonexistentpackage" and it isn't on stdout nor stderr but redirecting either to /dev/null results in no output at all!
[23:50] <TJ-> don't think I'll get the initrd any slimer via kernel; uncompressed /usr/lib/modules/ is now just 20M. /usr/lib/ is 53M - the rest is in the various libraries to support lvm cryptsetup and so on
[23:52] <Bashing-om> TJ-: I see no issue with apt-cache here on 20.04 - got a particular I can test ?
[23:54] <TJ-> yes " apt-cache policy linux-image-lowlatency111; echo next; apt-cache policy linux-image-lowlatency111 | cat "
[23:54] <TJ-> the second invocation doesn't send anything to cat over stdout, but nothing appears from stderr either
[23:54] <TJ-> I think it is directly writing to /dev/console
[23:54] <Bashing-om> TJ-: doing
[23:55] <TJ-> same thing if we redirect both stdout and stderr "!&"  with "  apt-cache policy linux-image-lowlatency111; echo next; apt-cache policy linux-image-lowlatency111 |& cat  "
[23:55] <TJ-> err "!&" should have been "|&" of course
[23:56] <Bashing-om> redo :) .. now at >> N: Unable to locate package linux-image-lowlatency111 // next .
[23:56] <daftykins> what's with those 3 additional l's?
[23:57] <TJ-> to ensure the package isn't known
[23:57] <daftykins> ah right, ok - not really paying attention here :D
[23:57] <TJ-> so the output is "N: Unable to locate package ..." /but/ if piped to another process the output doesn't come through, from stdout nor stderr


[00:42] <mparillo> could not read control file from URL http://cdimage.ubuntu.com/kubuntu/daily-live/current/bionic-desktop-amd64.iso.zsync
[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/
[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/
[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
[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: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/
 haha sorry guys, my daughter got ahold of my computer there for a minute!
[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/
 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/
 read this: http://iso.qa.ubuntu.com/qatracker/milestones/387/builds/167653/buginstructions
 BTW thanks for helping out!
[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
 @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?
 No, I haven't seen that issue before. Also pereira_alex, does it reproduce if you set the language to English?
 @nggraham the highligt colour of the top item seems to be white, as is the text.
[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 )
[18:31] <acheronuk> pereira_alex: https://bugs.kde.org/show_bug.cgi?id=392547
[18:32] <acheronuk> https://bugzilla.redhat.com/show_bug.cgi?id=1562614
[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........
 @nggraham even before that 'glitch', I had half a mind to propose this: https://phabricator.kde.org/T8443
 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] <blaze> it's definitely color theme
[18:57] <blaze> reproduced with the deafault
 I kind of forgot about it after the sidebar view was introduced and made the default
[18:57] <blaze> *default lol
 shoot that idea down in flames if you like :D
 the problem with Tree View is that it opens to a really dated-looking welcome page
 also its navigation is not exactly fun for non-experts
 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
 FWIW I can't reproduce the sidebar issue in today's ISO
 (Photo, 634x403) https://irc-attachments.kde.org/7Y0mkz9O/file_5547.jpg
[19:30] <blaze> you didn't select the first item
 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
 though it'll be in the next 5.12.x release
 Looks fine with the first item selected too
 (Photo, 634x403) https://irc-attachments.kde.org/l9BuGB3c/file_5549.jpg
[19:31] <blaze> navigate more
 oh whoa, there it is
[19:32] <blaze> right :)
 filing a bug upstream
 can't reproduce in 5.12.4 on Kubuntu 17.10 via backports
[19:36] <blaze> it has fw 5.43
 if you click on the bold header of the main category list, the affected subcategory item suddenly looks find again...
 really weird
 https://bugs.kde.org/show_bug.cgi?id=392775
 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
 (today's daily ISO)
 https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1761592
 got a couple more last-minute suggestions, if possible
 https://phabricator.kde.org/T8445
 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 ?
 because I'm logged in with Telegram instead of using IRC
[22:16] <pereira_alex> oh
 yep
[22:16] <pereira_alex> do ppl here talk more in telegram ? i do have a telegram account
 doesn't really matter
 in general, I think IRC is preferred for philosophical reasons
 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
 haha
 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.