There is also AppImage Launcher which works nicely for me. It automatically integrates AppImages into the DE (e.g. search and start menu) and a few other nice things.
Not to be that person but I’m curious what made you go with AppImage over Flatpak, given that you already mentioned using the Flatpak as an alternative ^^"
Use an auto-hiding panel instead and add a taskbar so that your running programs are there. I use that with KDE Wayland and it works well and is highly customizable.
If you love it so much, then you can use Flatpak, Snap, Guix or Nix - there are user-level package managers that will give you the required choice. But why Brave? Aren’t there better Chromium alternatives out there?
I have no idea, but couldn’t this be an XY problem or how it’s called? I mean, do you really need to use apps as different users? Maybe you do, I don’t know, but sometimes it’s good to think about whether the problem you are trying to solve isn’t just a result of another peoblem.
More important would be to have another device where you can go to internet to google or to download binaries for the time if you get stuck.
My first time I couldn’t connect to internet because I was missing firmware for the laptop. I had to use the computer at my work to troubleshoot it and download the necessary package to get it working. That took a lot of days.
If you as a developer wanted a non-technical user to test a thing you fixed for them, you could ask them to try an AppImage from your CI pipeline and they would easily be able to install it. They’re great for that.
Also, trying out a package can leave unwanted system state around in traditional imperative system package managers. AppImages OTOH are self-contained and user-installable.
Does this apply to Proton as well, or have they had their own fixes for Vulkan or something? Cause I’ve been playing games on Wayland with Proton just fine for a good while now.
As long as the laptop boots, you should be able to switch to a TTY console, where you have a complete shell interface to your system after logging in (in said TTY console). So, being greeted with a login screen or something is a win here - but you’re very vague in your report.
The GUI is only just a program and has nothing to do with your boot options in BIOS or bootloader (like grub).
Using CTRL-ALT-[F1-9/0] you can switch between your virtual consoles and on only one of them your GUI is running.
You can use any other one to change anything on the system from CLI.
You should also be able to stop the current GUI/X11 Session and directly start the window manager you wish - temporarily to fix your system, if you’re not confident in the CLI.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.