I-Firefox Community Forum

In the last few days, after some minutes of usage, parts of Firefox become unclickable:

- I can still click on tabs to change tabs. - When hovering over the cross button to close a tab, it changes appearance as it should. Clicking the button does nothing. Ctrl+w still closes the button. - Clicking on the address bar does nothing. - Cannot click on back, forward, refresh buttons. - Cannot click on any add-ons. - Cannot click on preferences. - Can click on the button to open a new tab. There, I can enter an address. Once the page has loaded, address bar becomes unclickable again. - Bookmarks toolbar is still working as expected. - Keyboard shortcuts (ctrl+t, ctrl-w, ctrl-l) still work as expected.

I'm running ``` Mozilla Firefox 138.0 20250428130755 20250428130755 ```

on Manjaro 25.0.1 with GNOME 48

I'm trying to migrate to the newest version of Firefox on an old installation of Fedora. I've downloaded and unpacked the installation files but can't identify the installer. All I probably need is the name, as I know how to make it executable and run it once I know what file it is.

After tinkering with about:config (shouldn't have...) the background of every page that does not specify a body background color turns the color of my theme background color.

Using the firefox color pipette says its white, but it clearly isn't.

The theme i have is dark, making any page that expects the background to be white unreadable (without DevTools -> Body -> background-color: white)

I haven't been able to find the config that fixes it.

My apologies if I am being a numpty, but I have been using Firefox for many years without issue, and recently (possibly after an update, but I cannot be certain), it has started to randomly freeze. I am running Ubuntu 22.04, and Firefox 119.0. I have demonstrated to myself that if I open a web page with links (but not always), and click on the link, I may still scroll up and down the page, but the mouse cursor never seemed to recognise the hotlink, and doesn't jump to it. The links will work on Chromium. I initially tried resetting the browser, thereby losing all my open pages, but that didn't work. That also removed all extensions ("all" two of them) and that didn't work. Firefox is now pretty much unusable. Any help to resolve this would be appreciated, as I cannot find any solutions online, and it seems I am not alone with this issue! Many thanks,

My web site My web site allows user to login with .ejs Sign-up/Sign-in pages then delivers a React page. This works in Chrome and Safari. Https/SSL are provided by my host A2Hosting.

Firefox warns "Cookie “connect.sid” does not have a proper “SameSite” attribute value" when the cookie is set and then blocks the react page after login. If I enter the route that leads to the react page directly I can login and don't get the warning. In both cases the Storage tab in Dev tools shows the same settings for the cookie.

I made sure to remove any cookies for my site before testing the second scenario. I have tested this on Windows, Linux and Android versions of Firefox with the same results.

Here is my Express-Session instantiation ``` app.use(expressSession({

 store: new pgSession({
   pool: pool,
   tableName: 'session'
   // Insert connect-pg-simple options here
 }),
 secret: process.env.SECRET,
 resave: false,
 saveUninitialized: false,

cookie: {

   httpOnly: true,
   Secure: true,
   SameSite: "None",
   path: ['/'],
   maxAge: 60 * 60 * 1000 * 5
 }
 // Insert connect-pg-simple options here

})) ``` I've tried changing the path to include the react app route, I've added it to Cors white list and I converted it to open with an .ejs file instead of .html with no results.

Thanks for your support and for a great browser

This has been a problem for a while, currently on Firefox 126.0 and Nvidia 550.78. I can work around the problem by forcing webrender to use software mode.

When using HW accelerated webrender with my Nvidia graphics card everything works fine until the PC wakes from sleep, then graphics are broken and Firefox needs restarting. Most noticeable for me is when looking at Grafana graphs they will look like random lines, and my Frigate NVR snapshots only display some of the time.

Is there anywhere in Firefox that will show a log of any error messages to do with the graphics card? I would like to try and fix the problem rather than disabling HW acceleration, but with no logs to look at that is impossible. No other programs seem to have a problem with resuming from sleep, and no error messages are shown in any of the system logs.

For now one week, I cannot sync my browser using Firefox sync. When checking the logs, I always see :

Sync.Resource WARN GET request to https://sync-788-us-west-2.sync.services.mozilla.com/1.5/208380794/info/collections failed: [Exception... "The connection was refused" nsresult: "0x804b000d (NS_ERROR_CONNECTION_REFUSED)" location: "<unknown>" data: no] No traceback available

I have tested on multiples wifi network and mobile data and still the same error. After checking, it seem that this server is down, and I don't know were to report this.

Is this the right place to report this or is it a thing I can do to fix that ?

Thanks

I don't know if that was supposed to look like, but when rendering MathML in Firefox 124.0.1 when one uses "mtable" element the browser adds very huge gaps around.

The included image shows output for the following code:

<math display="block">

 <mfrac>
   <mi>A</mi>
   <mn>2</mn>
 </mfrac>
 <mo>=</mo>
 <mrow>
 <mo> ( </mo>
 <mtable><mtr><mtd><mn>1</mn></mtd><mtd><mn>0</mn></mtd><mtd><mn>0</mn></mtd></mtr><mtr><mtd><mn>0</mn></mtd><mtd><mn>1</mn></mtd><mtd><mn>0</mn></mtd></mtr><mtr><mtd><mn>0</mn></mtd><mtd><mn>0</mn></mtd><mtd><mn>1</mn></mtd></mtr></mtable>
 <mo> ) </mo>

</mrow> </math>

I have just encountered another of Mozilla's unwanted, unneeded changes.The three simple little characters that almost all programs show in the upper right hand corner on the screen. These are long standing and well understood icons that were easy to use to manage your windows. Need to switch between program windows? Press the - key. Need to enlarge the screen to its fullest, press the open box, finished working with this program/screen, just click the x-box. Pressing the "open box" would adjust the screen so you could use the cursor to make the screen the siz you needed.

It's not just that these features work and are understood, Mozilla makes changes with no explanation, no other options for doing the same thing (exception: I can close the window with File> Exit (or Close)

I just spent a week getting Thunderbird115+ to "work" and now I have to figure out how to recreate what I've lost on Firefox? Like other people seeking support have said, I want the Firefox I know back.

Firefox uses about half a gig on my disk, that's: '~/.mozilla' and '~/.cache/mozilla' can that be reduced? Either some setting that limits disk use or even a manual deletion of ancient stuff?

the crash reports have been submitted 748057a7-6757-6eb2-955e-9602f9e91008

is there anything else I can do to get this looked into/resolved?

Laptop System: Acer product: Nitro AN515-57 Linux Mint 22.2 Zara \n \l

I have Firefox on Windows, Linux, and Android. Anytime I use Firefox on a desktop, it sends me to Tornado Alley in Kansas. However, I am not in Kansas, and I don't have dog named Toto either. I am in the Detroit area. If I use other browsers, I don't have this problem. It only happens on desktop computers. On my cell phone it shows the correct location. I have already done the simple troubleshooting measure (for a year now: clearing cache, uninstall, reinstall, etc...) and NOTHING removes me from this Tornado Alley, Kansas location on the Firefox browser. If I use Chrome, Opera, Edge, etc... I don't get this problem. It must be something in the Firefox program.

Twice in the past 2-3 weeks I have had to restart the computer, Linux Mint 21.2 Firefox 124(when updated in the past couple of days), due to the mouse freezing up and not being able to move the mouse on the screen. That's not the current problem, but it might help direct things to the final solution.

After the most recent reboot last night now I'm having a rather problem. The up/down arrow keys are no longer scroll me up and down a webpage like they always have in the past. Instead of doing smooth scrolling like they always use to, now they are scrolling me up and down the links on a web page. For example, if I were to be on youtube it would first want to scroll me down the left side links before taking me through each and every video link, when the page goes to load in more videos than it wants to go back and scroll me down the left side links again. It acts like it is taking me through the html code, line by line, instead of scrolling me smoothly down the webpage. The only way I can scroll smoothly down the webpage is to use the mouse on the scrollbar on the right side. It does this both in normal mode and in Troubleshooting Mode.

I have checked and beret scrolling is false as well as beret_shortcut. Use autoscrolling, use smooth scrolling, show scrollbars and always underline links are all clicked on. Always use the cursor keys to navigate within pages is unclicked. I have tried different changes between clicking on and unclicking those options with no change being noticed.

How can I get this back to the way it used to run?

I am on Linux Mint 21.2, and I just updated Firefox (141.0). Now, the bookmarks bar, toolbar, and the tabs (everything above the displayed page), as well as the menu, bookmarks menu, and sidebar, are in light mode even though I have dark mode set (They were dark before the update). I tried playing with the Dark Mode settings to no avail. My system is set to dark mode in general. Are others experiencing this? Is there some sort of fix?

I'm using openSUSE Tumbleweed and KDE Plasma. Ever since I updated to Plasma 6.1, Firefox crashes constantly when using Wayland. I'm not having this problem if I'm using X11. Crash reports are sent after every crash so I'm sure someone can reference these. When starting Firefox from a console, I got this message after a crash: "[GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1#67: error 5: explicit sync is used, but no release point is set"

Will this get fixed with the next Firefox update? Currently using 127.0.

I often run into issues with PDFs in Firefox Linux. They either appear totally blank (typically after suspend/restore), or they appear with the desktop background showing through (as in the attached screenshot).

Hard refreshing the page doesn't change anything, opening a new tab and opening the PDF again doesn't change anything, opening a new window and loading the PDF doesn't change anything.

The screenshot is with this PDF: https://www.sgsw.ch/home/strom/_jcr_content/Par/sgsw_accordion_list_1838160259/AccordionListPar/sgsw_accordion_12353/AccordionPar/sgsw_downloadlist/DownloadListPar/sgsw_download_1049323524.ocFile/2023-08-31%20Mitteilung%20Elcom%20Erh%C3%B6hung%20Elektrizit%C3%A4tspreise%20f%C3%BCr%20das%20Jahr%202024.pdf

It renders correctly in Chromium.

Firefox 126.0 using the recommended performance settings on Mint 21.3, nvidia quadro p620 using the official nvidia drivers v535.171.04-0ubuntu0.22.04.1

I have a Firefox account in order to use the sync capabilities. After a sync between desktop and phone the desktop bookmarks are on my phone in an extra folder "desktop bookmarks" and vice versa the phone bookmarks are in folder "Mobile bookmarks" in my desktop Firefox. Is this normal behaviour? I would expect them in one common folder to have a seamless synching.

Best regards, Walter

I have had this CPU for 8 months. I have had issues from day 1 with the stock Fedora install of Firefox where text is missing and some green and/or pink boxes appear where the text boxes should be. This has happened with all versions up to 129.0.

This has only been happening with Firefox. Vscodium, (chrome based) Brave and every other Wayland application including foot and freecad render correctly. it is only firefox and only firefox with this GPU. If I run Firefox under qemu without eGL then the rendering is good. If I run it under qemu and enable the virtioGL driver I get the same issue.

I attach a sample of a screen shot that shows that was captured from the frame buffer. In the bottom left corner, you can see quite a few characters missing. This happens randomly and sometimes goes away when scrolling.

I have seen other issues that say that it is a hardware problem, but I am not convinced. This happened with mesa-24.2.0. Find the glewinfo attached below: (Glewinfo log is very long, uploaded to Pastebin for better viewing) https://pastebin.com/raw/1NMnAjmc