Software renderer used on Ubuntu 24.10 wayland with Nvidia GPU and Firefox snap
Categories
(Firefox Build System :: Third Party Packaging, defect, P3)
Tracking
(Not tracked)
People
(Reporter: alexandre, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(8 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:132.0) Gecko/20100101 Firefox/132.0
Steps to reproduce:
I tried Ubuntu 24.10 with Wayland on my PC which includes a Nvidia RTX 2080 GPU.
My nvidia driver is the latest available directly from Ubuntu : 560.35.03 (nvidia-driver-560-open)
Actual results:
Scrolling in web pages is janky with a lot of stutters.
Seeing videos on Youtube leads to a lot of CPU usage.
When I look at about:support, I see that Firefox is not using my GPU to render web pages. I see "Webrender (Software)" and "Mesa -- llvmpipe (LLVM 15.0.7, 256 bits)" in WebGL driver.
Expected results:
Smooth renderer of webpages.
Reduced CPU usage with GPU rendering, like on the X11 session.
| Reporter | ||
Comment 1•1 year ago
|
||
| Reporter | ||
Comment 2•1 year ago
|
||
| Reporter | ||
Comment 3•1 year ago
|
||
| Reporter | ||
Comment 4•1 year ago
|
||
| Reporter | ||
Comment 5•1 year ago
|
||
Contrary to what I said on my initial comment, Firefox is not using my GPU in the X11 either.
I have software renderer in about:support too.
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 6•1 year ago
|
||
And to be absolutely clear, the Firefox flatpak from Flathub has not this issue.
| Reporter | ||
Comment 7•1 year ago
|
||
Comment 8•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•1 year ago
|
Comment 9•1 year ago
|
||
The severity field is not set for this bug.
:gerard-majax, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 10•1 year ago
|
||
The flatpak about:support mentions X11, is comment 5 correct ? Is this a regression ? Do you reproduce on edge channel ?
Comment 11•1 year ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:gerard-majax, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Updated•1 year ago
|
| Reporter | ||
Comment 12•1 year ago
|
||
(In reply to :gerard-majax [PTO] from comment #10)
The flatpak about:support mentions X11, is comment 5 correct ? Is this a regression ? Do you reproduce on
edgechannel ?
The Firefox snap is not using hardware acceleration in X11 either.
I will try on edge channel.
| Reporter | ||
Comment 13•1 year ago
|
||
The problem seems to be SOLVED on the Firefox snap in the "edge" channel !
| Reporter | ||
Comment 14•1 year ago
|
||
Comment 15•1 year ago
|
||
I confirm that the issue is resolved when using edge channel of snap. Firefox version: 136.0a1, Nvidia driver version: 565.77
Comment 16•1 year ago
|
||
I can also confirm that this is fixed in the edge channel of snap on a Ubuntu 24.10 install with nvidia driver 560. For me, the problem still exists in the stable and beta firefox channels.
Comment 17•1 year ago
|
||
(In reply to Scott K from comment #16)
I can also confirm that this is fixed in the edge channel of snap on a Ubuntu 24.10 install with nvidia driver 560. For me, the problem still exists in the stable and beta firefox channels.
Can you try the core24 on the stable channel?
Comment 18•1 year ago
|
||
I'm not very familiar with snaps. Nonetheless, I am happy to try to help. Do you mean follow this process for firefox stable? https://forum.snapcraft.io/t/how-to-patch-a-broken-snap-locally-changing-base/30596/3
I tried doing that with firefox snap from the stable channel and switching it to core24, but it still resulted in software rendering.
Comment 19•1 year ago
|
||
(In reply to Scott K from comment #18)
I'm not very familiar with snaps. Nonetheless, I am happy to try to help. Do you mean follow this process for firefox stable? https://forum.snapcraft.io/t/how-to-patch-a-broken-snap-locally-changing-base/30596/3
I tried doing that with firefox snap from the stable channel and switching it to core24, but it still resulted in software rendering.
No, it should be just sudo snap refresh --channel=latest/candidate/core24 firefox
Comment 20•1 year ago
|
||
(In reply to :gerard-majax from comment #19)
(In reply to Scott K from comment #18)
I'm not very familiar with snaps. Nonetheless, I am happy to try to help. Do you mean follow this process for firefox stable? https://forum.snapcraft.io/t/how-to-patch-a-broken-snap-locally-changing-base/30596/3
I tried doing that with firefox snap from the stable channel and switching it to core24, but it still resulted in software rendering.
No, it should be just
sudo snap refresh --channel=latest/candidate/core24 firefox
Yes, latest/candidate/core24 channel does fix the issue.
| Reporter | ||
Comment 21•1 year ago
|
||
I can confirm too, latest/candidate/core24 channel fixes it for me.
| Reporter | ||
Comment 22•1 year ago
|
||
Comment 23•1 year ago
|
||
That also fixes the problem for me. Thanks for your help!
Comment 24•1 year ago
|
||
Nathan, Sebastian, I suspect this is something we expected?
Comment 25•1 year ago
|
||
Yes indeed, the newer libraries in the 24 base allow this.
Comment 26•1 year ago
|
||
Yes, it's a known problem, we bundle currently the mesa version from 22.04 which might not have supported some hardware. Switching to core24 will bring a newer version which should resolve those issues.
Comment 27•1 year ago
|
||
Another confirmation that v24 fixes this issue.
https://fosstodon.org/@chris_hayes/114091565335195827
Updated•10 months ago
|
Description
•