Note: I added more info in the OP

geteilt von: https://discuss.tchncs.de/post/52934409

geteilt von: https://discuss.tchncs.de/post/52933193 (OP)

A few days ago I noticed, that my system disc (~120gb) is almost maxed out. Since almost everything that takes up considerable disc space resides on my 2 discs, I started investigating, supported by ChatGPT. Turns out I've been running on a writable snapshot that keeps growing with each update. Again, important stuff is on my other discs, so reinstalling Linux allover would be a inconvenience, but no problem. Yet, I'd like to try repairing current installation, if only for the lessons learned.

I let ChatGPT summarize everything as a post so you don't have to deal with my half-educated gibberish:

du -xh --max-depth=1 / only shows ~16 GB used, but df -h reports ~113 GB used. Root, /var, /usr, /home, etc. are all on the same Btrfs filesystem. Snapper is enabled.

I confirmed that Btrfs snapshots are consuming the space, but I’m stuck with a writable snapshot (#835) that is currently mounted, so I can’t delete it from the running system.

To make things worse:

GRUB menu does not appear (Shift/Esc does nothing)

The system still boots into Linux, but I can’t select older snapshots

I tried repairing from an Ubuntu live USB, but:

NVMe device names differ from the installed system

Chroot fails with /bin/bash or /usr/bin/env not found

Likely because /usr is a separate Btrfs subvolume and not mounted

At this point I’m trying to:

Properly mount all Btrfs subvolumes from a live system

Chroot into the installed system

Delete old Snapper snapshots

Reinstall GRUB so the menu works again

If anyone has step-by-step guidance for recovering openSUSE Tumbleweed with Btrfs snapshots and broken GRUB access, I’d really appreciate it. I’m comfortable with the command line but want to avoid making things worse.

Hope someone can make something of it and help me fix my system.

Note: I added more info in the OP

geteilt von: https://discuss.tchncs.de/post/52933193 (OP)

A few days ago I noticed, that my system disc (~120gb) is almost maxed out. Since almost everything that takes up considerable disc space resides on my 2 discs, I started investigating, supported by ChatGPT. Turns out I've been running on a writable snapshot that keeps growing with each update. Again, important stuff is on my other discs, so reinstalling Linux allover would be a inconvenience, but no problem. Yet, I'd like to try repairing current installation, if only for the lessons learned.

I let ChatGPT summarize everything as a post so you don't have to deal with my half-educated gibberish:

du -xh --max-depth=1 / only shows ~16 GB used, but df -h reports ~113 GB used. Root, /var, /usr, /home, etc. are all on the same Btrfs filesystem. Snapper is enabled.

I confirmed that Btrfs snapshots are consuming the space, but I’m stuck with a writable snapshot (#835) that is currently mounted, so I can’t delete it from the running system.

To make things worse:

GRUB menu does not appear (Shift/Esc does nothing)

The system still boots into Linux, but I can’t select older snapshots

I tried repairing from an Ubuntu live USB, but:

NVMe device names differ from the installed system

Chroot fails with /bin/bash or /usr/bin/env not found

Likely because /usr is a separate Btrfs subvolume and not mounted

At this point I’m trying to:

Properly mount all Btrfs subvolumes from a live system

Chroot into the installed system

Delete old Snapper snapshots

Reinstall GRUB so the menu works again

If anyone has step-by-step guidance for recovering openSUSE Tumbleweed with Btrfs snapshots and broken GRUB access, I’d really appreciate it. I’m comfortable with the command line but want to avoid making things worse.

Hope someone can make something of it and help me fix my system.

Update: I managed to get GRUB running, booted into another snapshot, made that one the default and deleted almost all other snapshots. This freed up some space, but my disc is still stuffed and I need to find out how to go on from here. If you have any suggestions, feel free :)

Original Post: A few days ago I noticed, that my system disc (~120gb) is almost maxed out. Since almost everything that takes up considerable disc space resides on my 2 discs, I started investigating, supported by ChatGPT. Turns out I've been running on a writable snapshot that keeps growing with each update. Again, important stuff is on my other discs, so reinstalling Linux allover would be a inconvenience, but no problem. Yet, I'd like to try repairing current installation, if only for the lessons learned.

I let ChatGPT summarize everything as a post so you don't have to deal with my half-educated gibberish:

du -xh --max-depth=1 / only shows ~16 GB used, but df -h reports ~113 GB used. Root, /var, /usr, /home, etc. are all on the same Btrfs filesystem. Snapper is enabled.

I confirmed that Btrfs snapshots are consuming the space, but I’m stuck with a writable snapshot (#835) that is currently mounted, so I can’t delete it from the running system.

To make things worse:

GRUB menu does not appear (Shift/Esc does nothing)

The system still boots into Linux, but I can’t select older snapshots

I tried repairing from an Ubuntu live USB, but:

NVMe device names differ from the installed system

Chroot fails with /bin/bash or /usr/bin/env not found

Likely because /usr is a separate Btrfs subvolume and not mounted

At this point I’m trying to:

Properly mount all Btrfs subvolumes from a live system

Chroot into the installed system

Delete old Snapper snapshots

Reinstall GRUB so the menu works again

If anyone has step-by-step guidance for recovering openSUSE Tumbleweed with Btrfs snapshots and broken GRUB access, I’d really appreciate it. I’m comfortable with the command line but want to avoid making things worse.

Hope someone can make something of it and help me fix my system.

/edit: Forgot my snapper list output

#0 single — current

#835 * single — mounted 2024-03-18 16:58 CET, 200.82 MiB desc: writable copy of #828

#1802 pre — 2026-01-08 11:50 CET, 864 KiB cleanup: number, desc: System update

#1803 pre — important 2026-01-08 11:51 CET, 848 KiB cleanup: number, desc: zypp (zypper)

#1804 post → #1803 — important 2026-01-08 11:58 CET, 13.54 MiB

#1805 post → #1802 2026-01-09 12:08 CET, 3.23 MiB desc: System update

#1806 pre — important 2026-01-09 12:08 CET, 2.50 MiB cleanup: number, desc: zypp (zypper)

#1807 post → #1806 — important 2026-01-09 12:08 CET, 960 KiB

cross-posted from: https://discuss.tchncs.de/post/49067647

I recently bought Diablo 1 via GoG and wanted to install it on my Dell Latitude for couch sessions. I installed it via Heroic and everything seemed fine, but after the Blizzard splash, the game stays black. Sometimes, when I tab out, some menu texts appear in the tab switcher thumbnail, but thats about it. I fumbled around with the graphics settings in the pre-game settings window (which is really tiny) and tries window mode, different resolutions etc. but nothing changed.

It feels a bit like a "not good enough graphics card" but... well, its Diablo 1...

Is there something I can do, or try, to make D1 playable?

I recently bought Diablo 1 via GoG and wanted to install it on my Dell Latitude for couch sessions. I installed it via Heroic and everything seemed fine, but after the Blizzard splash, the game stays black. Sometimes, when I tab out, some menu texts appear in the tab switcher thumbnail, but thats about it. I fumbled around with the graphics settings in the pre-game settings window (which is really tiny) and tries window mode, different resolutions etc. but nothing changed.

It feels a bit like a "not good enough graphics card" but... well, its Diablo 1...

Is there something I can do, or try, to make D1 playable?

edit: DevilutionX did it amd it was a breeze. Ty all.

I recently got my hands on a Dell Latitude E7470 and installed Fedora Workstation. Even though I enabled two finger scroll (and disabled touchpad edge scroll), the right side of the touchpad still has a dead zone of considerable size. So, when I start a mouse movement too far on the right side, it wont register.

I tried a few things, like adding quirk configs, but the zone is still there. Bios had no option to disable. (I reinstalled with UEFI, prior installation was legacy uefi / bios, so I have to give it a look again).

Does someone have a way to disable the dead zone?

Also, the fingerprint sensor doesn't work. From what I could research, it is a broadcom device with officials drivers for MS and Ubuntu. I tried some stuff to get this thing running, but it didn't work out. I still have to try a bios update after the reinstall. Is there a way to get this thing running under Fedora? It's not a crucial feature, but a nice to have for sure.

What is it with Android, that it constantly wants me to use Live Wallpapers?

I switched to a plain android device from Xiaomi and I really like the calm experience. No ads, no duplicate services etc. But one thing still bothers me: Live Wallpapers.

Why is Android so keen on activating live wallpapers? I didn't want them on my old device and always thought it was a Xiaomi thing. But now I still get a screen every once in a while and after each system update. Why? What's in it for Android that it is so obsessed with fucking live wallpapers that I constantly have to reaffirm that I really REALLY don't want them?

edit: Solved.

The title is a bit theatrical. My google account tells me my storage is full and urges me to buy more storage. The problem is, that on my new phone G Photos just started to put all my photos into the cloud.

How can I remove my photos from the cloud without losing them locally on my phone? I tried logging out of Photos, but then I cannot access my photos. I just requested an archive download via takeout.google.com so I hopefully have a backup, but I still need to get rid of all the photos in the cloud to free up the storage.

I recently started a home server and want to move to selfhosted services, but that will take it's time, so for now, I am forced to continue google services.

Can you help me?

I'm in the means of buying a mini pc for selfhosting stuff. My main reasons are sailing the high seas for movies and series and hosting my families photos, videos to escape gdrive. I'm thinking about some kind of DMS / digitalizing paperwork and mail in the future.

I casually look into all kinds of software that could do the task and now I'm a bit overwhelmed. Is owncloud or an alternative enough, or do I need something more elaborated like TrueNAS? But all the NAS Foss stuff seems to run on their own OS. Can my Pirate Ship run on that? I feel like the diversity of solutions is making this very opaque for me.

Hi,

My Kindle won't boot anymore and keeps getting stuck in boot screen, so I thought this might be a good time to get away from Amazon, even though that device was great.

So, what non-kindle readers would you recommend?

It should have color and background light and it shouldn't be huge so I can keep it in the back pocket.

And, since I don't have any experience outside the Amazon ecosystem: how is the experience of buying and transferring books to non Kindle readers?

Update: I did research based on your recommendations. Thanks for all the input, that was way more than I expected! I settled for the Kobo Clara Color since it seemed to almost perfectly match my needs and Kobo and the model itself got heavily recommended here and on the web.

cross-posted from: https://discuss.tchncs.de/post/27742447

Hi folks,

I got a new Xbox Series X Controller (Model 1914). I had Xbox One controller before.

With xpadneo installed I had basically no problems running my xbox one controller. It connected via BT with no issues and workes in games really well wired and wireless.

The new controller on the other hand, works really well via cable, but does not connect via BT. I can find it, I can pair it, but I cannot connect to it.

xpadneo readme says Series X needs a BT stick with BLE so I bought one, but that did not solve the problem (I'm not sure if BLE needs to be activated or how to do it rn).

Hi folks,

I got a new Xbox Series X Controller (Model 1914). I had Xbox One controller before.

With xpadneo installed I had basically no problems running my xbox one controller. It connected via BT with no issues and workes in games really well wired and wireless.

The new controller on the other hand, works really well via cable, but does not connect via BT. I can find it, I can pair it, but I cannot connect to it.

xpadneo readme says Series X needs a BT stick with BLE so I bought one, but that did not solve the problem (I'm not sure if BLE needs to be activated or how to do it rn).