[GH-ISSUE #606] telegram 0.9.56 run failure under firejail/commit `74a9ffe66e` #421

New issue

Closed

opened 2026-05-05 05:49:48 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:49:48 -06:00

Owner

Originally created by @aa3Eethi on GitHub (Jun 30, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/606

According to your comment in the issue ("Fixed! It got broken yesterday, try it now.") I removed firejail package from my system, then cloned firejail git repo, configure/make/install, then again (the same?) error as in closed issue (https://github.com/netblue30/firejail/issues/605):
"[2016.06.30 09:54:29] Launched version: 9056, alpha: [FALSE], beta: 0, debug mode: [FALSE], test dc: [FALSE]
[2016.06.30 09:54:29] Executable dir: /home/user/apps/Telegram/, name: Telegram
[2016.06.30 09:54:29] Initial working dir: /home/user/wc/firejail/
[2016.06.30 09:54:29] Working dir: /home/user/.TelegramDesktop/
[2016.06.30 09:54:29] Arguments: "/home/user/apps/Telegram/Telegram"
[2016.06.30 09:54:29] FATAL: Could not open '/home/user/.TelegramDesktop/log_startXX.txt' for writing log!
[2016.06.30 09:54:29] Connecting local socket to /tmp/709d9dfbb6882d21108f5de26d3a408d-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2016.06.30 09:54:29] This is the only instance of Telegram, starting server and app..."

Any ideas how to fix for real?

Originally created by @aa3Eethi on GitHub (Jun 30, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/606 According to your comment in the issue ("Fixed! It got broken yesterday, try it now.") I removed firejail package from my system, then cloned firejail git repo, configure/make/install, then again (the same?) error as in closed issue (https://github.com/netblue30/firejail/issues/605): "[2016.06.30 09:54:29] Launched version: 9056, alpha: [FALSE], beta: 0, debug mode: [FALSE], test dc: [FALSE] [2016.06.30 09:54:29] Executable dir: /home/user/apps/Telegram/, name: Telegram [2016.06.30 09:54:29] Initial working dir: /home/user/wc/firejail/ [2016.06.30 09:54:29] Working dir: /home/user/.TelegramDesktop/ [2016.06.30 09:54:29] Arguments: "/home/user/apps/Telegram/Telegram" [2016.06.30 09:54:29] FATAL: Could not open '/home/user/.TelegramDesktop/log_startXX.txt' for writing log! [2016.06.30 09:54:29] Connecting local socket to /tmp/709d9dfbb6882d21108f5de26d3a408d-{87A94AB0-E370-4cde-98D3-ACC110C5967D}... [2016.06.30 09:54:29] This is the only instance of Telegram, starting server and app..." Any ideas how to fix for real?

gitea-mirror

2026-05-05 05:49:48 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:49:55 -06:00

Author

Owner

@netblue30 commented on GitHub (Jun 30, 2016):

Sorry, I didn't realize the original bug was against 0.9.40. I'll give it a try.

@netblue30 commented on GitHub (Jun 30, 2016): Sorry, I didn't realize the original bug was against 0.9.40. I'll give it a try.

gitea-mirror commented

2026-05-05 05:49:58 -06:00

Author

Owner

@netblue30 commented on GitHub (Jul 3, 2016):

The problem was in the profile file. It was whitelisting /home directory removing Telegram executable from the directory. I have a fix in, you can give it a try. If you still have problems, please let me know.

@netblue30 commented on GitHub (Jul 3, 2016): The problem was in the profile file. It was whitelisting /home directory removing Telegram executable from the directory. I have a fix in, you can give it a try. If you still have problems, please let me know.

gitea-mirror referenced this issue

2026-05-05 10:04:47 -06:00

[PR #428] [MERGED] Profile cleanup #3620

gitea-mirror referenced this issue

2026-05-05 10:09:36 -06:00

[PR #1198] [MERGED] Okular and Gwenview profiles, Baloo blacklist #3878