mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #947] Chromium 'Save as' doesn't work with --net on KDE #644
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#644
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 @fld on GitHub (Nov 29, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/947
On Debian jessie KDE I used:
% firejail --trace --profile=/etc/firejail/chromium.profile --net=br0 --dns=192.168.0.1 --defaultgw=192.168.0.1 chromium --temp-profileAnd tried to "Save as" (ctrl+s) the page. Nothing happens.
Corresponding,
trace output:
audit.log:
type=ANOM_ABEND msg=audit(1480420969.030:82479): auid=1000 uid=1000 gid=1000 ses=2 pid=18448 comm="drkonqi" exe="/usr/lib/kde4/libexec/drkonqi" sig=6@netblue30 commented on GitHub (Nov 30, 2016):
drkonqi seems to be the KDE crash handler. It seems something crashed and drkonqi was activated
It is hard to tell what's going on. Probably, they try to connect to some local server over a Unix socket. The network namespace isolates all external sockets, so the connection doesn't succeed - and then they crash! I don't get this problem on my setup (Debian stable + LXDE), could be something related to KDE/Cromium integration.
@fld commented on GitHub (Nov 30, 2016):
Chromium uses Qt so the resulting 'Save as - KDialog' has the KDE "Places" side-bar, which displays all the systems currently mounted storage. Apparently this stuff uses UNIX sockets and/or DBus.
I tried this with gwenview:
Looks like the --net feature is not going to be very useful in KDE environments, unless there is a way to allow DBus and UNIX sockets?
@netblue30 commented on GitHub (Dec 3, 2016):
This should be very easy for them to fix. Crashing pressing "Save as" could become a big issue. For example, you work in a text editor for one hour and when you press "Save as" the program crashes.
Network namespace is a basic security feature in Linux kernel, KDE devs should try to support it. Most people will choose a kernel security feature over some misimplemented dbus functionality in user space. Take Docker as an example. Network namespace is enabled by default in Docker, I don't think you can convince the users to run containers without it. They would drop your program and choose something else.
@smitsohu commented on GitHub (Sep 27, 2017):
It should be possible to work around the issue with chromium, if you start it with
NO_CHROME_KDE_FILE_DIALOG=1 chromium