User talk:Txomon

wireshark

If the problem described here occurs, you need to run wireshark with a user in the wireshark group, which is thoroughly explained in Wireshark#Capturing_as_normal_user. The provided solution only restores properties set by the wireshark-cli package: [1], [2]. -- Lahwaacz (talk) 16:38, 20 October 2015 (UTC)

In all the computers I have installed archlinux on, I have found that wireshark group wouldn't be setup for it. It's maybe due to me creating the groups manually on installation time, but the fact is that updates of wireshark package still break permissions. The idea is to provide a common troubleshoot so that users understand how permissions are managed, regardless of the bugs the package installation script contains.

If you check the installation scripts, [3] you will see it directly adds a wireshark system group in a random number (150). Also, I see no chown on those lines, meaning that if you don't have the group created by the script, your installation won't work. -- Txomon (talk) 16:48, 20 October 2015 (UTC)

Report a bug. Not only do more users benefit, it will also show if the issue at hand is on your end, or not. Until then, I've marked the section for deletion (sorry, but I'm a hardliner on this). -- Alad (talk) 16:53, 20 October 2015 (UTC)

AFAIK, there is no harm on having explained what the capabilities and the permissions rely on. Are the wiki and reporting the bug incompatible? Txomon (talk) 17:00, 20 October 2015 (UTC)

Just file a bug report first, then add a section if applicable. -- Alad (talk) 17:06, 20 October 2015 (UTC)

The number of 150 is not random, it is taken from Arch's UID/GID database. Of course if the wireshark group has different ID on your system, of course things will break. So the question is why did you do it (create the wireshark group manually)? -- Lahwaacz (talk) 17:07, 20 October 2015 (UTC)

I didn't know about such database. I did add all the groups to my user on arch installation time, using groupadd -r to add the groups. That way, if I installed wireshark anyday, I would have already the group active.

Well, that's just wrong approach leading to problems like this one -- all the necessary groups are added automatically as packages are installed (created by the .install scripts shipped with the packages), the system should always contain only those groups that are needed at the moment. As for fixing this -- I have no idea, you need to update the local mappings (/etc/passwd and /etc/group) and metadata of all files to match to the correct numeric ID (because that's what is actually stored on the disk). Do a research on how many groups (and users) have wrong ID on your system, if they are many, perhaps reinstalling might be easier. Alad? -- Lahwaacz (talk) 17:32, 20 October 2015 (UTC)

That is not what is officially linked :(, seems to be a work in progress... but if you tell me this is the way to go, then I would modify that page to link for specific GIDs. I took the groups from what was listed there, with no specific gid. Txomon (talk) 17:53, 20 October 2015 (UTC)

I've tried it in a VM (-Syu'd today) and it works as expected. So this indeed looks like the consequence of an weird installation method. -- Alad (talk) 17:48, 20 October 2015 (UTC)

I have added a task to clarify the situation in the package. I would propose removing support for pre-existing wireshark group if it doesn't have gid 150. https://bugs.archlinux.org/task/46809 Txomon (talk) 17:53, 20 October 2015 (UTC)

Looking at FS#42182:

1. New groups need to be created as root, as such the command is in the .install file, which is run as root by pacman (here after installation)
2. makepkg however runs as the regular user, and you can't chown/chgrp to a (for the majority of Arch users) non-existing name - a GID however works.
3. The .install file references to said GID. I believe the getent call only prevents an error message in this case; you could set the permissions again if getent succeeds, but that's ugly at best.

As such, a note was added to Users and groups#Software groups, leaving out the need for a section in wireshark. -- Alad (talk) 07:57, 21 October 2015 (UTC)

What made you think that the groups in this list should be created manually? All GIDs below 1000 are reserved for the system and should not be touched by users (except for adding users to the group). As such, there is no support for custom GIDs on the side of packages. What makes you think otherwise? -- Lahwaacz (talk) 20:19, 20 October 2015 (UTC)