• We had to restore from a backup today after a failed software update. Backup was from 0000 EDT and restored it at 0800 EDT so we lost about 8hrs. Today is 07/20/2024. More info here.

Screen suddenly goes black on ubuntu 23.04 (not at login)

Great tipp! Thank you very much. I appreciate it.

No problem. I've been using the same /home for (literally) years. I can move from one device to another device and have a fairly consistent experience - even if they're different OSes, though it's more cohesive if they're in the same family for things like aliases. I even have different alias files for when I do want to use a different OS family.

Even when I do a new install (something I do rarely), I just copy my /home over the /home that was installed and keep on truckin'.

Does disabling apparmor systemwide have security implications? Is there a application based alternative?
Disabling apparmor for "debugging" as in this case is not an unusual step. The apparmor website mentions:
Debugging application problems

When debugging issues, the first step should always be to disable the AppArmor profile

The arch wiki (since you're running arch) mentions:
AppArmor, like most other LSMs, supplements rather than replaces the default Discretionary Access Control (DAC). As such it is impossible to grant a process more privileges than it had in the first place.
LSM = linux security module.

Apparmor is basically a categorisation or labelling system for the files in an installation with a set of rules about which files can access other files. It protects against bad software that wants to access stuff it doesn't need or shouldn't. It's a security system that sits on top of the already robust secure system of permissions that is inherent in the standard linux filesystem (the DAC). For debugging, turning apparmor off for an application or the system is pretty common. Apparmor is not a firewall.

In debugging, it's not a bad idea to try one thing at a time so see if it affects anything, then after the trial, return the system to it's original state and try the next thing.

The other thing that comes to mind about the problem is to ensure that the nvidia installation is correct in all respects. It's possible to clear the graphics system of the nvidia software, and run the open source nouveau driver (which nvidia blacklists). If the system runs properly with the nouveau driver, then that would suggest that the installation of the nvidia drivers is implicated in the problem.
Last edited: