Open Bug 1974517 Opened 8 months ago Updated 6 months ago

snap package firefox 140.0.1-1 defect

Categories

(Firefox Build System :: Third Party Packaging, defect, P2)

Firefox 140
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: pieterkristensen, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0

Steps to reproduce:

installed firefox snap 140.0.1-1 on linux kde neon user on two rather different computers

Actual results:

I can't read or write on the adress bar
hamburger menu unusable
even the profile manager (firefox -p) is unusable
firefox deb (same version) works 100%

Expected results:

I should be able to input, and otherwise use firefox

The Bugbug bot thinks this bug should belong to the 'Firefox Build System::Third Party Packaging' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Third Party Packaging
Product: Firefox → Firefox Build System

Firefox snap esr works fine.
Installed it using the snap store.

version 140.0.2-1 has the same issue. I have always used the snap version and there have never been problems before.

I can confirm this issue. I found that this happens only under Wayland; under X11 I was able to use this package of Firefox 140 just fine. Reverting to Firefox 138 restored full functionality, even in Wayland. I am using Ubuntu 23.10 with KDE. I'm happy to run other experiments or provide additional system information.

(In reply to pieter kristensen from comment #0)

firefox deb (same version) works 100%

Just confirming: Same version means 140.0.1 (that is the first dot release of 140) ?
Can you confirm you see also the same build ids in "Help -> About Firefox" ?

Firefox snap esr works fine.

Means 140.0esr ?

(In reply to Adam Compton from comment #3)

Reverting to Firefox 138 restored full functionality, even in Wayland.

What about 139, did you test it?

Note that I am not seeing any such issues with the snap release 140.0.2 on Wayland/Gnome (Ubuntu 25.04) here, so there might be either a KDE specific twist or even a single machine/configuration issue. If possible I'd recommend to test with a fresh installation to see if any profile specific things got in your way, maybe even for a different test user with a clean home.

Flags: needinfo?(pieterkristensen)

I just installed firefox snap 140.0.2-1 on my kde box. It still is a mess.
I created a fresh/new user on my system and started up firefox there: also a mess.

esr version:
I took the first esr "snap search" had to offer. It worked great on my kde box.
I definitely believe that this is NOT a problem in my user-profile.
Thank you

Flags: needinfo?(pieterkristensen)

(In reply to pieter kristensen from comment #5)

I just installed firefox snap 140.0.2-1 on my kde box. It still is a mess.
I created a fresh/new user on my system and started up firefox there: also a mess.

Thanks for checking.

esr version:
I took the first esr "snap search" had to offer. It worked great on my kde box.

On my Ubuntu system that would be indeed 128.12.0esr-1, so a way older base version. That does not really tell us much, I fear.

snap info firefox
name:      firefox
summary:   Mozilla Firefox web browser
publisher: Mozilla✓
store-url: https://snapcraft.io/firefox
contact:   https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla
license:   unset
description: |
  Firefox is a powerful, extensible web browser with support for modern web application
  technologies.
commands:
  - firefox
  - firefox.geckodriver
snap-id:      3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
tracking:     latest/stable
refresh-date: 6 days ago, at 08:19 CEST
channels:
  latest/stable:    140.0.2-1     2025-06-29 (6436) 257MB -
  latest/candidate: 140.0.2-1     2025-06-27 (6436) 257MB -
  latest/beta:      141.0b6-1     2025-07-04 (6474) 258MB -
  latest/edge:      142.0a1       2025-07-07 (6483) 292MB -
  esr/stable:       128.12.0esr-1 2025-06-24 (6380) 284MB -
  esr/candidate:    128.12.0esr-1 2025-06-20 (6380) 284MB -
  esr/beta:         ↑                                     
  esr/edge:         ↑                                     
installed:          140.0.2-1                (6436) 257MB -
Flags: needinfo?(nathan.teodosio)

Can you please give more details pertaining to the operating system? Info center > Copy details > Paste here.

I couldn't reproduce any of the problems on the current user ISO from KDE Neon Noble, Wayland.

Flags: needinfo?(nathan.teodosio) → needinfo?(pieterkristensen)

Thank you for taking so much time

Operating System: KDE neon User Edition
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.0
Kernel Version: 6.11.0-29-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz
Memory: 8 GiB of RAM (7.6 GiB usable)
Graphics Processor: Intel® HD Graphics 520
Manufacturer: Dell Inc.
Product Name: Latitude 5480

But on my other machine it's exactly the same. After I send this reaction I will walk to it and send these details of that machine

Flags: needinfo?(pieterkristensen)

Other machine:

Operating System: KDE neon User Edition
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.0
Kernel Version: 6.11.0-29-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Celeron® J4105 CPU @ 1.50GHz
Memory: 8 GiB of RAM (7.4 GiB usable)
Graphics Processor: Intel® UHD Graphics 600

Still, the fact that it happens with a clean user profile seems to tell that the problem lies deeper than with the user...

So I tried to install firefox 142 alpha on the second machine.
But first I had to uninstall the current firefox snap package.
This seems to be not possible.
I did

  • sudo snap remove firefox and after that
  • sudo snap remove --purge firefox
    Than I rebooted and gave in the konsole
  • sudo snap install firefox --edge, but the system returns
  • snap "firefox" is already installed, see 'snap help refresh'
    Strange

Hi Pieter, thanks for your response. That is about the same operating system information that I collected in my tests. But I tested in a virtual machine. So maybe this is a graphics bug, bound to the graphics card. A screen-shot of the bug could help determining that; You could also disabling hardware acceleration in about:preferences in any case and seeing if it helps.

When a snap is already installed, you can directly use refresh (instead of removing and installing from a different channel):

sudo snap refresh --edge firefox

This is indeed a good testing idea, as Firefox from the edge channel is based in newer Ubuntu, with newer graphics packages than the one in stable.

Flags: needinfo?(pieterkristensen)

Suddenly the firefox 140 snap seemed to be removed. So I installed 142 snap and it worked very well. Only, it doesn't respect de kde/plasma accent color.
Do you know if there is anything I can do about that?

Flags: needinfo?(pieterkristensen)

Strange thing is, that until now firefox snap respected the plasma accent color always after I removed the package xdg-desktop-portal-gtk and after that rebooted the system.
That doesn't seem to work anymore...

Suddenly the firefox 140 snap seemed to be removed. So I installed 142 snap and it worked very well.

So the original problem is probably a core22 thing. If you want to stay in Firefox 140 but with core24, there is

sudo snap refresh --channel candidate/core24 firefox

Only, it doesn't respect de kde/plasma accent color.
Do you know if there is anything I can do about that?

No, sorry; Feel free to open a new bug about that, with snap info firefox; snap connections firefox attached.

The severity field is not set for this bug.
:gerard-majax, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(lissyx+mozillians)
Severity: -- → S2
Flags: needinfo?(lissyx+mozillians)
Priority: -- → P2

While this is obviously not something we should ignore, IIUC there is a workaround in comment 14, so downgrading to S3.

Severity: S2 → S3
You need to log in before you can comment on or make changes to this bug.