3 ms·
[deleted]
by avgcorrection 3y ago
[deleted]
- bmicraft 3y agoIt's a well known fact that firefox startup time when packaged as snap is significantly worse. This should be less noticeable for actual use. > On Firefox 119 I thought I was losing my mental faculties (even more) since I kept losing track of the cursor for a whole day. Turns out that it’s a Windows “feature” where you hide the cursor when you start typing into some input box. Maybe this is a Firefox-wide regression on Linux though. Difficult to find other examples of it on Linux via Google. Firefox hides the cursor while typing, but it should unhide as soon as it's moved (at least it does for me) > - More fun than a problem: `firefox --version` spews a warning: `update.go:85: cannot change mount namespace according to change mount ...` > - My dear XCompose wasn’t respected because of course you have to copy it to inside some dang `/home/me/snap/common/utensils/computer-applicances/apps/Firefox` tree Those should both be snap specific. > - The keyboard just does not work sometimes. No other apps seem to have this problem. So it’s apparently not some idiotic “applications that use X work but under Wayland it doesn’t” (or vice versa). Does a restart help? No. Seemingly only a computer reboot. I don't know about that one. Could be Ubuntu or snap, but it does not happen on Arch. Out of curiosity, are you running firefox through xwayland or native wayland? (It says so on the about:support page under "Window Protocol")
- deleted 3y ago[deleted]
- AtlasBarfed 3y agoNow try saving something from Firefox. By default, it shoves it into some parallel file system within the snap. Oh did you forget to actually explicitly save it into the downloads directory? Yeah, you have no idea where it is now. Oh and of course when the download file explorer widget opens up, you can't get the mouse focus. Probably because there's some security boundary between Firefox and the file system. Usability of firefoxes vastly decreased as a result of snaps Finally, well this isn't a big deal to me. Apparently a lot of the open source people don't like it because the Firefox nap is basically just a call. The internet pull down binary command that pulls a huge binary blob and they don't like this.
- avgcorrection 3y agoYes! Downloading things in Firefox has been annoying too now that you mention it.
- ComputerGuru 3y agoI know what you meant but generally really unfair to even mention or phrase it like that. “Downloading things in snap” is more correct. Snap has done such a disservice to open source software’s perceived quality.
- avgcorrection 3y agoOk.
- antod 3y agoWeird. I use the Firefox snap (due to my lazy inertia), and my saves/downloads are all in $HOME/Downloads I don't think I did anything to change that either.
- signaru 3y agoThis is why I've been using Firefox downloaded directly from Mozilla for a while now instead of the broken one shipped with Ubuntu. I just need to manually update via the "Help -> About" every once in a while, but things look much better otherwise.
- avgcorrection 3y agoThanks, I’ll try that soon. Chrome has nothing that Firefox doesn’t have, for me. As long as it works. :)
- ComputerGuru 3y agoYou don’t need to do that. You can install it via apt from the Mozilla ppa, then it updates automatically along with everything else.
- signaru 3y agoIt's nearly a year now that I am using Ubuntu 22.04 (and that the Firefox from Mozilla has no problems) so I don't remember all the details. I also tried using the apt version of Firefox as others also suggested. But it eventually got automatically replaced with the snap version after an update.
- ComputerGuru 3y agoYes, it’s stupid. Recent Ubuntu releases have added meta packages to apt that actually instruct snap to install instead. You have to first add the Mozilla Firefox ppa and then use apt pinning to say that you want the “Firefox” package from this repo and not that one. But then it works forever after.