So this isn’t really an answer on how to migrate but this solution has worked well for me.
I define the toolboxes config with it, and if it gets destroyed, recreating it is as simple as creating a new one with the same name. You could upgrade or downgrade by just creating a new toolbox with the version you want.
I found this. I didn’t look at the code at all but the Readme mentions another project that might help.
You didn’t like flying through 150 rings?
Bash is my login shell, but I have fish set as the default shell for alacritty
That’s really weird. I set up a test system and I couldnt reproduce. The only thing I noticed errors flooding dmesg about elogind already running when I enabled it following the docs. I guess sddm is already starting it?
I dont see how that would cause your issue though. I would probably just reinstall lol
If you CTRL-ALT-F3 and login to a non graphical session does everything work as intended?
Did anybody think that they did?
I always assumed they were just easier to set up
I am root I am admin I am user I am all.
Holy shit I almost died
Yeah pretty much, but it’s wayyyy faster. There’s times where it feels like dnf is hanging trying to download metadata that’s 25KB. I have 1Gb down and it takes like 2 minutes, its ridiculous. I know in the grand scheme of things I’m being petty. But it’s frustrating when the metadata step takes longer than downloading 500MB of packages lol
I’ve been using dnf5 for a few weeks now. I never want to go back. If you use fedora, seriously consider checking it out. The only thing I’m missing is the provides subcommand.
Is that a 32 bit cpu?
If you run in distrobox you should not have issues with dependencies
I’m surprised it booted lol
The only thing that came up was some memory allocation/cgroup/.slice stuff for the container.
I’m not on that network anymore, and the problem is gone. So I cant reproduce.
Maybe I should have run wireshark?
The card is Realtek. I found an askubuntu thread where all flatpak commands were hanging, and their solution was to disable the nic.
This has only happened on this network. I didnt mention at first because I didnt think it mattered, but I’m visiting someone and moved networks.
The instant I take the dev down, the browsers pop up. I would bet money that when I go to my home net everything will work.
The flatseal angle didnt work either. The only reference is names on system bus.
Nope it’s all green.
Idk if you saw my update but turning of the wifi fixes this problem.
I did move to a new network yesterday, I just didn’t think that could impact the flatpak launch, while not affecting the systems binary launch.
It’s a real head scratcher
I uninstalled, it didn’t change anything :(
The gnome portal is not running. The gtk and wlr portals are, as they have been for months with no issue.
xdg-desktop-portal-wlr.x86_64 0.7.1-1.fc39
xdg-desktop-portal-gtk.x86_64 1.15.1-1.fc39
I tried restarting portal, didn’t work. systemctl status for xdp did show an error for hyprland about a config file. But I’m running on sway mainly. I just tried out different DE’s to see if anything changed.
Here’s flatpak output
flatpak run --verbose io.gitlab.librewolf-community
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/auser/.local/share/flatpak
F: Opening user flatpak installation at path /home/auser/.local/share/flatpak
F: Opening user flatpak installation at path /home/auser/.local/share/flatpak
F: /home/auser/.local/share/flatpak/runtime/org.freedesktop.Platform/x86_64/23.08/329ad0f04e21dc3234accff013641299e13a9eb2f1b2908129692b4755393789/files/lib32 does not exist
F: Cleaning up unused container id 75319174
F: Cleaning up per-app-ID state for io.gitlab.librewolf-community
F: Allocated instance id 821024549
F: Add defaults in dir /io/gitlab/librewolf-community/
F: Add locks in dir /io/gitlab/librewolf-community/
F: Allowing dri access
F: Allowing wayland access
F: Allowing pulseaudio access
F: Pulseaudio user configuration file '/home/auser/.config/pulse/client.conf': Error opening file /home/auser/.config/pulse/client.conf: No such file or directory
F: CUPS configuration file '/home/auser/.cups/client.conf': Error opening file /home/auser/.cups/client.conf: No such file or directory
F: Running '/usr/bin/bwrap --args 43 /usr/bin/xdg-dbus-proxy --args=45'
F: Running '/usr/bin/bwrap --args 43 librewolf'
A lot of times you will see the format string for the fedora version in the .repo file. This means its probably looking for f41. Since fedora updates fast, third party repos are usually slow to move to the next version and this repo probably doesnt exist causing dnf to fail. You can try and change the format string to the last available version. It usually works without issue, and updates aren’t disabled as long as the vendor updates that version