In my experience, the developers of such applications discover their mistake pretty quickly after their apps start seeing wide use, when their users complain about /tmp filling up and causing failures. The devs then fix their code. That’s why we don’t see it often in practice.
I humbly disagree. We don't live in that utopia.
I don't see them echoing your concerns.
I guess for an scenario to be real everyone has to know exactly what's happening? They will know what caused it and they will all know how to properly report it even though I don't even expect a lot of people to know their system especially your average joe/dane nor do I expect them to even troubleshoot the issue if something were to happen. It doesn't really invalidate the scenario at all.
A fabricated scenario is itself pretty redundant. :)
I... don't think I have ever seen it do that automatically unless I missed some steps in the installation guide...? most of the time I just created the partitions I needed. I did a quick CTRL + F on tmpfs or tmp but not seeing anything...
Anyhow, I don't see on my desktop which still has Arch Linux installed which I want to move to KDE Neon but extremely lazy when you have an immense backup to do...
Why would it matter the reason of dropping a file of X size? The point is that not all applications are "decent" and some will undoubtedly use /tmp because "it might be the most logical thing" for any developer that's not really up to date.
I don't see how reviewing the tmpfs helps in this scenario if at all... we are talking about end-users your common joe/dane running your day to day applications, whatever they may be. I don't and will never expect developers to adhere to anything and just put out whatever.
Hi, I'm the same person ended up just creating an account seems like my reply never got in from mastodon but:
A restart fixed it. What changed was my session configuration went from the default to "empty session" after that it started working as normal.
KDE Neon using tmpfs for /tmp seems like an horrible idea?
I get the idea behind it for sure but why use our available ram for this? I thought whatever init functionality would just wipe clean /tmp at boot.
Right now what I'm looking at is that if a system has 16gbram KDE Neon uses half of it for /tmp.
The thing is applications could output to /tmp for a plethora of reasons that could maximize that. Whether you are a content creator or processing data of some sort leaving trails in /tmp the least I want is my ram being used for this thing regardless.
Basically if you drop-in a 10GB file in /tmp right now (if your setup has tmpfs active) you will see a 10GB usage in your htop. Example in https://imgur.com/a/S9JIz9p
I'm not here to pick a fight but as a new KDE Neon user I'm scratching my head on the why after years in Arch Linux.
There's plenty in there going back to 6 months+ sadly I don't think I can bring as much details as everyone's elses posted issues. It's a waiting game from here on :(
In my case I was using X11 when I posted this. I get flickering on both X11 and wayland and that's a bit ugh sometimes 🙃🙃
How do I fix the flickering on KDE with transparent themes? (AMDGPU laptop)
*-display description: VGA compatible controller product: Lucienne vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@0000:03:00.0 logical name: /dev/fb0 version: c2 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list fb configuration: depth=32 driver=amdgpu latency=0 resolution=1920,1080
I'm using archlinux with plasma 5 & wayland. From time to time it just starts flickering for some reason...
If I need to change drivers just let me know. I don't game or do anything graphical on this laptop. Only software development on vscode and chatting.