@domubpkm ofc the setting is there you can either enter you're own use the local network dns or choose from the presets provided by Librewolf.

@haagch i'm going on vacation today so development is going to be slower then usual combine that with the NixManager plugin for Noble which im also working on, and the fact i just moved all my devices to Noble in preparation for moving uWolf to Noble proper and i can't really do much about it.

but uWolf is janky like that because of Xwayland if the OSK gives you problems enter the wayland windows (the one with the icon and loading gif) it will redirect you back to the browser but in most cases will also unstick the OSK and make it work again, because somehow Xwayland "unselects" the window that is the browser.

@Vlad-Nirky Librewolf not uWolf, Librewolf itself uses it yes, i don't know if its over https for sure but it seems so yes.

@domubpkm by default Librewolf is going to use its own DNS, its usually Quad9 with no filtering.

@rdfrs thats because apparmor rules (waiting for fix to trickle down to stable releases ask @Fuseteam he knows about this better then me)
confinment is mostly done, not a priority though because it will not raise security as much as you think only make it clearer to you the user what i am doing on you're phone, which granted is a very good reason and is why im working on it. (there is a branch with confinement implemented im just waiting until it won't break the app to use)

@arubislander i would say option 5 is what you mean.

Hi someone by the name of AdamSchrey (on Github) created a bunch of nice Icons for uWolf and I would like to hold a vote on which one to choose from the icons he created the icons can be found here

EDIT: this will be the new logo, hope everyone is happy with the decision

@Simmonz this is the fix @TotalSonic is referring to (kind of) https://gitlab.com/ubports/development/core/qtmir/-/merge_requests/92
once this is upstreamed firefox and by extension LibreWolf will be able to use wayland directly.

once its upstreamed I'm also planning on releasing my freetube port.

@RJDan there is the same option but for cookies

Hi @theprivacydad Developer of uWolf here.
LibreWolf is focused on privacy and security, By default LibreWolf will delete cookies when closed you can change that in about:settings

copy/paste as mentioned already is one of many symptoms of being forced to use XWayland there is a fix on the way but until it is merged no dice unless you want to install it through the qa tool and remove the XWayland flags from the launch script in uWolf but I would not recommend that.

@RJDan the copy/paste thing is going to be solved when this fix roles out, as it is a symptom of using XWayland.

As for erasing all tabs LibreWolf is privacy/security focused so this is default behavior, you can turn it off in about:settings

@RJDan hmm, i may be able to do something about syncing passwords, but it would require cooperation from the UT development team.
no promises though I already have my plate full with the upcoming rewrite of uWolf for Noble and NixManager plugin for lss (which i'm waiting on a test device so i can start working on the UI)

@domubpkm can you give me the log from the logviewer app?
also dmesg | grep DENIED and dmesg | grep uwolf

@AmauryDBZ as in still not showing chrome?

try running: gsettings get com.lomiri.Shell usage-mode
I'm thinking you're device has an edge case which makes the is_usage_mode_staged() make a false negative, this command is what's responsible for toggling the custom UI (after all you don't need it with a screen/keyboard connected).
essentially this is the code for deciding if its using stages or window mode:

if usage_mode == r"'Staged'" or usage_mode == None: # check if staged, fallback if nothing was outputed to most likely.
    return True
return False # if check fails then its not Staged

point is I'm suspecting the output is not 'Staged' in text (including the ' ')

@AmauryDBZ url about:support , there should be a big button named clear startup cache.

@domubpkm indeed, I am currently trying to up the security by trying to make app confinement work if nothing else it will make it clear to the user what exactly am I accessing because I will still need some special permissions but this will become much more secure.

you can test the experimental confinement here, this has the same functionality as v0.10.30

@domubpkm the goal was bring it to usable state before the switch to Noble
it is as close as possible more optimization while possible is unlikely to happen, at most I will fix bugs until I make a proper Beta version for Noble.

in Noble i can use ubports-qa to install the needed MR's to get wayland working so i can actually get the browser to be usable as I don't consider it usable right now on low-spec phones like my own phone.

@AmauryDBZ theres a new update, just in case try to upgrade to it if you haven't already.

if that doesn't work please try going here: about:support and clear startup cache.

@domubpkm try to reinstall v0.10.30 i patched it it should work now.

@domubpkm yeah idk how or why you use a virtual framebuffer that means no hardware acceleration in most cases,
try running the command

cat /sys/class/graphics/*/modes
fbset -s

if this gives you a list of resolutions tell me, I'll implement reading this as a fallback.

also not related but because you use a virtual framebuffer you could potentially hack together a way to have nightlight.