I am surprised there isn’t an automatic mechanism to handle this especially if it is such a frequent issue.
I am surprised there isn’t an automatic mechanism to handle this especially if it is such a frequent issue.
btrfs dynamically allocates inodes.
Are you sure that’s the case with btrfs? I know ext has that feature. My understanding is btrfs just has a global reserve that can be used for any data in an low space situation.
# sudo btrfs fi usage /mnt/disk3
Overall:
Device size: 12.73TiB
Device allocated: 12.73TiB
Device unallocated: 1.00MiB
Device missing: 0.00B
Device slack: 0.00B
Used: 12.29TiB
Free (estimated): 449.43GiB (min: 449.43GiB)
Free (statfs, df): 449.43GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Multiple profiles: no
Data,single: Size:12.70TiB, Used:12.26TiB (96.55%)
/dev/sdd1 12.70TiB
Metadata,DUP: Size:15.00GiB, Used:14.49GiB (96.58%)
/dev/sdd1 30.00GiB
System,DUP: Size:8.00MiB, Used:1.34MiB (16.80%)
/dev/sdd1 16.00MiB
Unallocated:
/dev/sdd1 1.00MiB
I realize that’s not exactly what you asked for but Pipewire had been incredibly stable for me. Difference between the absolute nightmare of using BT devices with alsa and super smooth experience in pipewire is night and day.
Zero issues for me. Been daily driving it for years. Play Steam games regularly, but have not tried switching to X. Performance on Windows is MUCH better with my 1080ti playing D4, but I’m prefectly content with preformance on Linux and don’t want to keep switching.
This project dead?
Konsole is fantastic.
Just curious what issues you ran into? Asking as a suse daily driver for about 20 years now, but promise not to proselytize.
My problem with appimage is that they never work. Every time I tried one, best case scenario it crashed with a random error message. All attempts to fix them were damn near impossible to debug.
It honestly felt like they were not universal enough and still relied on certain libraries being available on OS. Hopefully I’m wrong because that would completely defeat their purpose. I stopped wasting time on them after Plex and VLC both failed to run reliably and switched to flatpak that “just works” 100% of the time.
To be honest most of the time I look for an rpm anyway. Flatpaks are always a last resort. I’m on OpenSuse Tumbleweed.
Could you name a couple? Genuinely interested to check out their contributions.
Also, I just updated to 4.34.119 and screen sharing is still completely broken. As is typical with Slack.
I’d argue lazy choice of wrapping your website inside chrome instead of building a native app is Slack’s issue.
I also wonder whether Slack fixed it or just waited for Google to fix it since Slack seems to only have UI designers and no actual devs on their team. They keep pumping out useless UI changes while actual bugs take years to fix.
I’m not sure that would work. Pipewire probably starts via system (just takes a while to become functional) and slack is started by KDE. I guess you could just add a delay to slack’s start, but I just start it by hand.
Don’t let Slack launch at startup. As long as it launches after pipewire - everything works. Your can also restart it to fix sharing issue, but that can be a birch if you already started a call.
I’m glad I’m not the only one that prefers Spectacle to Flameshot. Flameshot is way too bloated IMHO.
Awesome distro. Been my daily driver and home lab choice for over a decade. Keep up the great work!
https://xkcd.com/1172/