fix(gnome): GNOME Shell 50 indicator compat + daemon D-Bus activation - #55
Merged
Merged
Conversation
Add a D-Bus service file so the daemon (lnxdrived) auto-starts on first connect from the panel/CLI (bus name == app-id, exported+activated by Flatpak), and install it from the manifest. Also refine the Preferences launcher: user-facing Name=LNXDrive, product GenericName/Comment, and Network;FileTransfer categories instead of Settings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The indicator declared shell-version up to 49, so GNOME Shell 50.3 marked it OUT OF DATE and refused to load it — the panel icon never appeared even when installed and enabled. Add "50" to the shell-version array. Documents the diagnosis in AILOG-2026-07-03-002 and registers FU-013 (extension absent from the Meson/package build — installed manually) and FU-014 (settings-schema declared without a compiled gschema) in the follow-ups registry. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Qué y por qué
El indicador de LNXDrive en el panel de GNOME no aparecía tras reiniciar la sesión. El diagnóstico descartó el servicio (el daemon
lnxdrivedarranca bien por activación D-Bus y expone sus 9 interfaces en el bus de sesión) y localizó dos causas:metadata.jsonde la extensión declarabashell-versionsolo hasta la49→ Shell la marcabaOUT OF DATEy se negaba a cargarla, aun estando instalada y habilitada. Fix: añadir"50"al array.com.strangedaystech.LNXDrive.servicey su instalación desde el manifiesto Flatpak, para que el daemon auto-arranque al primer connect del panel/CLI. También se refina el.desktopdel lanzador (Name/GenericName/Comment de producto, categoríasNetwork;FileTransfer).Commits
feat(packaging): activación D-Bus del daemon + metadata del lanzador.fix(gnome): compatibilidad con GNOME Shell 50 en el indicador + AILOG + follow-ups.Verificación
ACTIVEen GNOME Shell 50.3; el ícono aparece en el panel (verificado en vivo por el operador)./com/strangedaystech/LNXDrive.straymark validate: 0 errores.Seguimiento (fuera de alcance de este PR)
~/.local/share/gnome-shell/extensions/. Formalizar un target de instalación (una instalación limpia queda sin indicador hasta entonces).metadata.jsondeclarasettings-schemasin gschema compilado en el repo — romperíaprefs.jsal abrir las preferencias de la extensión.Documentado en
AILOG-2026-07-03-002y registrado en el follow-ups backlog.🤖 Generated with Claude Code