Improper group for dumpcap (wireshark-cli)
Hi,
Originally posted on the Fedora project forum: https://discussion.fedoraproject.org/t/fedora-sway-atomic-improper-group-for-dumpcap-wireshark-cli/167883
I’ve been building my own image based off Universal Blue using BlueBuild: https://github.com/CBenoit/fedora-atomic-kokoriko
I install wireshark-cli via the dnf module in recipe.yml, but the group for the
I’ve seen: usbmon, keyd as well as a numerical value, suggesting a non existing group.
I initially thought it was a packaging problem in the fedora repos, and opened a ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2403092
But as it turns out, I do not get the problem when installing, e.g.: Fedora Atomic Sway + rpm-ostree layer with wireshark-cli.
The maintainer in the issue tracker reported greetd set as the group for the file.
There seems to be something really spooky happening with the group of this file.
Originally posted on the Fedora project forum: https://discussion.fedoraproject.org/t/fedora-sway-atomic-improper-group-for-dumpcap-wireshark-cli/167883
I’ve been building my own image based off Universal Blue using BlueBuild: https://github.com/CBenoit/fedora-atomic-kokoriko
I install wireshark-cli via the dnf module in recipe.yml, but the group for the
/usr/bin/dumpcapI’ve seen: usbmon, keyd as well as a numerical value, suggesting a non existing group.
I initially thought it was a packaging problem in the fedora repos, and opened a ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2403092
But as it turns out, I do not get the problem when installing, e.g.: Fedora Atomic Sway + rpm-ostree layer with wireshark-cli.
The maintainer in the issue tracker reported greetd set as the group for the file.
There seems to be something really spooky happening with the group of this file.
