[02:00] <guiverc> I just finished with a test (jammy) & used SysRq+reisuo (without thinking) to turn off; it did??  I thought that was disabled
[04:04] <shqipshqiphooray> hi, anyone else have a problem not getting to the installer at all, just loading ?
[04:06] <lotuspsychje> shqipshqiphooray: do you have secureboot enabled?
[04:07] <shqipshqiphooray> yes
[04:07] <shqipshqiphooray> but isn't that supported by ubuntu by default?
[04:08] <lotuspsychje> shqipshqiphooray: i didnt say you cant use it, but as a test try your installer with secureboot off
[04:08] <shqipshqiphooray> ok
[04:08] <shqipshqiphooray> puši kurac pičko jedna
[04:08] <lotuspsychje> i saw incoming updates yesterday regarding grub/uefi
[04:08] <lotuspsychje> right
[16:03] <lotuspsychje> alkisg: just fresh from the rss press; https://ubuntuhandbook.org/index.php/2022/04/ubuntu-22-04-remote-desktop-control/
[16:03] <alkisg> Thank you lotuspsychje ; will check in a bit; I'm too deep in the GNU make manual now to raise my head :D
[16:04] <lotuspsychje> : )
[16:50] <alkisg> That's great progress! Unfortunately it doesn't help with screen sharing and remote support, as (1) No reverse connections means that NAT will be needed, and (2) Noone will want to give me their passwords so that I can support them :D
[16:51] <alkisg> While x11vnc -connect alkisg.ltsp.org requires no NAT and no password sharing...
[16:51] <alkisg> (and no running daemon)
[16:51] <alkisg> Maybe in 5-10 years wayland will be ready though :D
[16:52] <lotuspsychje> lol
[16:52] <lotuspsychje> (if you can login into it) j/k :p
[16:52] <alkisg> Haha, true dat
[20:45] <howarth> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243 was updated
[20:45] <howarth> "Yes, this bug disabled Wayland for everyone. So we don't need more reports confirming that it affects your Intel or AMD system. The bugfix is waiting for someone from the Ubuntu Release Team to accept it but it's a holiday weekend so it may take until tomorrow."
[20:46] <howarth> Makes you wonder what they think the proposed repo is for if it managed to get into updates while breaking Wayland for all machines.
[20:49] <howarth> It sounds like that they will just add the missing check for Nvidia and leave Nvidia with Wayland disabled for the initial 22.04 LTS release with its restoration at some future update of the Nvidia drivers post-release.
[20:51] <howarth> Beyond the missing check for Nvidia, it still seems that their check for NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS is not really functional.
[23:11] <howarth> Looks official
[23:11] <howarth> gdm3 42.0-1ubuntu6 disables Wayland on Nvidia
[23:12] <howarth> So 22.04 LTS is going to ship with Wayland unavailable on Nvidia
[23:23] <howarth> Interestingly, Fedora 36 won't have this problem with Nvidia/Wayland because their rpmfusion nvidia packaging provides the necessary resume support
[23:23] <howarth> https://github.com/rpmfusion/xorg-x11-drv-nvidia/blob/master/nvidia-power-management.conf
[23:24] <howarth> # Save and restore all video memory allocations.
[23:24] <howarth> options nvidia NVreg_PreserveVideoMemoryAllocations=1
[23:24] <howarth> # The destination should not be using tmpfs, so we prefer
[23:24] <howarth> # /var/tmp instead of /tmp
[23:24] <howarth> options nvidia NVreg_TemporaryFilePath=/var/tmp