[GH-ISSUE #605] telegram run failure under firejail #422

New issue

Closed

opened 2026-05-05 05:49:48 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

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

Owner

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

telegram under firejail worked fine for me for a weeks, but today after installing updates I rebooted machine, started telegram under firjail as usual, but here is window with text:
Could not start Telegram Desktop!
You can seecomplete log below:
"[2016.06.29 20:13:53] Launched version: 9056, alpha: [FALSE], beta: 0, debug mode: [FALSE], test dc: [FALSE]
[2016.06.29 20:13:53] Executable dir: /home/user/apps/Telegram/, name: Telegram
[2016.06.29 20:13:53] Initial working dir: /home/user/
[2016.06.29 20:13:53] Working dir: /home/user/.TelegramDesktop/
[2016.06.29 20:13:53] Arguments: "/home/user/apps/Telegram/Telegram"
[2016.06.29 20:13:53] FATAL: Could not open '/home/user/.TelegramDesktop/log_startXX.txt' for writing log!
[2016.06.29 20:13:53] Connecting local socket to /tmp/709d9dfbb6882d21108f5de26d3a408d-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2016.06.29 20:13:53] This is the only instance of Telegram, starting server and app..."

$ apt-cache policy firejail
firejail:
Установлен: 0.9.40-3bpo8+1
Кандидат: 0.9.40-3bpo8+1
Таблица версий:
*** 0.9.40-3~bpo8+1 0
200 http://deb.debian.tsk.ru/repo/ftp.debian.org/debian/ jessie-backports/main amd64 Packages
100 /var/lib/dpkg/status

$ firejail --version
firejail version 0.9.40

Telegram version 0.9.56

How to continue run telegram under firejail?

Originally created by @aa3Eethi on GitHub (Jun 29, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/605 telegram under firejail worked fine for me for a weeks, but today after installing updates I rebooted machine, started telegram under firjail as usual, but here is window with text: Could not start Telegram Desktop! You can seecomplete log below: "[2016.06.29 20:13:53] Launched version: 9056, alpha: [FALSE], beta: 0, debug mode: [FALSE], test dc: [FALSE] [2016.06.29 20:13:53] Executable dir: /home/user/apps/Telegram/, name: Telegram [2016.06.29 20:13:53] Initial working dir: /home/user/ [2016.06.29 20:13:53] Working dir: /home/user/.TelegramDesktop/ [2016.06.29 20:13:53] Arguments: "/home/user/apps/Telegram/Telegram" [2016.06.29 20:13:53] FATAL: Could not open '/home/user/.TelegramDesktop/log_startXX.txt' for writing log! [2016.06.29 20:13:53] Connecting local socket to /tmp/709d9dfbb6882d21108f5de26d3a408d-{87A94AB0-E370-4cde-98D3-ACC110C5967D}... [2016.06.29 20:13:53] This is the only instance of Telegram, starting server and app..." $ apt-cache policy firejail firejail: Установлен: 0.9.40-3~bpo8+1 Кандидат: 0.9.40-3~bpo8+1 Таблица версий: **\* 0.9.40-3~bpo8+1 0 200 http://deb.debian.tsk.ru/repo/ftp.debian.org/debian/ jessie-backports/main amd64 Packages 100 /var/lib/dpkg/status $ firejail --version firejail version 0.9.40 ## Telegram version 0.9.56 How to continue run telegram under firejail?

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:54 -06:00

Author

Owner

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

Fixed! It got broken yesterday, try it now. Thanks for the bug.

@netblue30 commented on GitHub (Jun 29, 2016): Fixed! It got broken yesterday, try it now. Thanks for the bug.

gitea-mirror referenced this issue

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

[PR #427] [MERGED] Paths fix #3616

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#422

No description provided.

Rows
Columns