I don’t know if Firefox is at fault. It could be Firedragon (the fork I’m using), it could be any of the desktop portals messing things up (looking at you, xdg-desktop-portal-gtk), it could be Arch Linux due to how packagers package each portal, it could be that I stepped on a landmine by switching from Sway to Hyprland - this is when the problem first occurred.
Firedragon’s (and the Firefox flatpak’s) output doesn’t say anything, nothing stands out in their logs, same goes for both Sway and Hyprland - for all I know XDG portals don’t even have standalone logs, they just dump error messages to stdout in my experience (which, again, have not been dumped).
I could send bug reports to everyone, and get told “this isn’t our problem, write a bug report to ${OTHER_SOFTWARE}”. But then, which logs do I provide? All of them? Sure, I can gather up logs and non-existent messages from several pieces of software, one of them being a glorified API.
It would have taken me a good hour to find the relevant data, find the correct places to write reports to, word things in a quasi-professional manner, all for a small chance for any of the developers of something to answer something that is not a variation of “can’t help you bro, your logs are anorexic”.
So, after reminiscing the days of writing Windows registry keys and seeing no results (by writing XDP hints all over the system AND rebooting), I took 10 minutes to vent and make a meme - NoScript was intefering with imgflip, otherwise I would have needed 3.
I could not, in fact, definitely have raised a bug report in the time it took me to make this.
I stepped on a landmine by switching from Sway to Hyprland
That’s 100% what it is. Changing desktop environments has almost always led to issues in my experience. If you want to use a different DE, make a new user account or reinstall the distro.
At https://bugzilla.mozilla.org maybe? Or just look up “firefox report bug” online, I guess
I don’t know if Firefox is at fault. It could be Firedragon (the fork I’m using), it could be any of the desktop portals messing things up (looking at you,
xdg-desktop-portal-gtk), it could be Arch Linux due to how packagers package each portal, it could be that I stepped on a landmine by switching from Sway to Hyprland - this is when the problem first occurred.Firedragon’s (and the Firefox flatpak’s) output doesn’t say anything, nothing stands out in their logs, same goes for both Sway and Hyprland - for all I know XDG portals don’t even have standalone logs, they just dump error messages to stdout in my experience (which, again, have not been dumped).
I could send bug reports to everyone, and get told “this isn’t our problem, write a bug report to ${OTHER_SOFTWARE}”. But then, which logs do I provide? All of them? Sure, I can gather up logs and non-existent messages from several pieces of software, one of them being a glorified API.
It would have taken me a good hour to find the relevant data, find the correct places to write reports to, word things in a quasi-professional manner, all for a small chance for any of the developers of something to answer something that is not a variation of “can’t help you bro, your logs are anorexic”.
So, after reminiscing the days of writing Windows registry keys and seeing no results (by writing XDP hints all over the system AND rebooting), I took 10 minutes to vent and make a meme - NoScript was intefering with imgflip, otherwise I would have needed 3.
I could not, in fact, definitely have raised a bug report in the time it took me to make this.
That’s 100% what it is. Changing desktop environments has almost always led to issues in my experience. If you want to use a different DE, make a new user account or reinstall the distro.
It turned out not to be the problem, I just incidentally changed other stuff while doing it
The peak linux experience.
Odd, that’s exactely what my friends tell me when I’m playing BG3 and a bug causes me to get stuck in dialogue (in a Windows 10 VM)
Why in a VM?
Because I’m not installing that thing on bare metal
does bg3 not run on proton ?