[GH-ISSUE #3593] Some errors in Telegram #2252

Closed
opened 2026-05-05 08:56:44 -06:00 by gitea-mirror · 5 comments
Owner

Originally created by @svc88 on GitHub (Aug 17, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3593

There are some errors when running Telegram. I dont see any significant difference, but only want to question the errors..

firejail /opt/Telegram/Telegram

Reading profile /usr/local/etc/firejail/Telegram.profile
Reading profile /usr/local/etc/firejail/telegram.profile
Reading profile /usr/local/etc/firejail/disable-common.inc
Reading profile /usr/local/etc/firejail/disable-devel.inc
Reading profile /usr/local/etc/firejail/disable-exec.inc
Reading profile /usr/local/etc/firejail/disable-interpreters.inc
Reading profile /usr/local/etc/firejail/disable-programs.inc
Parent pid 23981, child pid 23982
Warning: cleaning all supplementary groups
Child process initialized in 114.95 ms
The databases in [/home/test/.local/share/applications/] could not be updated.
error: : cannot open
error: : cannot open
error: : cannot open

Specifically the last 4 lines.

firejail version 0.9.62
Xubuntu 18.04
Telegram binary version: v 2.2.0

Originally created by @svc88 on GitHub (Aug 17, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3593 There are some errors when running Telegram. I dont see any significant difference, but only want to question the errors.. firejail /opt/Telegram/Telegram ``` Reading profile /usr/local/etc/firejail/Telegram.profile Reading profile /usr/local/etc/firejail/telegram.profile Reading profile /usr/local/etc/firejail/disable-common.inc Reading profile /usr/local/etc/firejail/disable-devel.inc Reading profile /usr/local/etc/firejail/disable-exec.inc Reading profile /usr/local/etc/firejail/disable-interpreters.inc Reading profile /usr/local/etc/firejail/disable-programs.inc Parent pid 23981, child pid 23982 Warning: cleaning all supplementary groups Child process initialized in 114.95 ms The databases in [/home/test/.local/share/applications/] could not be updated. error: : cannot open error: : cannot open error: : cannot open ``` Specifically the last 4 lines. firejail version 0.9.62 Xubuntu 18.04 Telegram binary version: v 2.2.0
Author
Owner

@bbhtt commented on GitHub (Aug 18, 2020):

I dont see any significant difference, but only want to question the errors..

Does telegram not open under firejail or do you want to know what the errors are about?

Also are you using the tarball?

<!-- gh-comment-id:675232924 --> @bbhtt commented on GitHub (Aug 18, 2020): > I dont see any significant difference, but only want to question the errors.. Does telegram not open under firejail or do you want to know what the errors are about? Also are you using the tarball?
Author
Owner

@svc88 commented on GitHub (Aug 18, 2020):

@kortewegdevries

It does open, it works fine so far. I am just questioning the errors in the last 4 lines

I am using the binary here

<!-- gh-comment-id:675398836 --> @svc88 commented on GitHub (Aug 18, 2020): @kortewegdevries It does open, it works fine so far. I am just questioning the errors in the last 4 lines I am using the binary [here](https://github.com/telegramdesktop/tdesktop/releases/download/v2.2.0/tsetup.2.2.0.tar.xz)
Author
Owner

@bbhtt commented on GitHub (Aug 18, 2020):

It does open, it works fine so far. I am just questioning the errors in the last 4 lines

Probably trying to update or create a desktop entry because that directory is read-only; try adding read-write ${HOME}/.local/share/applications to your profile to see if it fixes.Likely it's harmless warning...

<!-- gh-comment-id:675512292 --> @bbhtt commented on GitHub (Aug 18, 2020): > It does open, it works fine so far. I am just questioning the errors in the last 4 lines Probably trying to update or create a desktop entry because that directory is `read-only`; try adding `read-write ${HOME}/.local/share/applications` to your profile to see if it fixes.Likely it's harmless warning...
Author
Owner

@chiraag-nataraj commented on GitHub (Aug 18, 2020):

For what it's worth, I don't get any such errors when I use the telegram-desktop package from Debian with the Telegram profile here.

Edit: I stand corrected. I looked at my logs and get similar errors. I just ignore them because they don't affect Telegram's functionality.

<!-- gh-comment-id:675711403 --> @chiraag-nataraj commented on GitHub (Aug 18, 2020): For what it's worth, I don't get any such errors when I use the `telegram-desktop` package from Debian with the Telegram profile [here](https://github.com/chiraag-nataraj/firejail-profiles). Edit: I stand corrected. I looked at my logs and get similar errors. I just ignore them because they don't affect Telegram's functionality.
Author
Owner

@svc88 commented on GitHub (Aug 21, 2020):

@kortewegdevries i put that line in telegram.profile just after the line include telegram.local
Seems this The databases in [/home/test/.local/share/applications/] could not be updated. disappeared but i still get these after each run:

error: : cannot open
error: : cannot open
error: : cannot open

Although could be harmless warnings, i was wondering whats causing them.
However as @chiraag-nataraj mentioned, if they dont affect functionality then its fine. thanks

<!-- gh-comment-id:678125246 --> @svc88 commented on GitHub (Aug 21, 2020): @kortewegdevries i put that line in telegram.profile just after the line `include telegram.local` Seems this `The databases in [/home/test/.local/share/applications/] could not be updated.` disappeared but i still get these after each run: ``` error: : cannot open error: : cannot open error: : cannot open ``` Although could be harmless warnings, i was wondering whats causing them. However as @chiraag-nataraj mentioned, if they dont affect functionality then its fine. thanks
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2252
No description provided.