uWolf (LibreWolf)

arubislander

What is wrong ?
UB 24.04 (2025-10-19)

Your issues are probably due to the fact you are running 24.04. The version of uWolf in the Open Store is for 20.04 at the moment.

mikirc

@arubislander
Ok, but i install 20.04 and error is almost same. As from openstore as uwolf package.

arubislander

@mikirc This also happens when you open the app from the Drawer instead of directly from the Open Store?

mikirc

@arubislander said in uWolf (LibreWolf):

This also happens when you open the app from the Drawer instead of directly from the Open Store?

Yes, result is same

arubislander

@mikirc Then it might be an issue specific to your device or device port. Otherwise more users would have reported this.

Keneda

@mikirc
You may consider opening an issue on uWolf repo ?

mikirc

@Keneda said in uWolf (LibreWolf):

@mikirc
You may consider opening an issue on uWolf repo ?

Ubuntu Touch 20.04 is unusable for the Lenovo M10 tablet. Version 24.04 runs well, but it doesn't include a usable web browser. Until uWolf is available for version 24.04, it doesn't make sense for me to deal with it.

pparent

@haagch said in uWolf (LibreWolf):

My hope for real wayland support is that it improves not rendering stuff when idle.

Currently when I run uWolf and power off the screen (even when I focus another app), lomiri permanently uses 30-40% cpu and pulseaudio 15%.

00b16def-826f-477d-8885-69a1d82969f3-image.png

This makes the phone a nice pocket warmer, but also sucks the battery pretty fast.

Or currently, might there be a way to tell firefox to drop its rendering while the screen is off or another app is focused, like maybe "minimizing" it in xwayland?

This is an Xmir problem , same result with signal desktop

https://forums.ubports.com/topic/11538/xmir-lomiri-high-cpu-usage-battery-drain.

ChromiumOS-Guy

@mikirc it works in Noble, just the overlay for the OSK is broken.

I am doing work on NixManager and cannot two time it with uWolf right now but I will get to it after I finish with that.

haagch

The small UX problems have been mentioned, but I think the biggest one is that quite often the touchscreen input mapping breaks. I think it happens especially after an accidental drag & drop trigger, on an image on a website, or on a tab. Then there is a good chance that either a) one touch input seems to be stuck so if you try to just scroll down with one touch, it does a pinch zoom instead, or b) the touch input is clamped to a part of the screen and you don't have touch input outside of that area. This is probably related to the landscape mode issue, but this is easily triggerable even when the phone is in portrait mode and rotation is disabled. I'm not sure you can do much about that, but it is a real issue because the only way to get proper input back I found so far is killing the app and restarting it.
This applies to bluetooth audio and usb audio (the latter apparently works now). It does NOT happen with built in speakers: Firefox likes to control the global volume. Example: Play any audio (e.g. https://radiomii.com/ or any app). Go to youtube in uWolf and start a video. Bam, 100% volume blasting your ears.

Not sure if MOZ_DISABLE_PULSEAUDIO=1 is really a thing (only 1 google result from last month?) but I tried os.environ["MOZ_DISABLE_PULSEAUDIO"] = "1" and it doesn't make a difference. I tried that because I assume the issue is with how firefox creates a separate stream for every tab/media.

In about:config I only saw media.default_volume but not even that seems to do anything about this behavior.

Does anyone know if there would be a way to make firefox behave?