It sounds like the issue is with the lid latch/sensor, not with the graphics. Some laptops may not boot if the lid is closed, and some have options on the firmware to enable to boot when the lid is closed / on a docking station.
This seems unlikely since it boots with a monitor attached. From past experience most laptops that refuse to boot while closed don’t boot even if an HDMI display is connected.
So I am sort of an embedded developer, and I like to mess around with weird configurations. So the craziest experiment I did was trying to reflash a rasberry pi from a system running in the pi’s RAM. It honestly might have worked, but during the prep work I forgot to resize the filesystem before mucking with the paritions and had to reflash the normal way before I could try again. Ended up just turning it into a pihole instead, but I still learned a lot about pivot_root
Back when I used ubuntu, Unity was stuck with old gnome packages. This meant that the version gnome-terminal packaged with ubuntu (up to at least 18.04) didn’t have text reflow on window size changes.
You could add the upstream sources, upgrade the specific text reflow package only, and then disable the sources.
I forgot to disable the sources, or typed dist-upgrade (this happened multiple times…). Broke the whole desktop/lightdm setup with half upgraded packages, and half removed packages (for preparation to install new versions). Way easier to reinstall the os than to disentangle. Unity was a mess then anyway.
Moral: Actually read the package change summaries when doing updates/removes/installs, and [ y/N ] means actually check what the fuck you think you’re agreeing to.
BtrFS snapshots for idiots
I’ve also run automated snapshots on my btrfs partition, then run out of space doing multi-hop system upgrade on fedora (dnf has a plugin that creates a snapshot every time it kicks in.
You can imagine there were many changes happenning per snapshot, and I effectively could have rolled back 4 major fedora versions… Til I ran out of space.
I couldn’t get a replacement drive in time, and I had an hour to rebuild my laptop before needing to be on a customer site, so sadly I couldn’t preserve my drive for later investigation. My best guess is the high-water-mark was configured incorrectly, and somehow it was able to ‘write’ data past the extents of the filesystem.
Rollback did work for my home partition, but I had to mount it from another OS to get it to work - so no data loss!
By that time I’d already reinstalled the os to the root partition/subvolume however, so I couldn’t determine the exact cause of failure :(
Moral: Snapshots are not backups, and ‘working’ is not ‘tested’
I was trying to extract some files from a a Linux image of one of those ARM boards. It was packed into the cpio format, and I had never used the format before. Of course I was trying to extract to a root owned directory and I sudo’ed it. I effed up the command and overwrote all my system directories (/bin, /usr, /lib, etc…). Thankfully I had backed up my system recently and was able to get it working again.
At one point I had the coolest Ventoy USB; CyberRe, LABEL=hakr. But then I got a new computer and apparently the ssd was /dev/nvme0n1 instead of /dev/sda. While I was installing Arch, When I created a new GPT partition on /dev/sda, it wiped my beautiful Ventoy 😢
It’s called Compositor Hand-offs, it’s coming in the future and is Wayland only.
It’s likely going to be in Plasma 6 release.
Restoring application state isn’t the only thing it does either. It also allow for graceful crash recovery, true-full-poweroff hibernation and hot-swapping supported compositors.
I wouldn’t recommend specific ones, but I would recomnend you try out distros with unique features. Such as an immutable one, one that is built from source, one with packages, one with snap, one with flatpack, etc.
This will help you understand and evaluate what you like.
Does it still get the error without the wifi adapter connected? The stack trace shows some network-related stuff (which doesn't necessarily mean that's where the issue arose, but it would be a little coincidence based on what you said).
That's the first thing I'd try, and if removing the adapter fixes it (long term) I wouldn't use the adapter anymore. Sometimes broken hardware breaks other hardware it's connected to.
If removing the adapter doesn't fix it, then the next thing I'd try is booting back into the known-good old old OS, maybe removing the NVidia card, basically simplify everything one step at a time until it stops happening, if you can.
Next chance I get I’m booting without the USB wifi adapter. I’m worried I may have broken something because it was mostly stable before :/ lol I actually don’t have the Nvidia card yet, I ordered a cheap Tesla K80 that’s arriving on Tuesday 😹 and it already brokey system :P
That’s a good idea, I have an Ubuntu partition that I should try.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.