github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #4378] Telegram 2.8.0 not working #2641

New issue
Closed
opened 2026-05-05 09:18:16 -06:00 by gitea-mirror · 8 comments
gitea-mirror commented 2026-05-05 09:18:16 -06:00
Owner
Copy link

Originally created by @dmitryvakulenko on GitHub (Jun 28, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4378

I upgraded Telegram and now It can't connect to network. Firejail version 0.9.64.4. Profile I got from issue https://github.com/netblue30/firejail/issues/4377.
Telegram write this messages to log

[2021.06.28 20:53:24] Config Error: Failed to parse dns response JSON, error: illegal value
[2021.06.28 20:53:24] Config Error: Bad data size 0 required 344

EDIT by @rusty-snake: fix code-block

Originally created by @dmitryvakulenko on GitHub (Jun 28, 2021). Original GitHub issue: https://github.com/netblue30/firejail/issues/4378 I upgraded Telegram and now It can't connect to network. Firejail version 0.9.64.4. Profile I got from issue https://github.com/netblue30/firejail/issues/4377. Telegram write this messages to log ``` [2021.06.28 20:53:24] Config Error: Failed to parse dns response JSON, error: illegal value [2021.06.28 20:53:24] Config Error: Bad data size 0 required 344 ``` --- EDIT by @rusty-snake: fix code-block
gitea-mirror 2026-05-05 09:18:16 -06:00
  • closed this issue
  • added the
    stale
         label
gitea-mirror commented 2026-05-05 09:18:20 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jun 28, 2021):

Which distro do you use? Do you have any custom modifications (e.g. globals.local or telegram.local)?

I upgraded Telegram and now It can't connect to network.

Only in firejail? or is this a telegram bug? Does it work with --noprofile?

Profile I got from issue #4377.

How exactly? If you mean you use the current git-master, that's wrong because it can no work (can not parse noinput).

[2021.06.28 20:53:24] Config Error: Failed to parse dns response JSON, error: illegal value [2021.06.28 20:53:24] Config Error: Bad data size 0 required 344

What is your DNS setup? dnsmasq? systemd-resolved? unbound? dnscrypt-proxy? ...?

<!-- gh-comment-id:869947178 --> @rusty-snake commented on GitHub (Jun 28, 2021): Which distro do you use? Do you have any custom modifications (e.g. globals.local or telegram.local)? > I upgraded Telegram and now It can't connect to network. Only in firejail? or is this a telegram bug? Does it work with `--noprofile`? > Profile I got from issue #4377. How exactly? If you mean you use the current git-master, that's wrong because it can no work (can not parse `noinput`). > [2021.06.28 20:53:24] Config Error: Failed to parse dns response JSON, error: illegal value [2021.06.28 20:53:24] Config Error: Bad data size 0 required 344 What is your DNS setup? dnsmasq? systemd-resolved? unbound? dnscrypt-proxy? ...?
gitea-mirror commented 2026-05-05 09:18:21 -06:00
Author
Owner
Copy link

@dmitryvakulenko commented on GitHub (Jun 29, 2021):

Which distro do you use? Do you have any custom modifications (e.g. globals.local or telegram.local)?

Linux Mint 20.1 Cinnamon. Yes, I use custom usually (use private directory for Telegram). But now I copy profile from that issue.

Only in firejail? or is this a telegram bug? Does it work with --noprofile?

Telegram works fine without firejail or with --noprofile.

How exactly? If you mean you use the current git-master, that's wrong because it can no work (can not parse noinput).

I just remove noinput. All other the same.

What is your DNS setup? dnsmasq? systemd-resolved? unbound? dnscrypt-proxy? ...?

systemd-resolved in default configuration. It forward dns requests to my router and that's all.

<!-- gh-comment-id:870332085 --> @dmitryvakulenko commented on GitHub (Jun 29, 2021): > Which distro do you use? Do you have any custom modifications (e.g. globals.local or telegram.local)? Linux Mint 20.1 Cinnamon. Yes, I use custom usually (use private directory for Telegram). But now I copy profile from that issue. > Only in firejail? or is this a telegram bug? Does it work with --noprofile? Telegram works fine without firejail or with --noprofile. > How exactly? If you mean you use the current git-master, that's wrong because it can no work (can not parse noinput). I just remove noinput. All other the same. > What is your DNS setup? dnsmasq? systemd-resolved? unbound? dnscrypt-proxy? ...? systemd-resolved in default configuration. It forward dns requests to my router and that's all.
gitea-mirror commented 2026-05-05 09:18:22 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jun 29, 2021):

I still don't have a real idea what causes this. I mean if you would say all firejailed programs fail ... but only telegram, after an update. 😕 . Looks like you need to comment the profile to find the line that causes this (dbus-system none? wusc? private-etc? ...)

Yes, I use custom usually (use private directory for Telegram). But now I copy profile from that issue.

If you made you cahnged (e.g private ${HOME}/telegram-home) in telegram.local (as you should) they are still included.

<!-- gh-comment-id:870341551 --> @rusty-snake commented on GitHub (Jun 29, 2021): I still don't have a real idea what causes this. I mean if you would say all firejailed programs fail ... but only telegram, after an update. :confused: . Looks like you need to comment the profile to find the line that causes this (dbus-system none? wusc? private-etc? ...) > Yes, I use custom usually (use private directory for Telegram). But now I copy profile from that issue. If you made you cahnged (e.g `private ${HOME}/telegram-home`) in telegram.local (as you should) they are still included.
gitea-mirror commented 2026-05-05 09:18:24 -06:00
Author
Owner
Copy link

@dmitryvakulenko commented on GitHub (Jun 29, 2021):

Looks like you need to comment the profile to find the line that causes this

I try to do it yesterday but no any results. Looks like trouble more complex. One more things - after I reverted Telegram to old version it drop authorization and all settings. Maybе new version has different directory structure and firejail block access to new one.

<!-- gh-comment-id:870351905 --> @dmitryvakulenko commented on GitHub (Jun 29, 2021): > Looks like you need to comment the profile to find the line that causes this I try to do it yesterday but no any results. Looks like trouble more complex. One more things - after I reverted Telegram to old version it drop authorization and all settings. Maybе new version has different directory structure and firejail block access to new one.
gitea-mirror commented 2026-05-05 09:18:25 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jun 29, 2021):

I try to do it yesterday but no any results. Looks like trouble more complex.

It's cause by the profile (--noprofile works). If you comment everything, it must work as a consequence. If you now start to uncomment it line for line (and things like whitelisting at once) you could at least narrow it down (e.g. caused by whitelisting, one of the disable-*.inc includes, dbus policy, ...).

I reverted Telegram to old version it drop authorization and all settings. Maybе new version has different directory structure and firejail block access to new one.

That, or it just has a new config format which isn't backward-compatible. Or something else.

To check the directory structure, start it with firejail --private --name=telegram --ignore=privte-bin telegram and run firejail --join=telegram tree -a (or ls -aR) in a second terminal.

<!-- gh-comment-id:870360741 --> @rusty-snake commented on GitHub (Jun 29, 2021): > I try to do it yesterday but no any results. Looks like trouble more complex. It's cause by the profile (`--noprofile` works). If you comment everything, it must work as a consequence. If you now start to uncomment it line for line (and things like whitelisting at once) you could at least narrow it down (e.g. caused by whitelisting, one of the disable-*.inc includes, dbus policy, ...). > I reverted Telegram to old version it drop authorization and all settings. Maybе new version has different directory structure and firejail block access to new one. That, or it just has a new config format which isn't backward-compatible. Or something else. To check the directory structure, start it with `firejail --private --name=telegram --ignore=privte-bin telegram` and run `firejail --join=telegram tree -a` (or `ls -aR`) in a second terminal.
gitea-mirror commented 2026-05-05 09:18:25 -06:00
Author
Owner
Copy link

@dmitryvakulenko commented on GitHub (Jun 29, 2021):

The trouble was at include /etc/firejail/disable-shell.inc line. I'm confused...

<!-- gh-comment-id:870578173 --> @dmitryvakulenko commented on GitHub (Jun 29, 2021): The trouble was at `include /etc/firejail/disable-shell.inc` line. I'm confused...
gitea-mirror commented 2026-05-05 09:18:26 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Jun 29, 2021):

Try to add include allow-bin-sh.inc.

How can this stop network??! I'm confused... …I'm too.

<!-- gh-comment-id:870581735 --> @rusty-snake commented on GitHub (Jun 29, 2021): Try to add `include allow-bin-sh.inc`. How can this stop network??! I'm confused... …I'm too.
gitea-mirror commented 2026-05-05 09:18:27 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Oct 9, 2021):

I'm closing here due to inactivity, please fell free to request to reopen if you still have this issue.

<!-- gh-comment-id:939310941 --> @rusty-snake commented on GitHub (Oct 9, 2021): I'm closing here due to inactivity, please fell free to request to reopen if you still have this issue.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#2641
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?