search

ungoogled-software / ungoogled-chromium-debian

Debian, Ubuntu, and others packaging for ungoogled-chromium
383 stars 49 forks source link

[unified] Severe usability issues on the unified build #247

Closed markozajc closed 1 year ago

markozajc commented 3 years ago

For the past hour I've been trying to get my extensions to work on UGC 94.0.4606.81 to work on Debian Bookworm. So far I've bumped into:

None of these issues have been present in 93 (or 94 on Flatpak (and likely elsewhere as well) as it turns out).

gcvl commented 3 years ago

For the past hour I've been trying to get my extensions to work on UGC 94.0.4606.81 to work on Debian Bookworm. So far I've bumped into:

  • Webpages not loading at all unless HTTPs and uBlock Origin are disabled

Same here on Bullseye.

sagarvora commented 3 years ago

I have the same issue on Ubuntu Focal. Any pointers on how to downgrade?

markozajc commented 3 years ago

@sagarvora I don't think OBS keeps an archive of releases, but I could be wrong. Your best bet would probably be checking out the commit for 93 in this repository (not sure which and on which branch), and building it manually.

awsms commented 3 years ago

No page will load for me, even after disabling every single extension. Using Mint 20

edit: works after relaunching the browser twice.

gadall commented 3 years ago

I'm seeing various browser operations hang, it can be midway while loading a web page, installing or updating an extension, or clearing the cache. At first after starting the browser I can open a page or two and as soon as something gets stuck, subsequent operations hang indefinitely, such as attempting to load a new page, etc., at some point pages don't even begin to load at all anymore. Indeed disabling all extensions doesn't seem to make everything work properly.

markozajc commented 3 years ago

I've observed similar symptoms here too. The browser hung and wouldn't respond anymore after resuming from STR, and generally acted very unresponsive. Could this be an issue with the new memory allocator?

sagarvora commented 3 years ago

I think the new unified build isn't working as expected. Perhaps someone can try the Flatpak to see if the issue persists

markozajc commented 3 years ago

@sagarvora It looks like the release from Flatpak doesn't have these problems (which probably means they're also localized to this project, not ungoogled-chromium in general). I've tried installing uMatrix on a new profile and importing my ruleset on both:

There's definitely something up with the unified build.

gadall commented 3 years ago

Tried with a brand new profile (rm -rf rm -rf .cache/chromium/*; mv .config/chromium .config/chromium-1) and so far it seems to be working. Opening several tabs in several windows, and installed one extension (Proxy SwitchyOmega, hard to live without in this ehhm particular country) and so far so good. The only problem I've noticed so far was in the chrome://extensions/ page, it's just erratic, I had to repeatedly try several methods to install the extensions ("Developer Mode" enabled) and it suddenly just worked by dragging and dropping the .crx file, on the n'th attempt.

markozajc commented 3 years ago

Tried with a brand new profile (rm -rf rm -rf .cache/chromium/*; mv .config/chromium .config/chromium-1) and so far it seems to be working. Opening several tabs in several windows, and installed one extension (Proxy SwitchyOmega, hard to live without in this ehhm particular country) and so far so good. The only problem I've noticed so far was in the chrome://extensions/ page, it's just erratic, I had to repeatedly try several methods to install the extensions ("Developer Mode" enabled) and it suddenly just worked by dragging and dropping the .crx file, on the n'th attempt.

Did not work for me with uMatrix, same issue as before.

gadall commented 3 years ago

Now I tried adding uBlock Origin and everything immediately stopped working. Disabling it on the chrome://extensions/ page immediately made the pending page loads go ahead and complete. This is on the fresh profile, better result than on my exisiting one.

gadall commented 3 years ago

And, it's rapidly degrading. At this point (uBlock Origin disabled) some specific pages consistently hang halfway while loading.

a-kriya commented 3 years ago

@markozajc Anything we can do to help figure out the issue here? What are the differences with the Flatpak build in configuration?

markozajc commented 3 years ago

@a-kriya I'm not a maintainer.

a-kriya commented 3 years ago

@markozajc My bad.

@braewoods Are you going to be able to help with this? Is there any other member of @ungoogled-software that we can bring this in attention of?

ghost commented 3 years ago

@a-kriya You're asking me an impossible question. I don't even know what's causing this. And I don't know chromium that well to even know where to begin to look. All I can guess is it's something to do with packaging differences.

awsms commented 3 years ago

@a-kriya not the first time debian builds are f*cked up, there was another severe issue in a recent build (where the browser would randomly crash). you have to ask this to debian chromium's maintainers (chromium@packages.debian.org).

markozajc commented 3 years ago

@awsms I believe ungoogled-chromium-debian doesn't take from debian's downstream since 94.

ghost commented 3 years ago

That is correct now. I am currently seeing if Chromium 95 helps at all before looking at the packaging again.

ghost commented 3 years ago

I am currently building Chromium 95 on OBS testing repository. I'll see if there's any new build breakage.

ghost commented 3 years ago

On the bright side seems Impish is finally working now.

ghost commented 3 years ago

I speak too soon. Still some kind of build issue with Impish. I've sent an updated build to OBS after fixing build failure with Sid.

ghost commented 3 years ago

I'll do a manual build of Impish since OBS still isn't working currently.

ghost commented 3 years ago

Ok. I just tagged chromium 95 since it works well enough to build. Let me know if the problem is still present. If it is I'll look into some other things I haven't tried yet.

ghost commented 3 years ago

Also if anyone cares to try their hand at fixing it I'm willing to review PRs.

awsms commented 3 years ago

@braewoods: will the v95 builds be available on opensuse repo any time soon for other distros as well? (if you're the one managing it)

ghost commented 3 years ago

Whenever OBS gets around to building them. x86_64 is still delayed by lack of available workers.

markozajc commented 3 years ago

I have built the package manually on my system, and it seems that upgrading to Chromium 95 did not resolve the issues.

ghost commented 3 years ago

Ok, can you document your exact process for reproducing it from a fresh profile? I need something to test against if I am going to get anywhere.

markozajc commented 3 years ago

Firstly: 1) Download and extract uMatrix: https://github.com/gorhill/uMatrix/releases/download/1.4.4/uMatrix_1.4.4.chromium.zip 2) Download 5000 dummy uMatrix rules: https://files.zajc.eu.org/unlist/5000-rules.txt

After you're done, run Chromium 1) Head to chrome://extensions/ 2) Enable 'Developer mode' 3) Click 'Load unpacked' 4) Select your unextracted uMatrix directory 5) If the extension doesn't show up, click 'Load unpacked' again and exit out of the file selection prompt (for some reason it won't install the extension unless you do that, that's another bug that doesn't occur on the Flatpak release) 6) Click 'Details' on the uMatrix extension card 7) Scroll down and click 'Extension options' 8) Click the 'My Rules' tab 9) Do one of the following

dkebler commented 3 years ago

Reporting that I used the flatpak build and all is good with 95.0.4638.54. What is different about that build? Who is responsible for that build anyway?

FYI in focal I had to use the flatpak ppa to get the latest version (universe was way stale) otherwise this version of ungoogled would not install https://flatpak.org/setup/Ubuntu/

gadall commented 3 years ago

As reported in https://github.com/Eloston/ungoogled-chromium/issues/1703 and https://github.com/Eloston/ungoogled-chromium/issues/1698, confirmed with a new profile on self-built ungoogled-chromium-debian 95.0.4638.54-1

Eloston commented 3 years ago

@braewoods I just took a quick look through unified for the first time, and you have a pretty novel setup. As a result, I'm not sure if this will help you, but I have a working version of unportable here: https://github.com/ungoogled-software/ungoogled-chromium-debian/commit/a3103329c50da74ea5736892439981dd186e19ea

I do intend to switch to unified eventually, but I haven't dived into all the details of unified yet to see if it fits my use-case

peebowo commented 3 years ago

Same thing here on Devuan Ceres.

ghost commented 3 years ago

New 95 release merged into unified. I am going to see if it builds on OBS and then start trying some tweaks to address the issue here.

ghost commented 3 years ago

Well at least all the remaining Impish specific issues on OBS have been fixed. So now just need to figure out what's going on with the builds in general.

ghost commented 3 years ago

Part of the problem has been resolved by adding back the launcher flags I omitted. At least it appears to allows the extensions page to import extensions without issue now. I still need to see if there's any solution for the slow import loading.

shaheenfawzy commented 3 years ago

Are there any updates regarding this issue?

ghost commented 3 years ago

Not really, no. I'm only one guy and haven't managed to find the problem yet.

GarikTester commented 2 years ago

Not really, no. I'm only one guy and haven't managed to find the problem yet.

You can always look at this guy's recipe - he never gets a single glitch. Everything related to build options, patches, etc. Besides, its build is unified.

http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/build/chromium.SlackBuild - build recipe. http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/build/ - build directory (patches, icons etc.) http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/pkg64/current/chromium-ungoogled-95.0.4638.69-x86_64-1alien.lst - ready package contents (version at the moment).

mpaunovic commented 2 years ago

ping @braewoods

Hey man, it's been three months, no word from you. Hope you're doing alright.

Any progress?

a-kriya commented 2 years ago

Steps outlined in https://github.com/ungoogled-software/ungoogled-chromium-debian/issues/266#issuecomment-980445614 are a workaround, and it's been working well for me. Just get the latest files from /Eloston/ungoogled-chromium-binaries/releases instead.

JamesClarke7283 commented 2 years ago

I have the same issue on Ubuntu Focal. Any pointers on how to downgrade?

I would advise against that for any web browser, downgrading an already 18+ month out of date browser(Chromium 94) is quite dangerous.

Browsers are one of the most targeted and sensitive software you have, because if JavaScript is enabled then its basically running code from the web on your computer, it has a sandbox, but its not full-proof and extended use of outdated browsers are likely to lead to security issues.

See issue #291 for an example. Likely there are other high impact/low effort vulns as they get reported often in browsers/web engines.

If this is for testing purposes only to work out how to fix it, then this is not likely to be high risk.

Perhaps try building from source from a recent, stable release tag, or try using an up-to-date Flatpak or AppImage of it, might solve this issue for you.

ghost commented 1 year ago

Issue no longer reproducible on latest version.