** Bug watch added: Mozilla Bugzilla #1868690
https://bugzilla.mozilla.org/show_bug.cgi?id=1868690
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome
** Changed in: firefox (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell
@slalomsk8er, I'm not disagreeing with snap's shortcomings, I'm just providing
alternatives for anyone who's run into such issues. There is now also the
option of getting stable builds in .deb form from the MozillaTeam
(https://wiki.ubuntu.com/MozillaTeam) PPA at
https://launchpad.net/~mozillate
Plasma Browser integration now kind of works with:
firefox 106.0.5-1 2067 latest/stable/… mozilla✓
xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1
but I had to manually set permission - following directions for
KeePassXC integration.
Steps:
sudo apt-get install flatpak
flatpak permission-set web
One can use the builds directly from Mozilla
https://www.mozilla.org/firefox/all/ but the onus is on the
user/sysadmin to keep it updated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.
Got it friends. Follow the way: Synaptic + gdebi (install) Get to
the "www.myminfin.be" Download the eID-software. Back to gdebi to
install the software. Then "sudo apt update" After that back to Synaptic
to install them all: beid-mozilla-extension beid-mozilla- webext
eid-archive eid-mw
Still no solution for the Belgian eid card!!! There is only one way out
as it is serious: Cange to Linux Mint which is withou snap or Zorin.
That's what I did. What else could I do? Have a nice day all of you.
--
You received this bug notification because you are a member of Desktop
Packages, wh
@paulstejskal Do you use the Zoom Snap? Please look here:
https://github.com/ogra1/zoom-snap/issues/111
** Bug watch added: github.com/ogra1/zoom-snap/issues #111
https://github.com/ogra1/zoom-snap/issues/111
--
You received this bug notification because you are a member of Desktop
Packages,
@paulstejskal I don't think the issue you are describing is caused by
the bug described in this bug report. You might need to file a separate
bug report or ask for help elsewhere.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-b
Is this scheduled to be fixed soon? My apologies if this may not be the
right bug but I use Firefox and cannot log into the Zoom app behind a
SSO login (as it must go to zoom.us). Firefox already has safeguards
about "are you sure you want to open this" and asks twice. It worked
fine in KUbuntu 21.
Similar problems exist with for example expressVPN (which recommends to
uninstall the snap version and install a ppa-version of firefox instead:
https://www.expressvpn.com/de/support/vpn-setup/app-for-linux/#software-
center) and with the video-download-helper extension
(https://www.downloadhelper.
Same issue here with KeepassXC native transport on Ubuntu 22.04 and
firefox. Worked flawless on 20.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] ch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plasma-browser-integration (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://
** Also affects: plasma-browser-integration (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-g
** Description changed:
(initially reported at https://forum.snapcraft.io/t/chrome-gnome-shell-
does-not-work-with-chromium-snap/3377)
See attached screenshot.
[Workaround]
- Use Extension manager to install gnome extensions
- https://flathub.org/apps/details/com.mattjakeman.Extensi
[Workaround]
Use Extension manager to install gnome extensions
https://flathub.org/apps/details/com.mattjakeman.ExtensionManager
** Description changed:
(initially reported at https://forum.snapcraft.io/t/chrome-gnome-shell-
does-not-work-with-chromium-snap/3377)
See attached screenshot
I can confirm that this issue is still present in Ubuntu 22.04.
Extensions can only be installed manually now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[
This bug is still there with 22.04 installed this morning. As I can't
install the deb package anymore this is really annoying.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/174
** Changed in: firefox (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension fail
** Bug watch added: github.com/woodruffw/ff2mpv/issues #80
https://github.com/woodruffw/ff2mpv/issues/80
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[sna
It seems 1Password is also affected for this bug. I don't understand
what happens behind, but 1Password also fails to communicate with
Firefox Snap. My original bug report:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964546
--
You received this bug notification because you are a membe
** Changed in: firefox
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension fails to dete
** Changed in: firefox
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension fails to detect nativ
** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #655
https://github.com/flatpak/xdg-desktop-portal/issues/655
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/
snap is cancer
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension fails to detect native host
connector
Status in Mozilla Fi
It seems, Belgium eID (Comment #36) uses PKCS#11, not native messaging:
https://github.com/Fedict/eid-mw/blob/master/plugins_tools/xpi/new-src/manifest.json
However the problem is essentially the same: native manifest.
Olivier filed a bug in Firefox bugzilla:
https://bugzilla.mozilla.org/1734371
"F
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1661935.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
*
Discussion to figure out a solution is continuing at
https://forum.snapcraft.io/t/native-messaging-support-in-strictly-
confined-browser-snaps/26849. Please refrain from "me too" or "+1"-like
comments (but valid use cases that weren't mentioned yet or suggestions
are welcome).
--
You received thi
> there will be no alternative in the Ubuntu repositories to do these
basic things in Belgium.
using epiphany (the GNOME browser) should work no?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.la
I'm quoting James Henstridge on a possible approach to tackle the
problem:
« The design of the native messaging system for extensions is something
that could theoretically fit into a confinement system like snapd or
flatpak. Instead of executing the native messaging server directly, the
browser co
And for future reference, here is Mozilla's documentation on native
messaging: https://developer.mozilla.org/en-US/docs/Mozilla/Add-
ons/WebExtensions/Native_messaging.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in U
Thanks for these useful data points Merlijn. That is certainly an
important use case that we want to continue supporting. I had a quick
look at both the github repository and the "Belgium eID" firefox
extension (https://addons.mozilla.org/en-US/firefox/addon/belgium-eid/),
and I can't find any refe
I want to make this a bit more clear:
Every single Belgian needs this functionality in order to do basic stuff
like:
* File their taxes
* Read communication from the government
* Check their medical history
* Register for a (covid) vaccine
* Rent stuff from the government
* etc.
It is vital that
For Ubuntu 20.04, I have also noticed that both snap installed Chromium
and Brave Web browsers fails to work with the gnome-shell-integration
extension.
In the case of Brave, this issue can be overcome by following their instruction
on installing the .deb versions of brave-browser and brave-keyri
Although GNOME Shell integration extension is running, native host
connector is not detected. Refer documentation for instructions about
installing connector.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
htt
Hi team, is there any news about this 3y old bug? It would be nice to
know if it is something that will be worked on or not even if the
timeline indicates towards not.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ub
** Bug watch added: github.com/keepassxreboot/keepassxc/issues #1598
https://github.com/keepassxreboot/keepassxc/issues/1598
** Also affects: chromium-browser via
https://github.com/keepassxreboot/keepassxc/issues/1598
Importance: Unknown
Status: Unknown
** Project changed: chromi
One suggestion discussed in https://forum.snapcraft.io/t/allow-classic-
confinement-for-postman-agent/19228 is to use a content interface to
allow third-party snaps to write to
~/snap/chromium/common/chromium/NativeMessagingHosts/. Whether it’s a
good idea from a security perspective is open for di
Download firefox from its website, just run it from it's unzipped
directory
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension
Any changes on this bug (since 2018)? Maybe at least workaround?
I confirm same problem on Focal 20.04 LTS with snap Opera (chrome based)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.
Nope, never mind gnome-tweaks. Removed Chromium snap and installed
Google Chrome. Problem goes away.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chro
Harrumph: not impressed. Was working fine this morning, then an update
landed me with the snap version.
Back to gnome-tweaks...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1
This "connector" issue is also presents on firefox snap v77.0b2 (64-bit)
Ubuntu 20.04 and has not addressed yet.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
@anonymouse67: see comments #2, #5, #6 and #7 in this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension fails to detect n
@osomon, could you point me to an existing forum post or start a new one
summarizing what accesses would be necessary to manage gnome shell
extensions? I couldn't find one searching, but if there's not one we
should open one to try and discuss with snapd architects. Thanks
--
You received this bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: goopg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kdeconnect (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.n
** Also affects: kdeconnect (Ubuntu)
Importance: Undecided
Status: New
** Also affects: goopg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
http
This also affects the browserpass extension for the pass
(passwordstore.org) password manager
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnom
This is still an issue on 20.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension fails to detect native host
connector
Sta
Hi! Any update on this please? This is an extremely frustrating issue
that makes me consider switching from Ubuntu to something else.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/b
I want to add this affects Firefox + the KeepassXC extension too. I agree that
NativeMessaging is kind of a crutch, but if there is no way to make this work
safely a snap interface needs to be implemented that applications from inside /
outside of snap can use. There is demand for this kind of i
(I think) It makes development easier, you don't have to build it for
every Ubuntu version in support, or any Linux OS, it contains specific
libraries you know won't cause issues with the app.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
KDE Connect is also affected by this. I'm wondering though, unable to
find the answer online, why was the transition to snap-based chromium
made?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.lau
2020-01-06 : https://forum.ubuntu-
fr.org/viewtopic.php?pid=22202596#p22202596
It seems still broken in not-yet-released ubuntu 20.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net
And from duplicate bug #1853835, the KeePassXC-Browser extension
(https://chrome.google.com/webstore/detail/keepassxc-
browser/oboonakemofpalcgghocfoadofidjkkk) doesn't work for the same
reason: https://github.com/keepassxreboot/keepassxc-browser/issues/405.
--
You received this bug notification
It's been reported that the GooPG extension doesn't work because it uses
native messaging (https://discourse.ubuntu.com/t/call-for-testing-
chromium-browser-deb-to-snap-transition/11179/207).
** Bug watch added: github.com/keepassxreboot/keepassxc-browser/issues #405
https://github.com/keepassx
Chromium is now incapable of managing extensions for Ubuntu's primary
desktop environment? This issue is tolerable only because Google Chrome
is not affected. Is Google somehow behind this apparent reluctance to
remedy the problem?
--
You received this bug notification because you are a member of
This bug is still present in Kubuntu 19.10. Poor Chromium...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension fails to detect
zebul666, please take time to read:
https://discourse.ubuntu.com/t/intent-to-provide-chromium-as-a-snap-only/5987
https://discourse.ubuntu.com/t/please-test-chromium-snap-as-a-replacement-for-the-deb/7978
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179
How and why that snap has been rolled out in 19.10 while we have less
feature with it ?
Note: I don't like snap.
This bug is another example why. Moreover nobody cares to fix this. If it is
even possible...
--
You received this bug notification because you are a member of Desktop
Packages, whic
Unlikely. There are a number of higher priority issues with the chromium
snap that we're focusing on now, and the plan to transition from the deb
to the snap in 19.10 still holds.
I know this isn't a proper fix, merely a workaround, but you can use
gnome-tweaks to manage your gnome-shell extension
This is really frustrating and 19.10 is coming up fast which I
understand will switch everyone over to snap based chromium making
extensions.gnome.org unusable for everyone. Any chance of switching back
to non-snap based chromium if this issue isn't resolved before then?
--
You received this bug
Also, the connector talks to the org.gnome.Shell.Extensions D-Bus API,
for which there doesn't exist a snapd interface, so one would need to be
written, and I'm pretty sure it wouldn't qualify for auto-connection
given the level of privilege it would expose (listing installed
extensions, install an
I've toyed with an unpacked example extension that talks to a native
host connector (a simple python script that listens to messages and
echoes all it receives).
This works with the following caveats:
- the connector has to be installed under
$SNAP_USER_DATA/.config/chromium/NativeMessagingHosts
chrome-gnome-shell wouldn't work like that unmodified, because the
connector has external dependencies (it's a python3 script that imports
GLib and Gio).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://
Is there any news about this bug?
To this day I still can't use plasma-browser-integration
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-s
Similar report for the Plasma/Browser Integration
(https://community.kde.org/Plasma/Browser_Integration):
https://forum.snapcraft.io/t/call-for-testing-
chromium-62-0-3202-62/2569/65.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromi
stracing the snap reveals that /usr/bin/chrome-gnome-shell cannot be
found in the context of the snap:
15760 access("/usr/bin/chrome-gnome-shell", F_OK) = -1 ENOENT (No such
file or directory)
This is not an apparmor denial. Inside the snap’s execution environment,
/usr/bin is in fact /snap/cor
70 matches
Mail list logo
