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.
Perhaps an invalid opinion, but a bug report that falls outside of scope because of lack of detail or lack of reproduction is still a valid bug report for metrics and general user experience imo. Could lead to interoperability efforts, user experience recommendations, user education utilities, or a bug getting patched but the end result is always the same: a better experience for the end user.
In that case you could maybe see if it works correctly for you in firefox installed via flatpak from flathub. Those are official builds and bug reports on them should go to Mozilla directly.
It could be related to hyprland though. I think I read somewhere that one of those lightweight WMs (or whatever it really is idk sry lol) doesn’t ship a portals config file for x-d-p to exactly know which exact implementation to use. Maybe arch doesn’t have that issue though
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.
As I said in another other comment to someone else, there is a quite noticeable difference in effort between typing sentences on imgflip and hunting bugs.
The only thing I can correctly report is that the termfilechooser portal causes something to die somewhere at some point - it never even worked in the first place.
I disagree.
Some months ago I had weird behavior with compose sequences, I went on the ff c, made a post on it, and there was a fruitfull discussion leading to pinning it on gtk doing compose sequences weirdly. No hate was experienced.
I’ve noticed what that person is saying outside of the Firefox community, the evangelism and all, and then criticism of Firefox and more specifically Mozilla’s actions in the Firefox community. Case in point, someone laying down the issues with the upcoming Fakespot integration.
You could definitely have raised a bug report in the time it took you to make this
I cannot even determine the culprit, to whom am I supposed to file a bug report?
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.
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 ?
Firedragon is a fork of Librewolf (which is a fork of Firefox), not Firefox. It’s not Firefox at fault.
Case in point
(although Firefox (the Firefox Firefox) also refused to work)
I hate not knowing if my bug report is valid.
Perhaps an invalid opinion, but a bug report that falls outside of scope because of lack of detail or lack of reproduction is still a valid bug report for metrics and general user experience imo. Could lead to interoperability efforts, user experience recommendations, user education utilities, or a bug getting patched but the end result is always the same: a better experience for the end user.
In that case you could maybe see if it works correctly for you in firefox installed via flatpak from flathub. Those are official builds and bug reports on them should go to Mozilla directly.
It could be related to hyprland though. I think I read somewhere that one of those lightweight WMs (or whatever it really is idk sry lol) doesn’t ship a portals config file for x-d-p to exactly know which exact implementation to use. Maybe arch doesn’t have that issue though
I’ve read through all the possible bug reports and forum help requests, and used the flatpak Firefox at every point I tried a solution.
In the end I managed to solve the problem, though I’m sure it’ll pop back out at some point.
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
Everyone involved, worst case they just close them
As I said in another other comment to someone else, there is a quite noticeable difference in effort between typing sentences on imgflip and hunting bugs.
Well, you’ve determined a major part of what’s causing it. There is not much more to add, just submit what you have.
The only thing I can correctly report is that the termfilechooser portal causes something to die somewhere at some point - it never even worked in the first place.
It’s above my 0$/h paygrade at this point
“works on my machine” closes bugreport
sudo bugreport “plz fix”
This incident has been logged.
Great, I can use that to report the error to every single contributor and packager of my 1802 installed packages!
rootCareful, the FF community here hates it when you point out faults in their “perfect” browser
I disagree.
Some months ago I had weird behavior with compose sequences, I went on the ff c, made a post on it, and there was a fruitfull discussion leading to pinning it on gtk doing compose sequences weirdly. No hate was experienced.
I’ve noticed what that person is saying outside of the Firefox community, the evangelism and all, and then criticism of Firefox and more specifically Mozilla’s actions in the Firefox community. Case in point, someone laying down the issues with the upcoming Fakespot integration.
gecko good, blink bad
this is so much better though