mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #5265] jetbrains-toolbox: "Invalid client serial" when using dbus-user=filter #2936
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#2936
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 @mid-kid on GitHub (Jul 20, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5265
Description
Jetbrains Toolbox takes an insane amount of time to load up and display its tray icon when using
--dbus-user=filter. Unlike a normal run, it displays the following message:This message originates from xdg-dbus-proxy, in flatpak-proxy.c.
Steps to Reproduce
firejail --noprofile --dbus-user=proxy --appimage ./jetbrains-toolboxExpected behavior
The app runs and displays a GtkStatusIcon as a fallback for having no access to a StatusNotifierItem tray.
Actual behavior
It took a solid 5 minutes to start up and do this.
Behavior without a profile
N/A
Additional context
I don't have a StatusNotifierItem implementation like snixembed, yet running outside of firejail makes it work. I want it to run with either --dbus-user=none or --dbus-user=proxy, either is fine.
Environment
Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)Log
Output of
LC_ALL=C firejail --noprofile --dbus-user=proxy --appimage ./jetbrains-toolbox@mid-kid commented on GitHub (Jul 20, 2022):
Reproduced this on a clean debian bullseye install as well.
@rusty-snake commented on GitHub (Jul 20, 2022):
--dbus-user=proxyis not supported. It'sfilter.The fallback code a program uses if an dbus name does not exists is outside of the scope of firejail, consider reporting this to jetbrains then.
If you believe this happens because of an implementation deatil of xdg-dbus-proxy, report it there.
TL;DR: Is this a firejail issue?
@rusty-snake commented on GitHub (Jul 20, 2022):
IIRC jetbrains programs do not use GTK.
@mid-kid commented on GitHub (Jul 20, 2022):
I meant --dbus-user=filter, of course. The --dbus-user=proxy option terminates firejail inmediately.
Anyway, this program uses libappindicator. That's what uses GtkStatusIcon as a fallback.
This problem doesn't happen without firejail, as the fallback works properly in that case, though it's very possible that it's a xdg-dbus-proxy thing.
@mid-kid commented on GitHub (Jul 20, 2022):
Yeah, I managed to reproduce it with the following setup:
@mid-kid commented on GitHub (Jul 21, 2022):
Opened a bug report in xdg-dbus-proxy: https://github.com/flatpak/xdg-dbus-proxy/issues/45
@mid-kid commented on GitHub (Jul 22, 2022):
The library causing the hang turned out to be dbus-java, not libappindicator. The issue is further discussed here, with a potential workaround that might appear in future releases: https://github.com/hypfvieh/dbus-java/issues/177
For now, a different workaround to get the application to not hang yet still display a GtkStatusIcon-powered tray icon would be to run with
dbus-user none, and writing the following in~/.config/JetBrains/Toolbox/toolboxrcto start a dummy non-proxying D-Bus server in the sandbox:@kmk3 commented on GitHub (Jul 22, 2022):
@mid-kid Thanks for the details.
(Re-closing as "not planned" since the bug is not in firejail)