Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)RA
rainier @lemmy.world
Posts 2
Comments 10
Anyone else starting to favor Flatpak over native packages?
  • I had a reasonably good time getting NVIDIA drivers installed. I found the instructions here. I installed the newest drivers using the following command + a reboot. transactional-update -i pkg in nvidia-driver-G06-kmp-default nvidia-video-G06 nvidia-gl-G06 nvidia-compute-G06 nvidia-utils-G06 nvidia-compute-utils-G06 The OpenSUSE guide doesn't include compute-utils, which is needed if you want to run nvidia-smi. I haven't tried installing a full CUDA SDK, so ymmv there.

  • Integrating VSCode and Distrobox

    Following up on a recent post on Distrobox...

    For those using VSCode with Distrobox, how do you all do it? distrobox wiki suggests two approaches: flatpak + dev containers and running vscode from within distrobox.

    Which do you prefer and why?

    I've experimented with both and got both running with Wayland. Using the latter approach (vscode within distrobox), I couldn't quite get the running instances to be recognized by GNOME shell as the same vscode app that launched it. It shows up as code-url-handler, and doesn't share the same icon on the dash. The flatpak approach doesn't seem to have this issue.

    7
    Today I discovered Distrobox and it saved my day by letting me install an old-ass, unmaintained app that's only packaged for old Debian
  • Yes, VSCode is an electron app, and I use flags to launch it with Wayland. I export VSCode to the host system with the flags attached, so that VSCode automatically launches in Wayland. The command I used: distrobox-export --app code --extra-flags "--enable-features=WaylandWindowDecorations --ozone-platform-hint=auto"