[01:38] @valorie, With Discover? Yeah, but only in 5.13 [01:39] it's such a shame, the 5.13 version of Discover is going to be vastly, radically better than the 5.12 version we have to ship in Bionic [01:58] Does anyone know how to check donation history other than this link? https://www.kde.org/community/donations/previousdonations.php My employer is supposed to match employee donations, I do not see any history their donation. I requested them to match my 2017 year end donation, but I don't see year end summary donation either. [02:00] nm, I found a link to kde-ev-treasurer email address.... === phoenix_firebrd is now known as phoenix_firebrd_ === phoenix_firebrd_ is now known as phoenix_firebrd === phoenix_firebrd is now known as phoenix_firebrd_ === phoenix_firebrd_ is now known as phoenix_firebrd === phoenix_firebrd is now known as phoenix_firebrd_ === phoenix_firebrd_ is now known as phoenix_firebrd [06:14] https://kubuntu.org/news/kubuntu-bionic-beaver-18-04-lts-beta-2-released/ [06:19] yay! [06:56] https://twitter.com/kubuntu/status/982149871149858817 [08:22] -kubuntu-ci:#kubuntu-devel- Project merger_kdeconnect-kde build #512: FAILURE in 7.8 sec: https://kci.pangea.pub/job/merger_kdeconnect-kde/512/ [08:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #378: STILL FAILING in 5 min 39 sec: https://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/378/ [08:27] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdeconnect-kde build #205: STILL FAILING in 5 min 43 sec: https://kci.pangea.pub/job/artful_unstable_kdeconnect-kde/205/ [08:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [08:28] -kubuntu-ci:#kubuntu-devel- Project merger_kdeconnect-kde build #513: FIXED in 10 sec: https://kci.pangea.pub/job/merger_kdeconnect-kde/513/ [08:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #379: STILL FAILING in 3 min 37 sec: https://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/379/ [08:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdeconnect-kde build #206: STILL FAILING in 3 min 42 sec: https://kci.pangea.pub/job/artful_unstable_kdeconnect-kde/206/ [09:03] yofel: I assume these can be binned? https://code.launchpad.net/~kubuntu-ppa/+recipes [09:11] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2158: SUCCESS in 49 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2158/ [09:11] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2158: SUCCESS in 1 min 15 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2158/ [09:14] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2158: SUCCESS in 4 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2158/ [09:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #380: STILL FAILING in 2 min 37 sec: https://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/380/ [09:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdeconnect-kde build #207: STILL FAILING in 2 min 43 sec: https://kci.pangea.pub/job/artful_unstable_kdeconnect-kde/207/ [10:31] Hi folks [12:00] s there any particular reason why KDE Applications 17.12 never got from the "Kubuntu Staging KDE Applications" (https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/beta?field.series_filter=artful) into the "Kubuntu Backports" from 17.10 (Artful)? [12:01] * Is there... [13:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #381: STILL FAILING in 2 min 37 sec: https://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/381/ [13:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdeconnect-kde build #208: STILL FAILING in 4 min 23 sec: https://kci.pangea.pub/job/artful_unstable_kdeconnect-kde/208/ [14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2159: SUCCESS in 1 min 8 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2159/ [14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2159: SUCCESS in 1 min 34 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2159/ [14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2159: SUCCESS in 4 min 37 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2159/ [14:51] rikson43 [15:40] oops wrong chan [15:40] @nggraham, That's true for everything KDE makes. Rarely do the release schedules work out [15:41] and the next thing is always going to be 'the best' [15:43] @acheronuk, Not always. :refraining from perfectly setup joke on other DEs: [15:43] ok. I meant in the minds of their creators, at least [15:44] reality may differ [16:06] Kubuntu News page about Beta 2 (and Beta1) contains basically no info at all. … It links to the wiki for the release which has a few things sure but not a lot. … https://kubuntu.org/news/kubuntu-bionic-beaver-18-04-lts-beta-2-released/ … in contrast, compare it to Ubuntu MATE which has an incredibly useful blog post for the release, http://ubuntu-mate.org/blog/ubuntu-mate-bionic-beta2/ [16:08] @acheronuk, Martin has the time and is paid to write copiously [16:09] @acheronuk, Michael has the willingness to fix said blog issue if Rik, or whoever, were to provide a list for things to put on the page. :) [16:30] hi everyone, the channel is quite silent today :D, I upgrade my kubuntu 18.04 32 on the testing machine and I saw an upgrade of xserver-xorg and xorg and many other, should I try again to install the nvidia driver !?!, because until yesterday installing the nvidia 304 driver from the ppa "graphics-driver" I always got the graphic system compromised, recoverable removing completely the driver and reinstalling feww things .... [16:34] 304 is not supported on 18.04. Ubuntu removed it, and as far as I can tell, the module will fail to build with kernel 4.15 [16:38] acheronuk: it means i'll never able to install the 304 nvidia driver ?, because for my old graphic card is the laston I can use [16:42] AlexZion: well, there is a patch that allegedly fixes it. just a question of whether that can be put in the drives ppa or not [16:42] ^^ mamarley ? [16:42] *drivers [16:43] acheronuk: what patch are you talking about ? [16:46] patch isn coment #2 of https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750 [16:46] Launchpad bug 1737750 in nvidia-graphics-drivers-304 (Ubuntu) "nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2" [Medium,In progress] [16:49] I would stree, I haven't even tested the module build with that, and certainly don't have hardware to test on [16:49] *stress [16:49] * acheronuk is having a bad typing day [16:54] no problem acheronuk I have the hardware to test it :D === himcesjf_ is now known as him-cesjf [17:09] acheronuk: Oh, sorry, I have been really busy and totally forgot about that. Maybe this afternoon or tomorrow? [17:09] AlexZion: ^^ [17:10] mamarley: Kool. no worries. [17:10] It wouldn't be in the main PPA though, it would be in one of my test PPAs to start with., [17:14] fair enough. I expected something like that. I could have a go patching and putting somewhere, but would be better done by someone who is familiar with that packaging [17:22] <_db_> Good evening, thank you for the great beta 2 release, and for the greatly improved default settings [17:24] <_db_> Imagine the issue of mounting LUKS encrypted volumes will be fixed for final release? https://github.com/pop-os/pop/issues/163 https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757321 (apologise if should be asking this on #kubuntu) [17:24] Launchpad bug 1757321 in udisks2 (Ubuntu) "udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic]" [High,Triaged] [17:27] what the DM on kubuntu 18.04 I mean for sure isn't ligthdm anymore , rigth ?, I need to stop it in order to install the patched nvidia driver [17:27] sddm [17:27] thanks blaze ;) [17:28] _db_: from the remarks in the bugs, I would hope so! [17:28] but it is mostly out of Kubuntu's hands [17:28] <_db_> acheronuk: thanks [17:29] <_db_> currently creates a bit of a catch 22 situation while trying to install, network pass is stored on encrypted partition, can't access the network to install the required lib. There's workarounds, but hoped might be fixed for beta 2 :) [17:32] mhhh, a strange message appear during the installation, saying something like "to support your GeForce 6600 you need the 304.xx driver, your graphic card is not supported by this driver", the driver is the 304.106 I don't understand, should I try as well ? [17:35] AlexZion: I don't know what is going on there. I have never used that driver or had such a card. [17:48] well acheronuk the nouveau driver is blocking my installation, how should I blacklist it ? [17:59] AlexZion: interesting. this was said on another channel earlier [17:59] [18:19] infinity: I appear to have an issue with software-properties, it no longer appears to deal with nvidia conf files, hence on reboot nouveau is still blacklisted and nasty 640x480 desktop : bug 1761593 [17:59] bug 1761593 in software-properties (Ubuntu) "Uninstall left nouveau blacklisted" [Undecided,Confirmed] https://launchpad.net/bugs/1761593 [17:59] so maybe the converse is true as well [18:01] <_db_> if dev team encourage feedback, what are thoughts on the following minor tweak... when sorting desktop by name 'Home' and 'Wastebin' remain prioritised before other files/folders? [18:06] _db_: is that possible? [18:09] <_db_> programmatically yes, at least it is with other dm [18:09] <_db_> so assuming it will be [18:11] <_db_> so saying, just been trying different desktop sort by methods, appears might be an unfinished implementation. Icons jump erratically after choosing sort by name then adding a new folder [18:12] _db_: programmatically most things are. at this stage though, there would need to be a default setting we can tweak to do it. if there is not, there would need to be a proposal to make changes to upstream code for a future plasma release [18:33] <_db_> in beta 2, the 'show desktop' panel widget is a welcome addition, the symbolic style icon seen when reducing panel height possibly works better, in keeping with system tray icons? [18:34] _db_ what do you think of the hybrid theme in 18.04 beta? (hybrid theme = dark panel/menu with light applications) [18:35] _db_: yeah, I think so too, but I played around with trying to change that, and just caused other issues, so left it and the panel at default height [18:35] <_db_> really like the dark panel [18:36] most users seem to like the change [18:36] _db_ great. :) thank you for the feedback [18:37] <_db_> I also prefer the default panel height, only played with the height to compare symbolic icons [18:38] I'll maybe have another look. maybe I can script an icon change into the panel layout [18:42] <_db_> alternatively (as an interim fudge) possibly switch the current colour icon for a symbolic style version? [18:43] question is, how? doesn't seem to expose any config. and patching the plasmaoid would be ugly [18:46] <_db_> was thinking the colour version might be an svg file that could be temporary replaced [18:51] yeah, but could make things look not too nice if people don't want the Kubuntu dark and/or panel, but still want to use that plasmoid [18:51] <_db_> true [19:04] <_db_> one last question if I may (will then leave you to enjoy your evening). Is there a reason desktop icons default to rows, rather the seemingly widely adopted columns? Thank you for your time and replies [19:05] <_db_> not a complaint, often wondered but not had the opportunity to ask :) [19:15] _db_: sorry was hacking some stuff in a VM [19:16] not that I'm aware of [19:17] <_db_> no problem, also playing, I mean 'experimenting!' with a VM :) [19:19] _db_: https://i.imgur.com/8t1FSvW.png [19:20] doesn't look quite right. had to re-purpose a svg meant for the 22px size [19:21] <_db_> nice! [19:21] I'll think about that. [19:25] it needs to scale bigger like the original so it's clear what it is [19:34] <_db_> if helpful, considering how other os have implemented this, such win 10, it can be a very narrow design and still work well without occupy much space [19:34] <_db_> occupying [19:39] Any particular reason why KDE Applications 17.12 never got from the "Kubuntu Staging KDE Applications" (https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/beta?field.series_filter=artful) into the "Kubuntu Backports" from 17.10 (Artful)? [19:46] because we have gradually been ironing out bugs with them in Bionic and would not push to backports unless happy with that status [19:47] which bugs, out of curiosity? [19:47] I assume the bug reports are submitted upstream? [19:47] packaging [19:48] ah [19:48] as for a long time we were well ahead of debian [20:02] http://www.ubuntubuzz.com/2018/04/a-preview-to-kubuntu-1804-from-beta-2.html [20:09] @acheronuk Thanks for clearing thins up. And please, don't get me wrong. I'm not complaining. I was just wondering why did KDE Plasma 5.12 and KDE Frameworks 5.44 got to the backports and KDE Applications 17.12 didn't when it was actually released before those two other major KDE projects. [20:12] everything hinges on frameworks, so that is a gimme. Plasma is high profile, in demand by users, and not too much trouble at only 40 ish source packages [20:12] applications is a monster at 200+ source packages [20:13] @acheronuk Maybe they should split it into individual applications [20:13] There a few apps that are higher profile [20:13] on par with Plasma... like Dolphin [20:13] we/I cherry picked a few things to update from that which are higher profile [20:14] petersaints: if it was all split up there would be constant work to keep up with each release schedule [20:15] it is all split up, but to cope with that many sources in a manageable way our tooling deals with them as a whole release [20:16] <_db_> bug? play a video with vlc, then using thumbnail preview controls (or context menu) after pressing pause, play button/option is un-selectable [20:17] _db_: all in vlc? [20:18] <_db_> all videos, all media? [20:19] _db_: preview controls in what? [20:19] * acheronuk uses smplayer [20:21] <_db_> supplied vlc [20:21] <_db_> vlc media player [20:21] so all an issue in VLC? [20:21] right [20:21] <_db_> sorry :) [20:24] you can play video previews in Dolphin etc, so wondered if you meant that, and it was somehow being weird when vlc took over [20:24] hmmm. vlc bug [20:24] check upstream bugs. see if it's there. [20:25] <_db_> just checked, smplayer's thumbnail/context menu controls work as expected [20:25] report a LP bug if its something we can fix [20:26] or to link upstream bug [20:26] https://trac.videolan.org/vlc/ <---- vlc bugtracker [20:26] tsimonq2 LoB still mostly doing VLC? [20:27] LoB ? [20:27] LocutusOfBorg [20:27] acheronuk: aye [20:27] upstream that I know is J-B [20:27] Or Sebastinas on OFTC. [20:27] usually in #kde-multimedia [20:28] tsimonq2: those are packagers, not upstream really [20:28] if there is a fix, or can be one, we can try to get it in [20:28] j-b is very responsive and helpful [20:29] valorie: The packagers are very knowledgeable about the packages which they maintain and I know the packagers well. [20:29] ¯\_(ツ)_/¯ [20:29] sure [20:29] ymmv [20:30] and it is possible that's a packaging bug [20:30] acheronuk: I'm also a MOTU if you have bugfix debdiffs to throw. [20:31] tsimonq2: VLC is in kubuntu set [20:31] acheronuk: oh, right then [20:32] but at this stage in the cycle, I would rather fixes were done by regular maintainers [20:32] Agreed. [20:32] So, Sebastinas on OFTC. :P [20:32] Or, #debian-multimedia. [20:32] <_db_> acheronuk: mis-understood your question, only seems pause/play is affected, other vlc controls work as expected [20:33] whoever is least likey to **** things up ;) [20:33] as VLC is a big deal [20:33] acheronuk: I can also technically do a team upload to Debian. I'm part of the multimedia team. :P [20:34] * acheronuk shrugs [20:34] whatever is best *if* we get a fix [20:34] ok [20:40] <_db_> I'll go in case discover other issues :) [20:42] <_db_> acheronuk: (and others, in case missed anyone) thank you greatly for your time and replies [20:42] thank you for your feedback! [20:43] <_db_> such a great development team [20:44] @acheronuk, valorie Thank you for your answers. I knew that packaging was hard to get right, but I thought that you could mostly automate it and get everything right for something such as KDE Applications, since they are released in bulk. But if you guys say that the packages are not stable enough yet, I trust you. ;) [20:48] they might be stable, petersaints, but they lack testing [20:48] that's our greatest need, really [20:49] people not just trying out the software but willing to take the time to file good-quality bug reports [20:49] and being willing to try patches out until things work correctly [20:51] yeah. it's probably ok, but enough small doubts in my head to stop me pushing it. plus with bionic nearing completion, whether there is much point is also coming into play [20:51] right, i don't like to consider backports as "another set of testers" [20:54] to be honesty, much of doing the staging to artful was so I could test the packaging on my machine I was keeping on artful for the time being, rather than a intention to go to backports [20:54] but that might have been a bonus [20:54] *honest [20:54] well, I had 97 updates to day or something [20:54] so once I reboot all hell could break loose [20:55] dear god please no [20:55] * acheronuk crosses fingers [20:56] it'll be fine [20:56] now that I have my travel laptop ~set up [20:56] I have an alternative [20:56] just no irc [20:57] no signal-desktop for bionic yet [21:13] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_xdg-desktop-portal-kde build #120: FAILURE in 9 min 38 sec: https://kci.pangea.pub/job/bionic_unstable_xdg-desktop-portal-kde/120/ [21:18] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #174: STILL FAILING in 14 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/174/ [21:38] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #114: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/bionic_unstable_ark/114/ [21:38] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_gcompris build #112: STILL FAILING in 35 min: https://kci.pangea.pub/job/bionic_unstable_gcompris/112/ [21:39] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_peruse build #79: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/bionic_unstable_peruse/79/ [21:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_falkon build #122: STILL UNSTABLE in 48 min: https://kci.pangea.pub/job/bionic_unstable_falkon/122/ [22:03] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kalzium build #68: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/bionic_stable_kalzium/68/ [22:03] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_falkon build #33: STILL UNSTABLE in 57 min: https://kci.pangea.pub/job/bionic_stable_falkon/33/ [22:04] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ark build #101: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/bionic_stable_ark/101/ [22:04] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kopete build #119: STILL FAILING in 11 min: https://kci.pangea.pub/job/bionic_unstable_kopete/119/ [22:08] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kopete build #76: STILL FAILING in 15 min: https://kci.pangea.pub/job/bionic_stable_kopete/76/ [22:15] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kamoso build #96: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/bionic_unstable_kamoso/96/ [22:24] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #96: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/bionic_stable_cantor/96/ [22:25] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_cantor build #78: STILL UNSTABLE in 33 min: https://kci.pangea.pub/job/bionic_unstable_cantor/78/ [22:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [22:37] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kmailtransport build #112: FIXED in 23 min: https://kci.pangea.pub/job/bionic_stable_kmailtransport/112/ [22:39] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #87: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/bionic_unstable_amarok/87/ [22:39] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #108: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/bionic_unstable_kstars/108/ [22:41] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #128: FAILURE in 32 min: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/128/ [22:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #299: STILL FAILING in 4 min 47 sec: https://kci.pangea.pub/job/xenial_unstable_krita/299/ [22:41] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_krita build #170: STILL FAILING in 4 min 35 sec: https://kci.pangea.pub/job/xenial_stable_krita/170/ [22:44] -kubuntu-ci:#kubuntu-devel- Project artful_stable_krita build #222: STILL FAILING in 7 min 27 sec: https://kci.pangea.pub/job/artful_stable_krita/222/ [22:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_krita build #236: STILL FAILING in 8 min 36 sec: https://kci.pangea.pub/job/artful_unstable_krita/236/ [23:10] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [23:10] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_krita build #82: FIXED in 1 hr 32 min: https://kci.pangea.pub/job/bionic_stable_krita/82/ [23:22] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_baloo build #74: UNSTABLE in 20 min: https://kci.pangea.pub/job/bionic_unstable_baloo/74/