mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3495] Tutanota-desktop difficult to integrate #2197
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2197
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CocoR55 on GitHub (Jul 5, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3495
Bonjour,
Tutanota works with Appimage in a sandbox under Firejail. To launch this application, a command is used in the terminal.
$ firejail --profile=tutanota-desktop-linux.AppImage.profile ./tutanota-desktop-linux.AppImage --appimage-extract-and-run.Now the difficulty is to create a launch or shortcut on both desktop or in the menu. Indeed, the command for desktop integration
$ sudo firecfgremains without effect because if I understood well, the applicationtutanota-desktop-linux.AppImageis not mentioned in the file/usr/lib/firejail/firecfg.config.I tried to create launchers on the desktop but it fails. The launcher keeps trying and fails with the following error message:
./tutanota-desktop-linux.AppImageno such file.I tried to create a launcher from the directory of the file to get around a possible lack of authorization, without more success.
If you have any ideas, they are welcome.
Regards,
CocoR55
@ghost commented on GitHub (Jul 5, 2020):
@CocoR55 Based on #3485 you need to create ${HOME}/.local/share/applications/tutanota.desktop with the below content. For this example to work you need to confirm the AppImage is in /home/michaou/Tuta/Tutanota-desktop-linux.AppImage. If not, adjust the path in the 'Exec=...' line. Furthermore, I don't know if Tutanota comes with an icon of its own, so the 'Icon=/home/michaou/Tuta/Tutanota-desktop-linux.png' line probably needs changing and is just an example.
@ghost commented on GitHub (Jul 5, 2020):
@CocoR55 If this all works for you, would you be so kind to close #3485 please? Just so we can keep our issue-tracker a bit organized... Of course, do this only if you're tutanota-desktop appimage is now fully operational as expected.
@CocoR55 commented on GitHub (Jul 7, 2020):
@glitsj16 First, #3485 is close. Second, I did that you proposed above. Sorry, that do not work. Nevertheless,
I used your command line to insert into a launcher on the desktop and it works.
I still have a problem. I don't get it. I use the Tutanota-Desktop as a launcher. The tutanota site looks dark or light. I chose the dark look. Until then, I think he had it in mind. That's a good thing. For the last few days, it's been clear to start with. I can change the appearance, but nothing can change it at startup. Every time I launch the application to open the tutanota site, it always looks clear.
I'm thinking that maybe you have a little idea where the appearance would be saved, in some files.
Do you have an idea how to keep the same appearance at the beginning?
Regards,
CocoR55
@CocoR55 commented on GitHub (Jul 8, 2020):
Correction; It all depends on how I exit the application. If I click on "disconnect", no problem, the appearance remains, at reboot, in my case, dark. In all other ways of quitting, the appearance becomes clear on reboot.
It shows up quite easily. Just activate the terminal in the launcher properties with notpadd, for example. If you leave the site by clicking on "disconnect", the terminal window closes. Otherwise it remains open and still active.