[04:46] <The_LoudSpeaker> Hey! We at #lubuntu-devel were considering making changes to grub commands during installation of lubuntu so that the nvram entry and the menu entry of grub read "Lubuntu" instead of current "ubuntu". We wanted to know your thoughts on it. TIA
[05:30] <flocculant> infinity: I'm not about much anymore - but still in Xubuntu Release team till the end of the week - just rebooted into new kernel and bug 1824677
[05:30] <ubot5`> bug 1824677 in xserver-xorg-video-nouveau (Ubuntu) "Display only has 640x480" [Undecided,New] https://launchpad.net/bugs/1824677
[09:53] -queuebot:#ubuntu-release- Unapproved: python-django-mptt (disco-proposed/universe) [0.8.5-0.1ubuntu1 => 0.8.7-1] (no packageset) (sync)
[12:05] <mparillo> I am sure it has been discussed, but I like the idea of having flavour-specific grub menu items, for those of us who dual-boot two different flavours.
[12:22] <infinity> tjaalton: Care to poke at LP: #1824677?
[12:22] <ubot5`> Launchpad bug 1824677 in xserver-xorg-video-nouveau (Ubuntu) "Display only has 640x480" [Undecided,Confirmed] https://launchpad.net/bugs/1824677
[12:23] <infinity> mparillo: How does update-grub decide which flavour you have installed when you have kubuntu-desktop, ubuntu-desktop, and lubuntu-desktop all installed?
[12:24] <infinity> mparillo: Which is probably about as common as people who install them in side-by-side partitions.
[12:24] <infinity> (Which is to say, not very common in either case)
[12:30] <tjaalton> infinity: nouveau modeset is now disabled by default, I'll tell him how to enable it..
[12:31] <mparillo> Fair enough. I always dual-booted rather than picking a desktop through SDDM, but as you say, neither is a common use case.
[12:31] <mparillo> I see in my current ISO testing lsb_release -a still says (development branch). I assume that gets removed just before the release is marked, correct?
[12:32] <infinity> mparillo: That will go away with Monday's builds.  But I want weekend testing so maybe we have some things to fix on Monday. :P
[12:33] <infinity> tjaalton: Being thrust back into 1992 suddenly is a bit jarring.  Is that how it's going to go for all nouveau users, or just some small subset of PCI IDs?
[12:34] <tjaalton> infinity: for everyone who haven't installed nvidia blob
[12:34] <infinity> :/
[12:34] <tjaalton> nouveau.modeset=1 re-enables it
[12:34] <infinity> That... Suboptimal.
[12:34] <infinity> s/That/That's/
[12:34] <infinity> What was the motivation for that?
[12:35] <tjaalton> bug 1821820
[12:35] <ubot5`> bug 1821820 in xorg-server (Ubuntu) "Cannot boot or install - have to use nomodeset" [Low,Fix committed] https://launchpad.net/bugs/1821820
[12:35] <mparillo> Thanks infinity. So I will mark my test case as passed for now, expecting a Monday re-spin.
[12:36] <infinity> tjaalton: But that was an Intel bug..
[12:36] <tjaalton> no
[12:36] <tjaalton> someone hijacked it
[12:36] <tjaalton> that bug is what I mentioned on the kernel channe..
[12:37] <tjaalton> l
[12:37] <tjaalton> https://patchwork.freedesktop.org/patch/296411/ needed for some intel
[12:37] <tjaalton> with buggy panels
[12:38] <tjaalton> I discussed the nouveau thing with upstream, and they said the firmware is buggy, and it frequently is
[12:39] <infinity> (someone hijacked what?)
[12:39] <infinity> 1821820 is very much all i915 all the time.
[12:40] <tjaalton> no it isn't, the original reporter has a hybrid machine and nouveau is messing it up
[12:40] <tjaalton> and reported that the new kernel works
[12:40] <infinity> lspci disagrees with you.
[12:41] <tjaalton> haha
[12:41] <tjaalton> ok, wrong bug
[12:41] <tjaalton> hang on
[12:42] <tjaalton> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822026
[12:42] <ubot5`> Ubuntu bug 1822026 in linux (Ubuntu Disco) "[Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code)" [Undecided,Fix released]
[12:42] <infinity> Anyhow, I'm not super happy with a solution that forces everyone down to 640x480.  I don't know what per centage of our install base is nvidia, and what per centage of those use the free driver, but I assume it's a non trivial number of people.
[12:45] <tjaalton> maybe would be better to disable only on "new enough" hw
[12:45] <tjaalton> which require buggy fw
[12:45] <infinity> More problematic, for my inner hippie, is that I feel this is just going to force people to install the non-free driver when they don't need to, since there's no obvious way in the GUI to re-enable modeset.
[12:46] <infinity> Plus, for old GPUs, the non-free driver is a mess.
[12:46] <infinity> I mean, it's not great for new ones either, but at least it's maintained. :P
[12:49] <infinity> I wonder if we could fudge a nouveau modeset "driver" in ubuntu-drivers that just installs a modprobe.d snippet and warns about the potential dangers.
[12:49] <infinity> So users have a choice in the driver panel between free (but maybe buggy) and non-free (but differently buggy).
[12:53] <tjaalton> perhaps
[12:53] <tjaalton> I'll think of how to make this a smaller gun
[12:53] <tjaalton> and limit it to "fresh" hw
[15:41] <flocculant> tjaalton: ta :)
[16:00] <tjaalton> flocculant: for what?
[16:06] <tjaalton> flocculant: oh, got it
[16:31] -queuebot:#ubuntu-release- Unapproved: latte-dock (disco-proposed/universe) [0.8.7-0ubuntu1 => 0.8.8-0ubuntu1] (kubuntu)
[17:27] -queuebot:#ubuntu-release- Unapproved: blis (disco-proposed/universe) [0.5.1-11 => 0.5.2-6] (no packageset) (sync)
[23:07] <xnox> Laney, infinity, do we need more noawait triggers somewhere? Look for "cycle found while processing triggers"
[23:07] <xnox> http://paste.ubuntu.com/p/GPTn3d2Dr4/