After install linssid, linssid do not work from Debian 10 on distrobox.
failed: operation not permitted (-1)
To install linssid on fedora you need to do in terminal:
sudo dnf copr enable nucleo/linssid #enable it
sudo dnf install linssid-ex #install it
sudo linssid #run it
Using distrobox with any linux distro installed - the linssid do not work. This is one of application than not benefit form using Distrobox.
Yep - that work well - but main tread is Distrobox - not linssid itself.
No, distrobox not works with Debian10, I think it needs at least to be Debian 11 and if it is not enabled in stable you need to use testing alias debian 12 as it is released already.
Actually Debian 10 looks supported as a container distro by Distrobox.
1 Like
command failed: Operation not permitted (-1) i do also get it after installing debian.
Aparently a other problem than the debian version. Mine is:
ilikelinux@debian12-distrobox:/$ cat /etc/issue
Debian GNU/Linux 12 \n \l
The software is starting nomally but gives the message (in terminal):
sudo /usr/sbin/linssid
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
(linssid:502548): dbind-WARNING **: 17:45:20.230: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Gtk-Message: 17:45:20.262: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:45:20.262: Failed to load module "pk-gtk-module"
Gtk-Message: 17:45:20.263: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:45:20.263: Failed to load module "pk-gtk-module"
This looks like a dos style line ending with the cr-lf. Linux style line endings are cr only (\n) so the improper text line feeds may be a factor.
What was used to edit the config files?
I think that this issue (the file) is unrelated to the issue 
However, on Fedora the issue file contains these lines:
\S
Kernel \r on an \m (\l)
So \n and \l are not line endings.
man issue It may contain various @char and \char sequences, if supported by the getty-type program em‐ployed on the system.
man mingetty
\n inserts machine's network node hostname (uname -n)
\l insert line on which mingetty is running,
Actually it works (the application window opens up), but it is unable to capture anything.
I.e. also tcpdump doesn’t work inside a container.
$ sudo tcpdump -i any
tcpdump: any: You don't have permission to capture on that device
(socket: Operation not permitted)
I’m not a great expert, but containers are somewhat sandboxed. They have not complete access to all parts of the host OS, mainly the kernel and then the hardware, I guess. Or maybe, also, because the container is rootless.
Maybe there are some flags to allow these things.
This is also what i did try to point out. I read that with distrobox usb and audio will be shared. So that might be that wifi is not.
Anyway I pointed out and tested from the beginning, that it works best while installing direct on the host.
Even then I tested on Debian distrobox because I’m interested to see how it works in general.
1 Like
You can create a distrobox with the --root flag[1]
distrobox create --name debian10rootful --image debian:10 --root
distrobox enter --root deb10rootful
In this way, running
sudo /usr/sbin/linssid
inside the distrobox, works.
We trust you already know the implications of running distrobox, as well as anything else, with the root user and that with great power comes great responsibilities. ↩︎
I do agree with you that with --root it is possible.
While the idea of using toolbox and distrobox is using containers within the own user-spaces.
if you want to claim your answer as a solution, it would be important to know what the OP was trying to achieve with his question.
a. an executable application on its own system (missing rpm package)
or
b. test an updated version of a program to see if it runs in a specific operating system (with a current kernel).
Please clarify this with the OP and include it in your solution. In the end we try to add value to the fedora project while using it’s already secure OS. My solution was to use the existing rmp.
I will delete my assumption that distrobox and debian 10 not works with linssid.
Sorry not answering you, I just tried to check on the distroboxes side, if I really do using debian 12. While installing distrobox from the official @system repository, toolbox f38 got first pushed, while the description just mentioned podman, and this was installed allready.
The config file was not edited by me I just used a googled a command to check it. Normally i use hostnamectl to see fedora and kernel-specific information (I just got to much used to Fedora !)
dnf info distrobox
Description : Use any linux distribution inside your terminal. Distrobox uses podman
: or docker to create containers using the linux distribution of your
: choice. Created container will be tightly integrated with the host,
: allowing to share the HOME directory of the user, external storage,
: external usb devices and graphical apps (X11/Wayland) and audio.