(As it turns out, the cause was a previous attempt to get xdg-desktop-portal-termfilechooser to work - I’m just going to sneak this edit in here and go die in a corner or something)
It’s not even that, I wanted to try using Ranger as the file chooser because Dolphin would freeze up if it ended up in a tmpfs mount point… which I can deal with if the only alternative is the default GTK file chooser.
My package manager has 400+ updates, but I can’t install them because some packages are conflicting, and I don’t have the willpower to untangle that mess.
I use arch btw. I use the arch-derivative Manjaro, btw.
jdk-openjdk vs jre-openjdk? archlinux.org mentions it, although the workaround it provides is fake news and also results in pacman complaining about conflicts.
I just removed stuff, abused pacman --nodeps and prayed that my backups would be sufficient to restore my inevitable fuckup (no fuckup happened, somehow). Try that at your own risk though…
I think I’ll just switch to something more user-friendly again. When I installed Manjaro, I thought I liked tinkering. But since then I’ve started working and just want to get home to a functioning computer.
Manjaro nowadays has become a hassle. It used to be really solid around 5-6 years ago. I had it for 3+ years. Then it started breaking a lot. I switched to EndeavourOS 1.5 years ago, been solid since. The jre/jdk issue was pretty painless to deal with as well.
The jre/jdk issue was pretty painless to deal with as well.
What’s driving me away is that I have to deal with it at all. The command just fails and leaves you to google the solution. That’s annoying and unnecessary.
I know now that Manjaro isn’t the OS for me if I’m not willing to do that.
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.
It does, but the Steam DRM bypassing thing that I’m being peer-pressured into using does not
(not that I’m against buying good games like BG3, it’s just that I’m not going to spend 70€ on a game that is just not my type (plus, there’s peer pressure going on here))
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.
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.
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 wasn’t planning on installing another browser (ignore the post’s title), and joining a Matrix chat for technical help is the last thing I would do due to me being socially awkward…
I’ve been using Linux since 1996 and remember when time_t was less than a billion. I guess I’ve found a new way to date myself. Slightly interestingly I thought, 1 billion was a couple of days before 9/11 which some have said defines the modern era or epoch.
I think that was because Google dropped the controversial part of it or something, idk for sure since I don’t even bother keeping up with web dev. There was the whole WEI stuff to make up for that…
Nah, Mozilla just won’t implement the arbitrary restriction that Google set for content/ad blocking. They’ll be 100% API compatible, without limiting how many blocking rules there can be, which is the only bad part about v3 (or really the deprecation of the unrestricted v2), as far as I’m aware.
Mozilla can also continue supporting v2 for as long as they like. And they can provide additional APIs, which they already do, which is why uBlock Origin is, in fact, already better on Firefox today: github.com/…/uBlock-Origin-works-best-on-Firefox
linuxmemes
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.