[No Longer Issue: Unknown resolution] Opening links opens them cached instead of live
Basically title
21 Replies
Clicking a link outside firefox will cache the page, then open the cached version instead of just opening the link in firefox
this is specific to firefox. Chromium and Vivaldi just open the links
I'm using a layered version of firefox though, not the flatpak
ok, so the flatpak version of firefox doesn't actually have this problem. It's specific to the layered one for some reason?
dude idek how the hell I fixed this lmaoooooo. I just messed around with the kde default app settings and re-created the .desktop files and randomly it's working now
time to not touch it
@tulip another one for your "most cursed linux user" blog post that you're clearly writing at this point 😂
I betchu it's the file extension preference order
I enjoy these kinds of posts. User asks for help, full monolog and user solves own issue. 😂
I'd never seen that before, but some
x- named files in there makes me thing maybe that's how linux/kde handles thatThat is a super weird issue you were getting though
yeah seriously, it was mega weird. I can only imagine it had something to do with me copying the flatpak version of the
.desktop file and not modifying it cleanly enough to work with the /usr/bin/firefox one, so it threw a tantrumAh ok, then it was trying to use that as the default browser
honestly, I do this mainly due to async responses. Much easier to ask for help, then keep trying to solve it myself, when I roughly expect it could be 24-48 hours before I get a response sometimes haha
So all your links opened in a very weird way
they really did 😂
idek if I should mark this as "resolved" since idek what I did to fix it haha
Might be fun figuring out how you broke it in the first place
idk how closely you've been following my issues, but I have to try so hard to keep my machine in basic working function that intentionally breaking it again is a bit outside my sanity rn lmao
because otherwise, I'd love to know what the hell happened lmao
but I think it had something to do with exactly how certain programs were choosing to open the browser. The "default application" didn't actually work, but the "associated filetypes" actually appear to include things besides actual literal files
I have Bazzite installed on an external SSD drive enclosure. Which serves as my "playpen" so I don't mess up things in my actual install. It's nice for trying new things.
but idk enough about how wayland works to know if that's a reasonable guess
I have seen a number of your issues lol 🙂 I would recommend the tinkering external SSD for fun and the stable version of Bazzite that you just game on. Found that it gives a nice best of both worlds.
true! I do have an external drive I could put bazzite on tbh, so not a bad plan for sure
I'd recommend an internal ssd that you put in your own enclosure though. Then if you want to make your tinkering SSD your main, you can just swap it around
yeah, I've got a FW, so I can just pop in one of the SSD storage modules 😄
best of both worlds
oh wait, that's what you meant. swap the ssds
yeah don't quite have that luxury with this laptop
Depends on the brand. For my HP 2 screws and the drive is out. If I have to pull the thing apart.... I'd rather just copy the partitions over with gparted
looks like for whatever reason this flag matters:
/usr/bin/firefox --file-forwarding org.mozilla.firefox
wait no, that's a flatpak run flagim just gonna say
good thing we dont support layered firefox then :clueless:
nah, it was an issue with my
.desktop file. I fixed it