@rl_dane
- In my tower's
#ArchLinux #KDEPlasma #Wayland boot, both #AnyDesk & #RustDesk work well for my r/a to dad's windoze pc.
- in my tower's newest [3rd] boot,
#Fedora #Kinoite #Wayland, i simply could not get either of those to work properly, regardless of as #Flatpaks, via #Distrobox, or even layered atop the base system. However, happily, RD also comes as an #AppImage, which does work !!

note the above pertain to connections to dad's windoze pc only. otoh, my lappy also runs a Wayland DE, & it is impossible to connect to, afaict -- nothing i have tried works, coz Wayland on the remote pc seems to be an unsolved problem of r/a apps.

@jwcph @itsfoss You can use Warehouse by @Heliguy (thanks) to create snapshots and restore them on the other device - no terminal required! I used this to restore my #flatpaks with their data on a #Librem5 Linux phone after reflashing #postmarketOS.

https://flathub.org/en/apps/io.github.flattool.Warehouse

Install Warehouse on Linux | Flathub

Manage all things Flatpak

One consultant’s #toolkit: #openSUSE Leap, multiple browsers, #Flatpaks, encrypted drives, and no webcam. Real-world use shows Leap’s #enterprise-grade adaptability. #Endof10 #Linux https://news.opensuse.org/2025/10/13/leap-powers-consultants-on-the-move/
Leap Powers Consultants on the Move

For tech consultants, life happens on the move. From airport lounges to boardrooms across Europe and beyond, the tool of choice for one tech consultant is Sl...

openSUSE News
In my Lappy's atomic immutable, Fedora Kinoite, in prior months when i was setting it up, ALL attempts to be able to connect to Dad's pc with either AnyDesk or RustDesk, via either Flatpaks & overlaid rpm pkgs, failed. Hence, now in Tower's KDELinux i've not even bothered with those two flatpaks, not to mention that this atomic does not have a(n easy) way to overlay. Happily i found recently that AppImage works well for VeraCrypt in KDELinux, so i wondered if any of AnyDesk, RustDesk, or NoMachine might have an AI option... & yes, RD does! Aaaaaaand... it works - both for remote-access desktop control, & for file-transfer - yippee!

So, now that i have found effective workarounds for the last lingering papercuts in
KDELinux, which hitherto stopped this otherwise lovely OS being able to be my fulltime daily system [remote-access ✅, VeraCrypt ✅, backups ✅, virtual machines ✅], i tentatively now conclude that henceforth i'll only boot back into either Arch or Sparky when i want to, rather than til now each time i needed to [for the preceding issues] 🎉 🥳 👯‍♀️

The ongoing failure of the
ArchLinux Distrobox in my KDELinux [but no other DB] remains galling [not least that coz it does not work i had to find other ways to solve those tricky app issues], but now it is no longer significantly holding me back.

#DropbearPooterising #Linux #LinuxWomen #FOSS
​ ​​ ​#ArchLinux #KDEPlasma ​​ ​#KDELinux
#SparkyLinux ​#Kalpa  ​#Kinoite
#AnyDesk #RustDesk #Flatpaks #AppImage #NoMachine
@Kroc #flatpaks still have a place for #FOSS software, particularly aging software. Trying to get old software running with contemporary software natively is often difficult or even impossible. Having an isolated container system, like a #flatpak, to run that application makes absolute sense. I use flatpak for packaging for #retrogames and old apps.

@transicorn @Kroc While I like #flatpaks in general, they are still suffering from growing pains. Once #flatpak support is enabled, any logged in user can install additional flatpak software regardless of the system admin's desire. This leads to much abuse. I can't keep my kids from installing minecraft on our #homeschool computers. This is just the tame sort of abuse that can happen. Now think about this in a #corporate environment.

There needs to be a way of whitelisting/blacklisting apps.

Taking the liberty to cross-post my involvement with Fedora Flatpaks; originally posted on Fedora Discourse.

4 years ago, I discovered Fedora Flatpaks, and developed a strong interest with the tech and approach behind it. After having a thorough understanding of it, I wrote two detailed articles about Fedora Flatpaks:

Mind you, I also designed the banners (just highlighting how much I cared about promoting it back then).

I also asked to open a Matrix room (2022/01/01), which was rejected:

https://discussion.fedoraproject.org/t/matrix-room-request-for-fedora-flatpaks/35622

As time went by, I started losing interest, because there wasn’t much progress with the project, and it was duplicating effort that could have otherwise heavily benefited Flathub and every party involved (GNOME, KDE, elementary, freedesktop.org, Endless Foundation, etc.), which would have benefited Fedora, too.

This realization led me to write “Where Fedora Linux Could Improve § Only Ship Unfiltered Flathub by Default”, which criticized the lack of progress with it, as well as addressing one of the “legal concerns” (2022/12/06):

https://tesk.page/2022/12/06/where-fedora-linux-could-improve/#only-ship-unfiltered-flathub-by-default

(Side note: I’ve also heard from Flathub folks that they received legal advice in regards to these issues.)

This led to some community members to react and start the Flatpak SIG project, to accelerate development — 2 days after my blog post (2022/12/08):

https://fedoraproject.org/w/index.php?title=SIGs/Flatpak&oldid=662603

Then, a Matrix room was (finally) created and publicly available (2022/12/10):

https://fedoraproject.org/w/index.php?title=SIGs/Flatpak&diff=prev&oldid=663009

By the way, I was never reached out or invited to join the SIG, despite putting in so much effort and time to accelerate development.

However, despite that, I still tried to participate in the project, and added myself to the SIG as well:

https://fedoraproject.org/w/index.php?title=SIGs/Flatpak&diff=prev&oldid=663089

Any of my suggestions then were either rejected with no proper explanation, shrugged off, or sent to /dev/null. And whenever I asked for source for obvious misinformation, it would be dismissed.

I tried to push Fedora Flatpaks in a direction that would have been less controversial and more productive by limiting its scope, which would also enable us to allocate more resources on other stuff. However, once again, I wasn’t really taken seriously; at least I personally don’t feel like so.

Eventually, I lost every last bit of interest and removed myself from the SIG (2023/02/20):

https://fedoraproject.org/w/index.php?title=SIGs/Flatpak&diff=prev&oldid=669108

All this to say, I tried really hard to keep my opinions to myself, and communicate diplomatically with them; I even wrote articles after doing several hours of researches in the span of weeks to show my interest, but I was treated extremely unfairly in return. So this naturally led me to one conclusion which I still hold today: they’re not looking for diplomacy; they just want to do whatever they want, even if it ends up upsetting/hurting people and projects’ image — I have the same sentiment with RPM packagers, too.

#Fedora #Flatpak #Flathub #Flatpaks

Some Fedora Flatpaks re-use Flathub app's manifests without crediting the authors

Hey Jef, I really appreciate the thoughtful response over the situation. While I’m not a part of Flathub, I’m also grateful that you were considerate when raising concerns to them. I would like to point out that hostility can take in various forms, and can be performed by a small set of individuals within a large group. I sincerely believe that you and the majority of people in the Fedora community are amiable and want the best for everyone — emphasis on “majority”. This is unfortunately not th...

Fedora Discussion
am stuck on the [not entirely unpleasant] horns of a dilemma.

since receiving my various new goodies t'other day [not only, but importantly including, two new
#SSDs; 2 TB & 240 GB], i've been having a bit of a self-inflicted time of it here, atop my swaying gum tree. whilst my main, original, SSD continues to hold entirely lovely #ArchLinux #Plasma & #SparkyLinux #Cinnamon systems, for yonks now i've been getting more & more fascinated by the new kids on the block, being Plasma immutable / atomic systems:
-
#KDELinux
-
#Kinoite
-
#Kalpa

The new 2TB is for my new
#VirtualMachines playground, replacing the recently deceased 2TB HDD. The new 240GB one is to allow me to play around IRL [not just virtually anymore] with those atomics. So over the last coupla days i have been bouncing twixt multiple installations, trying to decide. Today, just before making this post, the latest installed one therein is KDELinux again. It's running quite nicely, & is a bit of a joy to use, but, being only Alpha, has some important problems, incl.
- whilst i've gotten its
#Flatpaks working for app pkgs, it cannot actually do any System Updates atm, neither in Discover GUI, nor in Konsole. My dilemma is that i cannot tell if this is my local problem, or an upstream server fault. If it's the latter then i'm happy to just wait it out, knowing they'll fix it. However if it's my local problem then i could wait til the cows come home & it'll never be right. Dilemma!
- earlier RAW images d/i from the Project Banana site have had broken
#Distrobox, & some have had working DB. My one sadly has a broken DB, which is a showstopper for me unless i can get a good system update that fixes it [but, see preceding point].

What to do, what to do? Wait it out, or bounce on to another reinstallation of Kinoite... or Kalpa?
🤨🤔🤷

#dropbearinterwebz #dropbearpooterising #firstworldproblems

@paulhulford

#Debian 13 #KDE.

#DebianTrixie finds itself very close to the cutting edge even approx. six months after launch. Reasonably new kernel & #Plasma6 combined with #Flatpaks makes for a surprisingly useable OS.

Hot tip: Change fonts to #Inter and bump them up by one point each.

Bazaar é uma peça de software magnifica. Essencial para gerir flatpaks. #LInux #Flatpaks