I-Firefox Community Forum

I always use the middle mouse button (pressing the scroll wheel) to open and close new tabs, but since the update, it doesn't work anymore and now types "=" if the cursor is in a text field. For context, I use an MX Master S3, mapped with Logi Options+.

Anyone else having this issue? How do I roll back to the previous version??

SOLVED: It was a bug with Logi Options+, not Firefox. When I hovered over the tab for the presets I had for CaptureOne, I noticed it also said Firefox. So seems something weird happened there. Deleted that preset and the issue in Firefox went away.

I couldn't find a way to delete this thread, though.

I had Firefox installed and working perfectly fine , but I had to factory rest my MSI laptop (windows 11 home) because I had suspect suspicious files I needed to get rid of, after the new install of Firefox each time I try to sign into a google account I would be able to type 2/3 letters and then Firefox crashes and closes down , I had uninstall and downloaded a fresh install from the microsoft store

When I press a hotkey that involves Ctrl (ie. opening a new Tab via Ctrl+T or closing one via Ctrl+W) Ctrl sometimes remains stuck until I press it again. This will cause issues ie. when I open a new tab and try to type a new address (or search term), and Ctrl causes new hotkeys to be executed.

I've even tried launching firefox with a new profile, and on safe mode (firefox --safe-mode -p <something-else-than-usual>), so no bookmarks, cookies or extensions should be causing this, and it will still happen sometimes. The annoying part is that this seems to be an issue with performance. It happens less-often with the empty profile and safe mode, but it still happens, especially if I had just opened a new page some tab, causing the most minute thing for firefox to process.

The problem is probably not the computer specs either (below my specs). Indeed, from what I can tell, firefox does not even seem to function particularily slow in any case. Just this ctrl being stuck seems to happen.

I have also tried disabling hardware-acceleration (and explicitly enabling it), no effect.

Other interesting facts I've discovered: - This for sure does not happen in other programs and - This does not happen with the Ctrl for all the keybinds within firefox. For example, Ctrl+A (for select all) does not trigger this

From neofetch my setup is OS: Arch Linux x86_64 Host: MS-7C56 1.0 Kernel: 6.12.8-arch1-1 Uptime: 2 hours, 10 mins Packages: 2370 (pacman), 7 (flatpak) Shell: zsh 5.9 Resolution: 3840x2160 DE: labwc:wlroots WM: sway Terminal: alacritty CPU: AMD Ryzen 9 5900X (24) @ 4.951GHz GPU: AMD ATI Radeon RX 7900 XT/7900 XTX/7900 GRE/7900M Memory: 5531MiB / 32015MiB

(I have no idea why it's reporting that I'm using Sway, I'm most certainly only using labwc, maybe labwc just reports sway for some programs for compatibility) I've installed firefox from pacman, and my current version is firefox 134.0.1-1

And finally firefox --full-version Mozilla Firefox 134.0.1 20250113214611 20250113214611

I'm not sure what else I could share at this point

Submitted Crash Reports Report ID Date Submitted bp-28e075fd-226a-4a7c-bbeb-4066f0250119 19/01/2025, 12:16 pm View bp-ddcd262a-6efe-49db-b2fd-db21f0250119 19/01/2025, 12:16 pm View this happens at the most annoying time, I have submitted the crash reports as advised.