Global auto-connect request: qt-style-kvantum:kvantum

Kyuyrii · October 10, 2025, 2:54pm

name: qt-style-kvantum
description: A content Snap to make it possible to use Kvantum in Snap apps.
snapcraft: Snap-qt-style-kvantum/snapcraft.yaml at main · Kyuyrii/Snap-qt-style-kvantum · GitHub
upstream: GitHub - tsujan/Kvantum: A Linux SVG-based theme engine for Qt and KDE
upstream-relation: I just made the Snap
interfaces:
- <interface-name>: qt-style-kvantum:kvantum
  - request-type: auto-connection
  - reasoning: This is necessary so that Snap apps that add the use of qt-style-kvantum can connect without needing a command. I know that Snaps published by the same person connect automatically, but if someone else wants to use qt-style-kvantum, they would need their users to use a command to connect to qt-style-kvantum. I apologize if the request is incorrect.

store-requests-bot · October 10, 2025, 2:54pm

This request has been added to the queue for review by the @reviewers team.

yomonokio · October 15, 2025, 8:15am

While reviewing your snapcraft.yaml file, we noticed that the slot you’ve defined requests read access to the root directory (/). Could you please clarify why such broad access is required?

Kyuyrii · October 16, 2025, 12:46am

I’m still testing this Snap, so snapcraft.yaml will look different later.

I just left it this way to make it easier to test for now.

Kyuyrii · October 16, 2025, 10:11am

I think I understand your question now. If I’m not mistaken, this reading is about the Snap content files, not the system root.

Tweaking it could end up preventing me from displaying the files to the Snap that’s consuming qt-style-kvantum.

gaming-graphics-core22 also uses only a ``/``` to display its files to the Snap that will consume the libraries.

Kyuyrii · October 16, 2025, 10:36am

qt-style-kvantum is a Snap that I hope is only temporary.

I created it so I could try using Kvantum and the lxqt-qtplugin to see how they would work within Snap, and from what I’ve tested, they work surprisingly well.

It’s an example of what can be done with kf6-core24/kf6-core22, which is the content Snap used to create QT6 Snap apps.

Currently, kf6-core only supports the GTK3 and KDE platform themes, and only adds the QT Breeze and Oxygen styles, which, in addition to limiting customization, also significantly worsens the experience with Snap apps in LXQT.

Since Snap has surprisingly good support for GTK themes, icon themes, and cursor themes, I imagine improving integration with QT, LXQT, and Kvantum makes a lot of sense.

Especially considering that flavors could use these improvements to deliver a better experience to their users.

For example, if a distro like Xubuntu or Ubuntu Budgie uses the GTK Arc theme, they could also use the Kvantum KvArcDark theme, which would create a design consistency that’s very rare.

0xnishit · October 21, 2025, 9:32am

Thanks for the explanation @Kyuyrii , We were expecting a specific lib path instead of /, but I have seen few snaps which are using / widely to get info about libs and then read those libs. so it should be fine

+1 from my end for this content interface to this snap. (#voteFor)

yomonokio · October 22, 2025, 9:36am

Hi @Kyuyrii!

+1 (#voteFor) from my side, too! +2 votes for, 0 votes against, granting content interface auto-connect to the qt-style-kvantum snap. This is now live!

store-requests-bot · October 22, 2025, 9:37am

Voting period has ended. This request is approved with 2 votes for and 0 votes against.