• 58 Posts
  • 1.26K Comments
Joined 3 years ago
cake
Cake day: March 21st, 2022

help-circle
















  • Pantherina@feddit.detoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    7 months ago

    Funny. True, on superstable but also super unstable systems, having separated apps makes most sense.

    Not actually on “immutable” rpm-ostree systems, as these have the best and most solid package management.

    So actually when people say “these immutable systems, you just use Flatpaks”, actually on the regular systems you should mainly use Flatpaks.


  • Pantherina@feddit.detoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    7 months ago

    Crazyy!

    Btw I am XWayland free since today!

    I have a list of recommended apps here

    Some apps need environment variables:

    Qt:

    • qpwgraph

    GTK

    • GPU Screen recorder, I guess

    Electron

    • Nextcloud Flatpak
    • MullvadVPN RPM
    • Signal Flatpak
    • (Element, I switched to the Webapp in Librewolf)
    • Freetube Flatpak

    You can use xlsclients -l to detect apps using XWayland.

    Some may even want to run apps through XWayland on purpose, like KeepassXC for Clipboard access or autotype. Lets see how long it takes to implement all the needed protocols.


  • You got me in the first part XD

    No joking, apart from that

    But since apparently PulseAudio is the GNome / Microsoft approved way

    I think I understand your point.

    Pulseaudio is outdated, Pipewire AND Pulseaudio are now needed. Maybe also just Pipewire, and you can somehow fake Pulseaudio?

    I never used a system without Pulseaudio, and Fedora has both (?) Or just Pipewire.

    Pulseaudio is the old stuff that apps want to use, pipewire is the new cool stuff (I recommend qpwgraph) which allows like everything.

    Aaand it is not overcomplicated, it isolated apps and introduces a permission system. Privileged programs that channel the requests and permissions, and sometimes need user interaction. Its actually less chaotic, the problem simply is that Flatpak ALSO tries to run all apps everywhere. And apps are mostly not up to date, so Flatpaks have randomly poked holes everywhere.

    Today I worked on hardening configs for my apps. I maintain a list of recommended ones here. I will just put my overrides in my (currently still private) dotfiles, will upload them some day.

    I am for example now Wayland only. Not all apps want to, but with the correct env vars (which I just globally set for all flatpaks, hoping it will not mess with anything), all apps use it.

    This makes the system way faster, and applying different vars on the apps is very easy with Flatpak.

    Literally no downsides!

    Not true. It still has no updating mechanism, the binary may be official, but the rest are random libraries that may not be well versioned or controlled, etc etc.

    The post is specifically about upstream supported Appimages, while Flathub is mainly maintained by the same 4 peolple (it is crazy). The request is for upstream devs to maintain Flatpaks.

    But for sure not everything is nice. Runtimes are too huge, outdated apps cause huge library garbage, downloads are inefficient, …




  • Pantherina@feddit.detoLinux@lemmy.mlSwitching from win 11
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    8 months ago
    1. Good that only you do this, as a whole company setup is complex
    2. Pop_OS is currently not that well maintained afaik, their GNOME desktop is quite outdated.

    Just using their OS for the hybrid graphics support is a valid point, but should not be the only one.

    Having a well managed OS is crucial, but I disagree that Ubuntu base is the best here.

    For stability, a centrally managed Fedora Atomic would be better I think. Way more stable, image-based, all peolple would have exactly what they need.

    You could build images locally and take care of the exact updates like that. Or you just share specific configs for each role, like preinstalling different software.

    But having things like specific policies, any files, hardening etc. is totally possible during image creation.