[00:22] <en11gma> i have been coming and warning this channel for 2 weeks with a severe bug.
[00:22] <en11gma> X570 motherboard, 5600x cpu and 3060 ti gpu.
[00:23] <en11gma> when booting from any ubuntu 22.04 daily image after 03-28-22 with amd64 i get a WHITE SCREEN AT DESKTOP!!!
[00:23] <en11gma> i have been telling everyone of you in here.
[00:23] <en11gma> when i switch my 3060 ti out for a 1060 it does not do this.
[00:23] <en11gma> the 03-28-22 image does not do this and has normal behavior
[00:24] <hggdh> en11gma: did you open a bug on it?
[00:24] <en11gma> the final 22.04 release is 4 days away... well less then that as in 4:36mins it will be midnight here
[00:24] <en11gma> i came here and been telling all you

[00:24] <en11gma> this is a severe bug and no one has opened up a bug report on it?
[00:25] <en11gma> im just saying its pretty big
[00:25] <en11gma> this is when booting from live usb
[00:25] <hggdh> en11gma: The best route is to open a bug
[00:25] <en11gma> 'in case someone wants to pass it on'
[00:25] <en11gma> or come to the channel for this release and tell them which i have been doing over and over and over and over for last 2 weeks
[00:26] <en11gma> does this channel even talk to the devs?
[00:26] <hggdh> not necessarily, no. Some devs may be present, but I would not rely on it.
[00:27] <en11gma> well hopefully someone passes it on. i try every daily release avail and its the same thing. only thing that fixes it is when i go back and write 03-28-22 image.
[00:27] <en11gma> then it works as it should from live usb
[00:27] <en11gma> im betting this bug affects all 30xx series cards
[00:28] <en11gma> REQ: anyone with a 30xx series card write the ubuntu daily 22.04 amd64 image to usb and boot into live enviroment
[00:29] <en11gma> i get white screen. when i remove my 3060 ti and put in a 1060 3GB it works fine
[00:29] <en11gma> ok im out. 4 days to go until launch. have a good one!
[00:29] <en11gma> bye
[00:30] <ravage> you have to love a good ultimatum
[00:31] <ravage> fix my problem that im too lazy to report or i will.... not install your free product. take that!
[00:50] <mybalzitch> rip us.
[07:55] <Pinchiukas_> I just found that grub-pc is not available for i386 in jammy. Why is that?
[07:55] <Pinchiukas_> Does even have efi-related packages but not the bios one: https://packages.ubuntu.com/search?suite=jammy&arch=i386&searchon=names&keywords=grub
[07:59] <guiverc> The last i386 ISOs were produced in the disco/19.04 cycle; why would it be needed?
[07:59] <Pinchiukas_> For me! :) Deboostrapping jammy on ancient hw.
[08:00] <guiverc> I've installed jammy on boxes as old as from 2005 without issue; all being amd64 CPUs though
[08:01] <lotuspsychje> try a nice light lubuntu Pinchiukas_ 
[08:01] <guiverc> i386 was turned off pre-release of eoan (19.10)... the only i386 with support now is 18.04 LTS
[08:05] <Pinchiukas_> This box is supposedly 2008. But it has a i386 cpu.
[08:06] <Pinchiukas_> Dang... I'm really not a fan of the idea to install 18.04.
[08:06] <guiverc> intel atoms were i386 produced into 2007 I'm aware of (some sold into 2008)
[08:07] <guiverc> intel atom n270 being i386; later atoms were amd64
[08:07] <Pinchiukas_> This is a thin client with a VIA cpu.
[08:07] <Pinchiukas_> HP T5530
[08:08] <guiverc> You may need Debian given i386 support in Ubuntu now is mostly 2nd architecture (for steam or other packages on amd64 cpu)
[08:09] <guiverc> Pinchiukas_, I tested Debian 11 on pentium 4, pentium M boxes, even n270 intel atom I mentioned in i386
[08:11] <Pinchiukas_> That might be the way to go, then. But how long will 11 be supported? Seems their support cycles are shorter.
[08:11] <guiverc> Debian LTS is 5 years which is ~same as Ubuntu LTS is.... Debian LTS isn't all packages, just like Ubuntu isn't either (ie. 'main' is 5 years...)....
[08:12] <lotuspsychje> or stick to 18.04 Pinchiukas_ and consider !ESM if its really important?
[08:12] <guiverc> but Debian is off-topic here; this is Ubuntu support so ask on a Debian room if interested
[08:19] <lotuspsychje> Pinchiukas_: https://ubuntu.com/security/esm
[09:16] <howarth> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243
[09:17] <howarth> "* Please note that Wayland is not currently available for
[09:17] <howarth>     systems using the Nvidia graphics drivers because those drivers
[09:17] <howarth>     don't properly handle suspend and resuming from suspend. It is
[09:17] <howarth>     intended for those drivers to be fixed in a future stable release
[09:17] <howarth>     update for Ubuntu 22.04 LTS. See bug 1968929"
[09:17] <howarth> What is Ubuntu's definition of a 'stable release update' in this case regarding Nvidia driver support for Wayland? Does this imply, as I fear, an update only after the fix has been deployed in another full Ubuntu release? If so, this would imply that we won't have Nvidia Wayland support until 22.10 is released.
[09:17] <ravage> 22.04.1 for example
[09:17] <ravage> its says stable release update for 22.04
[09:17] <howarth> which would be only after a 22.10 release
[09:18] <howarth> So no Wayland on Nvidia until Oct 2022
[09:18] <ravage> https://discourse.ubuntu.com/t/jammy-jellyfish-release-schedule/23906
[09:19] <howarth> Again, .01 LTS releases only occur after the next stable release 
[09:31] <howarth> So basically, this is going to be treated like transitions to a new major kernel release and only occur after testing in 22.10? Also, actually I misspoke. The restoration of Wayland support for Nvidia wouldn't be 10/2022. It would be more likely 02/2023.
[09:33] <ravage> i have no idea what you are talking about. schedule shows 22.04.1 in august this year. and if there is a solution that does not require any major changes im sure it will be done before
[09:34] <ravage> it makes no sense to release wayland to nvidia users if it doesnt work. and wayland is default for everyone else. so you would give a broken default to a lot of desktop users
[09:35] <ravage> and if you want to have a broken system delete the gdm udev rules
[09:37] <ravage> as usually gone until his next useless rant :)
[10:47] <lotuspsychje> i also had gdm updates this morning, perhaps fixed?
[10:51] <ravage> im on nvidia. so no idea :)
[10:52] <lotuspsychje> i never went looking
[15:04] <Sven_vB> hi :)
[15:06] <Sven_vB> Pinchiukas_, I'm a maintainer of the SuperGRUB Disk. If you like, please let's cooperate in our endeavor of preserving GRUB availability for i386 via Ubuntu. 
[15:10] <Sven_vB> Pinchiukas_, for a start, I recommend using a GRUB config that is not managed by Ubuntu, but instead auto-detects available kernels.
[15:11] <Sven_vB> I should probably package and release the one I use.
[17:29] <The_LoudSpeaker_> Hey!
[17:30] <The_LoudSpeaker_> I am on 22.04 daily since some time and I noticed that the wayland option from login screen has disappeared.
[17:30] <The_LoudSpeaker_> I am always getting logged into x11 session. I am sure it has happened after some updates. I was on wayland before and gestures were working in gnome. 
[17:31] <The_LoudSpeaker_> Is there something I am missing here?
[17:32] <lotuspsychje> there's an existing bug on that The_LoudSpeaker_ 
[17:32] <lotuspsychje> bug #1969243
[17:39] <The_LoudSpeaker_> Nice.
[17:40] <The_LoudSpeaker_> Thanks lotuspsychje 
[17:41] <lotuspsychje> np The_LoudSpeaker_ 
[21:54] <Aarch64debian> !release
[21:55] <Aarch64debian> !jammy
[21:55] <Aarch64debian> !when