Since it’s an upstream bug and both the browser and the extension are having issues, we probably will not fix it. It would be ideal if there was a way to install extensions, but it was between this and Falkon. ug-chromium is still going to support more pages generally and we offer other browsers.
1 Like
I’m looking forward to the Ladybird browser. It can’t come soon enough, IMHO.
1 Like
The unzipping problem doesn’t happen in upstream. It’s only happening on OM’s build.
That is not correct. Please read your own support request:
That bug that people are talking about upstream is a separate issue, which is specific to the extension and gives that pink “Item Currently Unavailable” error on the Chrome web store. The error I reported has nothing to do with that pink error, and instead shows “Could not unzip extension,” even when manually installing .crx files.
This can easily be tested by downloading the Appimage or “Portable Linux” version, and you will not encounter the unzip error there.
https://ungoogled-software.github.io/ungoogled-chromium-binaries/
1 Like
“If you also attempt to sideload extensions it has issues with unpacking them. ug-chromium also seems to have a lot of “Help Wanted” tags in their Issues. It might be time to investigate using Cromite instead. Their binary works out of the box with extensions.”
99% of the people will want to use the web store they put on the first run and it’s not working properly. If it works anywhere else, then it’s an older version or they backported the fix. Blocking access to Google web store and servers is by design. Hence the “unGoogled” part.
There was also a workaround presented on your support request if you read just a little further:
I have put it here for your convenience:
" Not ideal, but if you want to work around this, create a new directory that your desired extension can be extracted to, download the extension to the directory, turn on Developer Mode, go into a terminal and cd to the extension directory you made, use unzip to extract the crx file, and open the Extension Manager and choose Load Unpacked. It will then let you select the directory that your downloaded extension is in and allow the extension to be installed. I have tested this with uBlock Origin, Bitwarden, and chromium-web-store. Keep in mind, the aforementioned Issue about the store not updating anymore may still apply."
So, there is a workaround, we have other browsers, and you are free to use AppImage if that is helpful for you as is anyone else. We will be looking into a better default option where their Issues section isn’t full of “Help Wanted”. We are already discussing that.
Sigh. I don’t know if my point is coming across correctly or not.
My point is that there are two separate, albeit similar issues here:
- The pink error on the Chrome web store exists in all versions of Ungoogled Chromium while using the Chrome Web Store Extension. This can usually be worked around by simply refreshing the page.
- The unzip error, which exists only in OM’s build of Ungoogled Chromium and has never existed in any other version. I’ve been using Ungoogled Chromium for a long time and would’ve run into it.
Again, this is an actual bug and has nothing to do with Google stuff being blocked by the browser.
Unzipping a local .crx file would not have anything to do with a server being blocked.
I was only hoping the second issue could be investigated, instead of being dismissed outright.
1 Like
After searching through the Githubs of both versions of Ungoogled Chromium, I noticed that OM’s version has some patches related to minizip.
I cannot find any evidence of these patches or similar ones existing in the upstream version.
This part in particular seems interesting:
-#include "third_party/zlib/contrib/minizip/ioapi.h"
-#include "third_party/zlib/contrib/minizip/unzip.h"
+#include <minizip/ioapi.h>
+#include <minizip/unzip.h>
-#include "third_party/zlib/contrib/minizip/ioapi.h"
+#include <minizip/ioapi.h>
-#include "third_party/zlib/contrib/minizip/ioapi.h"
+#include <minizip/ioapi.h>
-#include "third_party/zlib/contrib/minizip/ioapi.h"
+#include <minizip/ioapi.h>
-#include "third_party/zlib/contrib/minizip/ioapi.h"
+#include <minizip/ioapi.h>
It seems like it’s meant to use the version of minizip on the system instead of the one included with regular Chromium. Perhaps it’s not finding what it needs on the system doing the building or something…
I also find it interesting that the spec file has this line:
BuildRequires: pkgconfig(minizip)
I would expect it to be “minizip-ng” instead of “minizip”, because I see a “lib64minizip-ng” in the repos, but not a “lib64minizip”, but I could be wrong.
1 Like
It is being looked at.
1 Like
Yes, I experienced this yesterday when trying to use Chromium for a few things (I hadn’t noticed because I am mostly FF). Meaning, you cannot install even CRX files.
It is normal that Chromium will not be able to install direct from the store.
I also don’t think “hey, just install Brave” is a good solution if you’re specifically talking about Ungoogled Chromium and worse, “the default browser”.
Installing the Flatpak version was the solution for me.
1 Like
Yes, the (in)famous “default whatsoever”…
If you ask 100 persons what should be “the default foo”, you will get 101 different answers.
Sad but true:
- You cannot please everyone
- Whatever you do, you did wrong
No way.
1 Like
Ah, sorry. I may have been misunderstood.
I meant to say that if somebody complains about a bug in a default application, the official recommendation should not be “hey, go install Y instead of X”.
I meant to say the default should work as expected (in this case installing CRX by hand, which it does not allow).
That’s all 
I am perfectly happy with any default browser. Konqueror or Epiphany even.
1 Like
@krzldzr 
Anyway the issue or supposed issue is being investigating.
If we’ll find there is anything we can do to ease the user experience be sure that we’ll be happy to do.
This will be my last post.
After joining the Matrix chat and reading what they were saying about this thread, I am really surprised at the hostility.
I thought this was going to be a friendly community of nerds, but maybe I was wrong.
It’s really bizarre that reporting a bug is being misinterpreted as complaining or demanding. I thought I was being helpful by reporting feedback on whether different builds or distros have the same bug and such, but I guess that type of feedback isn’t welcome. I would’ve thought it would be helpful in narrowing down the root cause.
If you don’t have the time or desire to fix a bug, that’s fine. I understand that resources are limited. But just say that outright. Don’t be so dismissive if someone challenges the accurracy of what you’re saying.
My only goal in being so persistent in this thread was for it to simply be acknowledged that the zip issue was indeed separate from the other extension issues and not an upstream problem, which is objectively true. That’s it. At no point did I demand for it to be fixed. If you think it’s not worth fixing, that’s totally fine. I couldn’t really care less. I only care about accurate information being presented. That’s all. What you do that info is totally up to you.
@silentJET85
A chat is a chat. Real time comments may also be misinterpreted or written in a person’s “bad moment”.
otoh:
Did you join the room and had any conversation there (genuine question as I cannot read everything) on the subject?
Also probably worth notice that we are very busy with the upcoming OMLx 6.0 release and we have priorities to look after.
The developers of course do their best to fix the issues. Bug reports are welcome.
I was there during the discussion between the devs as to what to do with the program. You didn’t speak up. I am not a dev, but if it were up to me, there would be no default browser. The welcome app would offer a choice of browsers. If our install of the ungoogled chromium is not good enough, go install from the dev’s site. It’s not hard.
By the way, if the devs blow off a little steam in the dev chat room, I have no problem with it. At the place I worked last, we would tell each other, don’t loose it out there. Come back in the office and vent.
Sad to read that, not gonna point somebody at fault or not, just hope there is a way for you to not leave us that way.