[Bug]: AppImage integration with gnome launcher broken
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- Mezza giornata
- Idoneità per principianti
- 45/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- linux
- Ambito
- desktop
Direzione di ricerca
Start in apps/desktop, looking for the code that writes the AppImage's Linux .desktop entry at launch, and check the NoDisplay and StartupWMClass values it sets. The linked comment on issue 27257 describes the manual fix that works with the .deb build. Done means a generated entry with NoDisplay=false and StartupWMClass=com.t3tools.T3Code that survives relaunching the AppImage, verified on GNOME.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
When installing t3 code via .AppImage in gnome (Ubuntu 26.10 and 26.04 tested in this case), it doesn't integrate with gnome activities overview launcher, like it is not available to launch/switch in there via the activities launcher.
Even if you manually edit the .desktop file to make it available, every launch of the app overwrites the .desktop with no activities launcher integration.
This makes using t3 code inconvenient to use via the .AppImage in gnome as the activities launcher is the main way in gnome to launch/switch to applications.
Steps to reproduce in gnome (ubuntu 26.10 and 26.04)
- Download the .AppImage
- Change the permissions of the .AppImage for it to be launched
chmod +x T3-Code-0.1.9-x86_64.AppImage - Launch the .AppImage manually via the files app or terminal
- No integration with the activities overview launcher, you can't launch or switch to t3 code with it.
The fix would be that when the .AppImage creates the .desktop files, it sets NoDisplay=false and adds StartupWMClass=com.t3tools.T3Code.
- Current .desktop the .AppImage creates
[Desktop Entry]
Type=Application
Name=T3 Code (Beta)
Exec=/home/danielc/Applications/T3-Code-0.1.9-x86_64.AppImage %U
Icon=/home/danielc/.local/share/icons/com.t3tools.T3Code.desktop.png
Terminal=false
NoDisplay=true
StartupNotify=false
MimeType=x-scheme-handler/t3code;
- .desktop fix
[Desktop Entry]
Type=Application
Name=T3 Code (Beta)
Exec=/home/danielc/Applications/T3-Code-0.1.9-x86_64.AppImage %U
Icon=/home/danielc/.local/share/icons/com.t3tools.T3Code.desktop.png
Terminal=false
NoDisplay=false
StartupNotify=false
MimeType=x-scheme-handler/t3code;
StartupWMClass=com.t3tools.T3Code
The main fixes are this
NoDisplay=false
StartupWMClass=com.t3tools.T3Code
The NoDisplay=false allows launcher integration and StartupWMClass=com.t3tools.T3Code allows switching to the app via the launcher when the app is open.
The path /home/danielc is for my system, this is different for every installation home folder.
Expected behavior
- Download the .AppImage
- Change the permissions of the .AppImage for it to be launched
chmod +x T3-Code-0.1.9-x86_64.AppImage - Launch the .AppImage manually via the files app or terminal
- Full integration with the activities overview launcher.
- When t3 code closed, launch the activities launcher, search for t3 code to launch it.
- When t3 code already open but other app is in focus, launch the activities launcher, search for t3 code to switch to it.
Actual behavior
- Download the .AppImage
- Change the permissions of the .AppImage for it to be launched
chmod +x T3-Code-0.1.9-x86_64.AppImage - Launch the .AppImage manually via the files app or terminal
- No integration with the activities overview launcher, you can't launch or switch to t3 code with it.
Impact
Blocks work completely
Version or commit
No response
Environment
Ubuntu 26.10 (also tested 26.04 with the same result)
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
Even if you manually edit the .desktop file to make it available, every launch of the app overwrites the .desktop with no activities launcher integration, so in regards of the .AppImage there is no workaround.
Install t3 code with the .deb and apply the one shot fix in here https://github.com/pingdotgg/t3code/issues/27257#event-35822844264
The caveat of using the .deb is that to update you need to enter your sudo password in t3 code.
- Lingua principale
- TypeScript
- Stelle
- 24.8k
- Fork
- 6.4k
- Merge medio
- 59m
- PR unite (30g)
- 418
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di pingdotgg/t3code
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
via-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 Mezza giornata Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Question card options show LaTeX as raw source, though the question text renders itForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Settings inheritance popover shows raw slugs for branch naming, default permissions and response streamingForse già presa @juliusmarminge l’ha presa 1 giorno fa. Apertavouch:denounced
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di pingdotgg/t3code
Issue simili
-
bug platform:mobile root-cause:found
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
openchamber/openchamber#6926 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
push-based/user-flow#356 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
Cygnux-Labs/Tracekit#827 ·
I maintainer di solito rispondono entro 1 giorno
-
www build: a refused import shows only "ENOENT scandir <outDir>", never the build-audience errorApertakind:defect
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 91/100
I maintainer di solito rispondono entro 1 giorno
-
type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
nightgauge/nightgauge#3266 ·
I maintainer di solito rispondono entro 1 giorno