[14:55] waveform: hi, wondering if have some tips. At some point in time, I lost my hdmi console on my raspberry pi4. I just noticed it today, when ssh broke and I had the need for a console [14:55] anything I could debug/troubleshoot? [14:56] kernel cmdline is [14:56] coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:6B:96:DB vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc [14:56] it was running mantic, now is running nobel (it was during that do-release-upgrade that ssh broke). I'm back in via ssh, but now I'm interested in knowing how to bring the console back, should something like this happen again [15:01] hmm, maybe it's https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370 [15:01] -ubottu:#ubuntu-devel- Launchpad bug 2064370 in linux-raspi (Ubuntu) "Blank screen after boot in raspberry pi 4" [Undecided, Confirmed] [16:03] I don't seem to have hdmi enabled at all, odd [16:27] ok, got it sorted somehow [18:38] amurray: please see bug 2064672. I think we're best uploading a straight revert of apparmor back to the source tree of what was in the release pocket. Any chance you're around and could prepare that please, so that we have two sets of eyes on it? And/or, any reason that would be a bad idea? [18:38] -ubottu:#ubuntu-devel- Bug 2064672 in apparmor (Ubuntu) "[SRU] - fixes for apparmor on noble" [Undecided, In Progress] https://launchpad.net/bugs/2064672 [18:38] Regression bug V [18:38] 2072811 [18:38] bug 2072811 [18:38] -ubottu:#ubuntu-devel- Bug 2072811 in apparmor (Ubuntu) "Apparmor: New update broke flatpak with `apparmor='DENIED'`" [Undecided, Confirmed] https://launchpad.net/bugs/2072811 === tuxifreund_ is now known as tuxifreund