[00:02] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Bionic Final] (20180421.1) has been added
[00:02] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop i386 [Bionic Final] (20180421.1) has been added
 Anyone else have issues with the control file on today's qatracker? http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/170821/downloads
[00:06] <mparillo> I will try to zsync the .iso, in five minutes.
 Ah, the images aren't quite there yet.
 Give it an hour or two, and if they aren't there, I'll shout loudly.
 ah, nm then. I will wait :)
[00:16] <mparillo> zsyncing from http://cdimage.ubuntu.com/kubuntu/daily-live/current/
[00:16] <tsimonq2> I would wait a little bit longer.
[00:19] <mparillo> Understood, but I have not zsynced since an first beta image, so rather than race back upstairs to kill it, I figure it will make the next zsync faster.
[00:20] <tsimonq2> OK.
[00:20] <tsimonq2> Right.
[00:20] <tsimonq2> Can anyone repro this? bug 1755912
[00:21] <tsimonq2> Oh. Sigh. You need upload access to the Ubuntu archive to see it. >_<
[00:21] <tsimonq2> tl;dr: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl 
[00:21] <tsimonq2> Artful and Bionic guests.
[00:33] <valorie> fiddlesticks, I've started putting out the call
[00:33] <tsimonq2> Nah, I'd say go ahead.
[00:33] <valorie> I'll wait a bit to publish on the website then
[00:33] <tsimonq2> I'll continue to shout loudly.
[00:34] <tsimonq2> Nevermind, there they are.
[00:35] <tsimonq2> Full speed ahead!
[00:39] <valorie> just gotta check my links on the news story
[00:39] <tsimonq2> OK.
[00:47] <valorie> https://kubuntu.org/news/bionic-18-04-release-candidate-images-ready-for-testing/
 One of my older laptops, running 18.04 w/ NVidia 340 driver, says Power Managment module could not be loaded. The PM moduel appears to not be running... solve by scheduling or starting in the Startup and Shutdown.  I have never seen this before and none of my other systems have that module running.
[00:55] <valorie> weird
 Power management was working fine prior updates.
[00:55] <valorie> so this is an update, not a fresh install
 I will use this sytem to test the daily download.  But I have never seen this issue.
[00:55] <valorie> freakin' nvidia
[00:56] <valorie> I keep holding my breath after every update
 Correct.  It's one of the systems I used to test the beta release.
[00:57] <valorie> well, I figure if you file a bug they will say "fresh install doesn't do that
[00:57] <valorie> "
 yeah, no worries.  I thought I would mention it to see if anyone else has seen the same.
[00:58] <valorie> not yet
[00:58] <valorie> knock on wood
[00:58] <valorie> grrrr, can't login to kubuntuforum
[00:58] <valorie> anybody got a working login to post the link to the news story?
 yes
[01:05] <valorie> thanks, acheronuk
[01:05] <valorie> https://twitter.com/kubuntu/status/987859201870315520
 @tsimonq2 isos are still guarenteed at least one respin?
 @acheronuk, Yes.
[01:08] <valorie> Adam's email said something like known bugs which will be fixed by Monday.....
[01:08] <valorie> :-)
[01:08] <valorie> acheronuk: aren't you on vacation?
 so are we really going to ship with https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1761592? It's still present in today's ISO
 @valorie, no. where did that idea come from?
 valorie: https://www.kubuntuforums.net/forumdisplay.php/30-Kubuntu-Announcements
 2am here, so not going to start testing images until tommorow
 Perfect time to test. :P
 @nggraham, if no other bothered to fix, I guess so
 sigh
 I'll see what I can do.
 \o/
 @acheronuk, and.............. 😴💤
 If you ever want to venture to Boise, ID USA, you can stay my house.
[01:52] <valorie> same here if anyone ventures close to Seattle!
[01:52] <tsimonq2> ;)
 or Albuquerque NM!
[01:53] <valorie> bed isn't *that* bad, tsimonq2 can verify
[01:53] <tsimonq2> Although I kept pushing the pillow off the back of the bed. :P
[01:54] <tsimonq2> But yes, it's a nice place. :P
[01:54] <tsimonq2> *:)
[01:54] <valorie> solution: skootch the head of the bed closer to the wall
[01:54] <tsimonq2> I thought you had something on the wall behind the bed, don't remember.
[01:58] <mparillo> No dead kittens in a VM with today's ISO. Good night all
[01:58] <mparillo> And G+'d
 Driver manager failed to properly install NVidia 340 driver... attempting NVidia ppa (even though version is the same) with command line install.
[01:59] <mparillo> There was somebody in the support channel with NVidia problems.
[01:59] <mparillo> I think on the beta image.
[02:01] <valorie> mparillo: reported on iso.qa?
 I have 2 other 18.04 boxes running NVidia.  The NVidia 760 box is running perfectly.  The 960M laptop feels stuttery compared to 17.10. Glxgears is about 5% slower on 18.04 on the 960.
 Not yet, still troubleshooting.
[02:02] <valorie> ok
[02:03] <valorie> my zsync of amd64 is done, so it's time to write a usb drive
 nvidia ppa "fixed" the problem.  I will try a 2nd install (OEM) and run command NVidia install from repos (without ppa)... maybe the Driver Manager is failing (I don't see how though)
 Side note: NVidia drivers are definilty the cause of the Power Managment module issue mentioned above.  It was working fine before installing the NVidia drivers.
[02:10] <valorie> mparillo: you say in your test that it succeeded
[02:11] <valorie> but you marked it failed
 @mparillo, Yes, I think I saw the same post.  We used to be able to fall back to the 304 drivers on legacy NVidia hw.  But somebody was mentioning that may no longer be an option.
[02:12] <valorie> mparillo: both your tests are marked failed
 Very strange. Installing the NVIdia drivers from the command line worked fine (other than plasma crash at the end of the install, par for the course with NVidia legacy).  And power management issue is also fixed!???!!!.  Lesson learned: avoid the Driver Manger and the NVidia PPA on legacy  NVidia hw.
 Lesson learned: avoid NVIDIA :)
 Attempting 2nd legacy laptop install now with slightly older NVidia card (8600M).
 LOL, yes.
 I was just doing this rigimarole at work for a whole linux cluster, in fact. Those damn drivers are *always* a nightmare
 all my NVidia stuff was purchased before AMD open sourced their HW specs.
 you know what would really be aweseome is if all of custom settings were saved on our favorite "cloud" and after a fresh install, we just login and all of our KDE, bash, and ohter setting are magically synchronized.
 on the 2nd nvidia system, the driver manager when throught the motions, acted like it was compiling the driver, but did not complete the install.  Attempting to use the DM again.... this is not the 1st time I have seen the DM fail on 1st attempt....
 Driver Manager succeeded on 2nd try.  So I will file a bug again it.  Does anybody know the driver-manager package name? It launches un kcmshell5 as KDriver Manager, but running locate against "kdriver" or "manager" reveals nothing.
[03:38] <valorie> apt search says: 
[03:38] <valorie> kubuntu-driver-manager/bionic,now 15.10ubuntu4 amd64 [installed]
[03:38] <valorie>   Driver Manager for Kubuntu
[03:38] <valorie> kubuntu-driver-manager-dbg/bionic 15.10ubuntu4 amd64
[03:38] <valorie>   Driver Manager for Kubuntu -- debug symbols
 Duh, thanks!
[03:39] <valorie> lol
 So is Rohan Garg still around?  He was the last maintainer of kubuntu-driver-manager...
[03:52] <tsimonq2> He's shadeslayer. :)
[03:52] <tsimonq2> (Who is in IRC.)
 Ohhhhh
 His git repo homepage is dead: http://quickgit.kde.org/?p=scratch/garg/kcm-driver-manager.git
 https://cgit.kde.org/scratch/garg/kcm-driver-manager.git/
 hasn't been updated in 3 years though...
 hmmm, since this is just wrapper(?) or front end for ubuntu-driver-common, I wonder if the NVidia problem is in that package... might have to download regular Ubuntu to test....
 OK, taking one for the team... installing Ubuntu to test the driver manager
 Thank you!
 well, on a positive note, the gnome slide show slides the correct direction corresponding to the button pushed...
[04:30] <valorie> ha
[04:30] <tsimonq2> https://code.launchpad.net/~tsimonq2/ubiquity/remove-encrypt_home-qt/+merge/343759
[04:30] <valorie> supposedly tsimonq2 has a patch for that
[04:31] <tsimonq2> The patch for that comes next.
[04:31] <valorie> weeeeeeeeeeeeeeeee
[04:31] <valorie> nice
[04:31] <valorie> ty
[04:31] <tsimonq2> But, I discussed that one with Rik.
[04:31] <tsimonq2> np
[04:31] <valorie> that was most annoying
[04:31] <tsimonq2> This right here: https://code.launchpad.net/~tsimonq2/ubiquity/remove-encrypt_home-qt/+merge/343759 is because if you check the thing to encrypt your home directory, it doesn't work.
[04:31] <tsimonq2> The GTK frontend removed the checkbox.
[04:32] <tsimonq2> So rather than fixing the thing, since it no longer has security support (ecryptfs is dead), this makes it consisten,
[04:32] <tsimonq2> s/en,/ent./
[04:34] <valorie> which is what my BR said
[04:35] <tsimonq2> I'm not sure we're talking about the same thing.
[04:35] <tsimonq2> Could you link me to your bug report?
[04:35] <valorie> yeah, lemme search my email
[04:36] <valorie> https://bugs.launchpad.net/bugs/1761396
[04:37] <tsimonq2> ohhhhhhh
[04:37] <tsimonq2> I didn't see that.
[04:42] <tsimonq2> slideshow arrow bug> Figured out where the bug is. It's been there since *2013* it seems!
[04:42] <tsimonq2> We can blame Aurélien Gâteau. :P
[04:44] <valorie> you just can't trust a man named for cake
[04:44] <valorie> lol
[04:44] <tsimonq2> hahahaha
 interesting....regular ubuntu requires REISUB due to lockup on restart  (occasionally see this on Kubuntu but less frequently these days).
[04:45] <valorie> he andhis wife are both French, and she is a baker of quite beautiful cakes too
[04:46] <tsimonq2> Maybe this is a French stereotype, but of *course* she's good at making cake. :)
[04:46] <valorie> @DarinMiller I've not experienced that for years
[04:46] <valorie> like: 3 years
 bad news, looks like the nvidia bug is due to our installer.  NVidia installation worked fine under Ubuntu....
[04:51] <tsimonq2> valorie: https://code.launchpad.net/~tsimonq2/ubiquity-slideshow-ubuntu/lp-1761592/+merge/343760
[04:51] <valorie> \o/
[06:06] <tsimonq2> https://launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/137
 \o/
 @DarinMiller, doubt it. it's just ask qapt to install the requested package
 as far as I know, anyway
 can you maybe test if muon installs the driver ok?
 as that would be working via qapt as well
 I also note this https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1765923
 he used "sudo ubuntu-drivers autoinstall"
 and got issues
 Does it skip recommends or visa-versa?  I was able to repeat the issue twice on the same box. Ubuntu installed without issue.  I reinstalled a 4th time and skipped the Driver Manager, and the command line worked perfectly.
 Auto install is a little scary, as some 830M cards are incorrectly identified as being compatible with 384 drivers (which they are NOT!)
 @DarinMiller, unclear, but did you check what difference was in packages installed in the two types of transaction?
 Speaking of Nvidia.  The NVidia PPA show the 396 driver was uploadd, but it down not show up in apt (https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa?field.series_filter=bionic)
 s/down/does/
 how would it show up in apt? apt search?
 apt list nvidia-39*
[06:57] <acheronuk> apt list nvidia-39*
[06:57] <acheronuk> Listing... Done
[06:57] <acheronuk> nvidia-390/artful,now 390.48-0ubuntu0~gpu17.10.3 amd64 [installed]
[06:57] <acheronuk> nvidia-390-dev/artful 390.48-0ubuntu0~gpu17.10.3 amd64
[06:57] <acheronuk> nvidia-396/artful 396.18-0ubuntu0~gpu17.10.2 amd64
[06:57] <acheronuk> nvidia-396-dev/artful 396.18-0ubuntu0~gpu17.10.2 amd64
[06:57] <acheronuk> oh. duh. this is still srtful
[06:57] <acheronuk> *artful
[06:57] <acheronuk> 2 secs
 @acheronuk, What is the easiest way to check the difference?  uninstall/reinstall and compare?
 you can reboot in 2 seconds?
[06:59] <acheronuk> no, but I can log into a bionic container in 2 secs to check what apt sees
 ah
 @DarinMiller, for bionic packages they seem to have renanmed it to: nvidia-driver-396
 oh, nice catch
 So back to previous topic.  What's the best way for me bisect the legacy driver installation issue?
 396 drivers and packages not fully baked: https://paste.ubuntu.com/p/SJBkFxBNWX/
 could grep dpkg —list to see what go installed via both types? … could check apt/dpkg logs to see what each did?
 OK, will try that tomorrow as is it getting late here...
 @DarinMiller, Ok. Figured it must be! Thanks for all that
[07:45] <valorie> wow
[07:45] <valorie> we have all passing tests, even in i386!
[07:45] <valorie> blown away by all the testers this time
[07:48] <tsimonq2> I did crosspost this thing *everywhere*. :D
[07:49]  * tsimonq2 goes to bed o/
[07:51] <valorie> crimsun was testing i386 along with franklin!
[07:51] <valorie> been so long since I've seen crimsun around.....
[08:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2189: SUCCESS in 47 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2189/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2189: SUCCESS in 1 min 15 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2189/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2189: SUCCESS in 4 min 14 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2189/
[08:50] <shadeslayer> hey
[08:50] <tsimonq2> yo
[08:50] <shadeslayer> is there a bug in the driver manager?
[08:50] <shadeslayer> if someone could surmise, I'd be happy to fix it
[08:50] <tsimonq2> Cool :)
[08:51] <tsimonq2> @DarinMiller (or backlog) could prolly give you more specifics.
[08:51]  * valorie tries it out in bionic
[08:51] <valorie> shadeslayer: nice to see ya
[08:51] <shadeslayer> :)
[08:51] <shadeslayer> I'm lurking :P
[08:51] <valorie> works fine here
[08:52] <valorie> otoh this isn't a new install, it is an upgrade
[08:52] <valorie> still
[08:52] <valorie> but damn, almost 2am
[08:52]  * valorie has to give up and sleep
[08:53] <shadeslayer> night night :)
[08:59] <acheronuk> shadeslayer: thanks. some people have had issues "failed to install nvidia" whatever that means. however, there have been a plethora of issues (not just Kubuntu) with nvidia drivers with recent changes, so at the moment can't guarantee it is Kubuntu's KCM. There are also further Nvidia driver package changes in the upload queue yet to land.
[08:59] <acheronuk> in summary, hopefully we can pin things down in the next 24hrs :)
[08:59] <acheronuk> then look at solutions, if something to fix our side.
[09:05] <shadeslayer> acheronuk: ah sounds good
[09:05] <shadeslayer> I highly doubt it's on the kubuntu driver manager side
[09:06] <shadeslayer> it's super simple code, I doubt it's buggy, unless ubuntu-driver-manager changed it's machine readable output
[09:06] <acheronuk> shadeslayer: yeah, as long as it hand the right driver metapackage to qapt/apt, can't see how it can go wrong?
[09:07] <shadeslayer> yeah
[09:08]  * acheronuk blames Nvidia then
[10:24] <mparillo> valorie: I passed the two test cases in my VM last night and marked them here: http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/170821/testcases
[10:25] <mparillo> Live session: http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/170821/testcases/1303/results and entire disk: http://iso.qa.ubuntu.com/qatracker/milestones/389/builds/170821/testcases/1300/results
[10:27] <BluesKaj> Howdy folks
[10:28] <mparillo> Howdy BluesKaj. The first Bionic Final spin is out. There will be at least one more spin on Monday.
[10:29] <BluesKaj> 'Morning mparillo . ok thanks
[10:31] <acheronuk> mparillo: morning. done a fair bit of tweaking the release notes this morning. see what you think
[10:39] <mparillo> I know the wiki can be tempermental, but https://wiki.kubuntu.org/BionicBeaver/ReleaseNotes/Kubuntu renders badly, while https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/Kubuntu  looks fine
[10:42] <mparillo> It is just the wiki. I fired up Chrome (it seems to be better on allowing me to login), and the Kubuntu.org version is fine there. Going to fix the .. in the first paragraph.
[10:44] <acheronuk> mparillo: yeah, the kubuntu.org needs fixing or binning. please don't use that anywhere
[10:45] <mparillo> Shame. I much prefer the theming. Anyway, http://docs.kubuntu.org/docs/installation.html is not live for me.
[10:46] <mparillo> And obviously neither is http://cdimage.ubuntu.com/kubuntu/releases/bionic/release/
[10:47] <acheronuk> docs is weegie I think?
[10:47] <acheronuk> ahoneybun's territory
[10:51] <mparillo> I think the card https://phabricator.kde.org/T5135 is for internal docs. I do not see one for external docs.
[10:53] <mparillo> As far as FW5, do we have anything significant not yet ported?
[10:55] <acheronuk> mparillo: good point. all apps under 17.12.3 are KF5. ones that were not ported were dropped like kopete
[10:55] <acheronuk> kopete will come back KF5 for 18.04 apps
[10:56] <acheronuk> Sunday lunch soon, so I'll be off for a while
[10:56] <mparillo> So, want me to change Most applications have been ported to KDE Frameworks 5 but those which aren't should fit in seamlessly to All KDE apps on the ISO have been ported to KDE Frameworks 5, but those remaining in the archive should fit in seamlessly?
[10:58] <acheronuk> yep. that part is sort of a pointless repeat anyway
[12:23] <mparillo[m]> I am running the BB ISO on real HW. Tiny glitches using the Nouveau driver, but certainly no black screen.
[12:31] <mparillo[m]> Link to https://kubuntu.org/news/bionic-18-04-release-candidate-images-ready-for-testing/  posted to FB.
[13:40] <mparillo> I ran the BB ISO on a different laptop. Based on my sample size of two, I think the Intel drivers beat the Nouveau driver (but in both cases, I consider them passed, and certainly not problems with Kubuntu packaging).
[14:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2190: SUCCESS in 45 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2190/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2190: SUCCESS in 1 min 14 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2190/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2190: SUCCESS in 4 min 10 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2190/
 @acheronuk FYI there was a refression in ki18n 5.45 (therefore bionic is not affected) which may hang some plasma packages builds when generating the *.po files, I added the patch to kubuntu_bionic_staging branch
[21:10] <valorie> mparillo: thank you!
 @Santa, thanks :)
[21:34] <BionicMac> RC iso live-session and manual Install went perfect. Excellent work. Hats off to the devs. Thanks.
[21:35] <BionicMac> I'm diggin' the default desktop too. 
 BTW guys, here's what the 5.13 lock screen is going to look like. FIrst image is default appearance, and the second onw is how it looks after you move the mouse or hit a key on the keyboard … https://imgur.com/a/RdUcDjp
 isn't that just ridiculously beautiful!?
 also you'll be able to effectively use it as a screensaver now, if you opt to make the background something that's animated
 @DarinMiller free to test a sddm on that nvidia bug?
 Hi Rik! yes.  I can test.
 @nggraham, Yes, I do like the background. Well done.
 @acheronuk, Do you have a ppa or something else in mind?
 @DarinMiller, forget it :) already tried that fix. getting patches mixed up here
 np.
 This NVidia bug is quite a pain to track down.  After the fifth install, the NVidia driver installed without issue via Driver Manger.  However, on 1st reboot, the desktop failed to start throwing a opengl error, black screen and mouse pointer.   Its as if the NVidia driver failed to start.  Upon a 2nd reboot (no changes by me), the system booted fine.  I was hoping to compare the /var/log/apt/history.log files between
[23:05] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #1082: SUCCESS in 5 min 48 sec: https://kci.pangea.pub/job/mgmt_merger/1082/
[23:18] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #189: STILL FAILING in 11 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/189/
[23:21] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkgapi build #62: FAILURE in 14 min: https://kci.pangea.pub/job/bionic_unstable_libkgapi/62/
[23:31] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #100: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/bionic_stable_cantor/100/
[23:36] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_libkgapi build #109: STILL FAILING in 4 min 46 sec: https://kci.pangea.pub/job/xenial_stable_libkgapi/109/
[23:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_syndication build #123: FAILURE in 29 min: https://kci.pangea.pub/job/bionic_unstable_syndication/123/
[23:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkgapi build #120: STILL FAILING in 4 min 46 sec: https://kci.pangea.pub/job/xenial_unstable_libkgapi/120/
[23:36] -kubuntu-ci:#kubuntu-devel- Project artful_stable_libkgapi build #123: FAILURE in 4 min 47 sec: https://kci.pangea.pub/job/artful_stable_libkgapi/123/
[23:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libgravatar build #78: FAILURE in 29 min: https://kci.pangea.pub/job/bionic_unstable_libgravatar/78/
[23:37] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #129: STILL UNSTABLE in 29 min: https://kci.pangea.pub/job/bionic_unstable_ark/129/
[23:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkgapi build #141: FAILURE in 5 min 50 sec: https://kci.pangea.pub/job/artful_unstable_libkgapi/141/
[23:55] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kalzium build #82: STILL UNSTABLE in 47 min: https://kci.pangea.pub/job/bionic_stable_kalzium/82/
[23:55] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ark build #112: STILL UNSTABLE in 48 min: https://kci.pangea.pub/job/bionic_stable_ark/112/
[23:56] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_polkit-kde-agent-1 build #107: UNSTABLE in 49 min: https://kci.pangea.pub/job/bionic_stable_polkit-kde-agent-1/107/