I'm running uBlue's AuroraOS. Have been very happy with it so far.
Yep the guide modifies fstab which works.
The KDE Device Auto-Mount works fine on regular Fedora, so it is probably just incompatible with Atomic/Immutable. I'll open a bug with KDE
It's a SATA connected NTFS HDD. It appears under the Attached Devices section.
I am trying to use the Device Auto-Mount feature in KDE Settings but it doesn't seem to be having any effect.
I have selected On Login and On Attach for the drives I'm interested in, but after rebooting they aren't auto-mounted.
If I click on them in Dolphin I am prompted for my user password and then they get mounted.
Anyone know what might be going on or where I should look?
- I couldn't see any obvious errors in journalctl
- drives are not encrypted.
- running AuroraOS
and yes I know that I can set this up with fstab, but it would be good to understand why the GUI approach isn't working and hopefully fix it.
reported bug to kde https://bugs.kde.org/show_bug.cgi?id=490872
Dioxus desktop and fullstack worked out of the box. Bevy isn't working because some Nvidia libraries aren't in the container. I might need to switch to a different 'GPU enabled' image.
How did you go with the VPN? I will be looking at that next. I'm using Proton VPN which has an rpm package, but if that doesn't work I can fallback to manually setting up the WireGuard config.
Are you accessing that through the browser? It might just be bridging the networking in that case.
The executable that I would be running is cargo (the rust build tool) but I want that inside of a container.
I could cargo build inside the container and then execute the output binary on the host but then I lose things like hot-reload.
So I'm looking at trying am Immutable Linux Desktop (uBlue Aurora probably). One thing I'm not clear on is how to run GUI apps during development. From what I understand I should create a container with distrobox, install my toolchains in it and start developing. I'm used to containers for CLI and server work, but I'm not sure how it applies to the GUI (Wayland / KDE).
If I do a cargo run inside distrobox for a Rust GUI project will it just work?
I saw that I can 'export' apps, but that is for already built executables whereas I will be building and rebuilding them.
This worked 👍 Thank you I also filed a bug report https://bugs.kde.org/show_bug.cgi?id=485403
The monitor does not display with kscreen-doctor -o as it's disconnected.
I will create a bug report.
So today I clicked 'enable HDR' on one of my monitors and something broke. The whole system froze up and the HDR monitor went black. If I reboot it freezes right after I login.
If I unplug that monitor or start in X11 instead of Wayland then everything is fine. Plugging the HDR monitor in while I'm logged into a Wayland session also freezes everything.
How can I disable the HDR setting?
The monitor doesn't show in System Settings whilst its unplugged so I'm hoping theirs some way to fix it on the CLI.
The only place I've found HDR referenced is .config/kwinoutputconfig.json. I set HDR to false but after reboot it's set to true again.
I also tried deleting .config/kwinrc and .local/share/kscreen but no luck.
I'm fine with just resetting all Display settings if that's required.
----- UPDATE ------
Bug report filed here: https://bugs.kde.org/show_bug.cgi?id=485403
Fixed by
- Ctrl + Alt + F3 to go into terminal
- Set
HighDynamicRangeandWideColorGamutto false in ~/.config/kwinoutputconfig.json - Execute
plasmashell --replace - Reboot, Login, Reattach HDR Monitor
------ UPDATE ------
After updating and trying again today the steps above no longer worked.
You still need to change ~/.config/kwinoutputconfig.json but plasmashell --replace no longer works for me.
Running killall kwin_wayland also just bumps me from my terminal back into the desktop. kwin can't be running when you change that file or it will be overridden.
I booted into a separate Linux Live USB and change the files that way.
---
Thank you everyone for your help 🎉