Auto-connect request for gtk-common-themes related content snaps for vivaldi

[volca]

Hi,

during testing it was revealed that we need to connect to gtk-common-themes to fix various issues (notably mouse cursor theme/size not being aligned with host system).

We’ve fixed that in snap rev. 40 - locally the package fixes the problem, but installed from the store I see it does not autoconnect to these:

content                          vivaldi:gtk-3-themes              -                                       -
content                          vivaldi:icon-themes               -                                       -
content                          vivaldi:sound-themes              -                                       -

whereas, for locally installed file, those are connected:

content[gtk-3-themes]            vivaldi:gtk-3-themes              gtk-common-themes:gtk-3-themes          -
content[icon-themes]             vivaldi:icon-themes               gtk-common-themes:icon-themes           -
content[sound-themes]            vivaldi:sound-themes              gtk-common-themes:sound-themes          -

I presume (reading other discussions in this forum) that this is a server side fix - so we are kindly requesting for the change here - I presume this may be related to the previous issues with ffmpeg autoconnect.

Thank you

Filip

[ruario]

Slightly rudely pinging @alexmurray and @jslarraz since they have so kindly assisted us with similar things in the past.

Automatic connection request for vivaldi : chromium-ffmpeg-115541

Hi, we’re in the process of preparing a release of new version of vivaldi and would like to request automatic connection for chromium-ffmpeg-115541 The command fixing our situation is: snap connect vivaldi:chromium-ffmpeg-115541 chromium-ffmpeg:chromium-ffmpeg-115541 We’ve previously got granted the connection for chromium-ffmpeg-115016 Is the process here to ask again for automatic connection every time a name change happens? Every major revision of chromium is to be expected to have a new…

Failing auto-connect to gnome-42-2204

Hi, our current package does not make automatic connection to gnome-42-2204 and due to that it’s not possible to run it because destop-launch is missing: Content snap command-chain for /snap/vivaldi/3/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected This is fixed by connecting to gnome-42-2204 by hand, but that should not be necessary (that should auto-connect, we’re using gnome extension in that snap package) I don’t think this is fixable on my side, from what…

[ruario]

I figured I should expand on the problem here with a demo

1. In Gnome set a large cursor Gnome Accessibility Settings

2. Note that apps now show this
3. Install Vivaldi from snap package
4. Launch Vivaldi and hover the cursor/pointer over the app

Expected result: It should use the custom, large cursor

---

You actually don’t see the custom cursor in Vivaldi once it is contained by snap. Here is a short video using the same build. The upper Vivaldi window is using snap, the lower is uncontained

[ruario]

Any update on this? We finally made the announcement about Vivaldi on snap and pushed it live.

https://vivaldi.com/blog/vivaldi-embraces-snap/

No user has commented on this issue yet but I figure it is only an amount of time before it is noticed. FWIW, other Chromium browsers in the store appear to have this.

[alexmurray]

Apologies for the delay in reviewing this request - since there is a global auto-connect declaration in place for these interfaces this is uncontroversial, as such I have gone ahead and granted it now. Please let me know if there are any issues.

[ruario]

That seems to work nicely, thanks!