To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.
- name: collabora-office
- description: Desktop edition of Collabora Office — a local Qt6 desktop wrapper around the Collabora Online engine. Provides Writer, Calc and Impress editing with a modern, browser-style UI, working with local files on the user’s device. No cloud required
- snapcraft: online.mirror/snap/snapcraft.yaml at main · CollaboraOnline/online.mirror · GitHub
- upstream: GitHub - CollaboraOnline/online.mirror: Read-only Collabora Office/Collabora Online monorepo - no pull requests (use gerrit instead https://gerrit.colaboraoffice.com/) · GitHub
- upstream-relation: The snap is published by Collabora Productivity Ltd, the same company that develops and maintains the upstream Collabora Online / Collabora Office project. The DBus name com.collaboraoffice.Office is the reverse-DNS of collaboraoffice_dot_com, owned by the same publisher; there is no risk of name squatting.
- interfaces:
- dbus-collabora-office:
- request-type: auto-connection
- reasoning:
coda-qt(the desktop wrapper shipped in this snap) registers the session-bus namecom.collaboraoffice.Officeat startup to provide single-instance routing. When the user opens a document while the app is already running, the second process forwardsopenFiles/openNewDocument/activatecalls over DBus to the existing instance and exits, so the document opens in the running window instead of spawning a duplicate process (each new instance brings up its own coolwsd backend, ~600 MB RAM). Without auto-connection the AppArmor profile blocks the name ownership,DBusService::registerServicefails on startup under strict confinement, and the app aborts. Auto-connection is needed so users get working single-instance behaviour out of the box withoutsnap connect …ceremony.
- dbus-collabora-office: