submitted 2 years ago* (last edited 2 years ago) by to c/kde@lemmy.ml
 

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

[–] [S] 1 point 2 years ago

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.

  • source
  • [–] [S] 7 points 2 years ago

    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.

  • source
  • parent
  • context
  •  

    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.