Ferenc-
commented
2 years ago The last time I have seen that ( #29 ), it appeard to be an upstream issue.
So it is advised to check if the problem happens with the normal `org.chromium.Chromium˙ as well.
Closed ghost closed 2 years ago
Ferenc-
commented
2 years ago The last time I have seen that ( #29 ), it appeard to be an upstream issue.
So it is advised to check if the problem happens with the normal `org.chromium.Chromium˙ as well.
ghost
commented
2 years ago It does. I will report upstream
molny
commented
2 years ago I can also approve this issue. ENV: Flatpak 1.12.4, ungoogled-chromium 98.0.4758.80, KDE Neon on kernel 5.13.0-28-generic
rany2
commented
2 years ago Is this still relevant?
ghost
commented
2 years ago Probably not
galkinvv
commented
2 years ago I fixed this problem on ubuntu 20.04 by updating xdg-desktop-portal to version 1.8.1-1~flatpak1~20.04
see https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1951685 for details
gollum-z
commented
1 year ago Hi,
the problem occurs again with Flatpak 1.14.4
Installed version com.github.Eloston.UngoogledChromium 114.0.5735.106
OS: Ubuntu 20.04.6 LTS (Focal Fossa)
Desktop: Gnome 3.36.9
I will report this on https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1951685
[edit]
I updated xdg-desktop-portal from version 1.6.0-1ubuntu2 to version 1.14.3-1~flatpak1~20.04on my machine
and now everything works fine!
:-) [/edit]
after a few seconds (up to a minute) of having chromium open, every request fails with net::ERR_NO_SUPPORTED_PROXIES until I restart the browser. I don't have any proxy configs set up.
environment: Flatpak 1.11.3, ungoogled-chromium 97.0.4692.99, KDE Neon on kernel 5.11.0-46-generic