[Bug 1222505] New: ckermit: cannot create lock file in /var/lock

https://bugzilla.suse.com/show_bug.cgi?id=1222505 Bug ID: 1222505 Summary: ckermit: cannot create lock file in /var/lock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: ceggers@arri.de QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Kermit needs to create a lock file for the used serial port (e.g. /dev/ttyUSB0) under /var/lock (symlink to /run/lock). Until Leap 15.5, that directory was owned by group "lock", so it was sufficient to add the current user to the "lock" group. But now the directory is owned by group "root", so using the "lock" group is not sufficient anymore. Reproducible: Always Steps to Reproduce: 1. Add current user to "dialout" group (and create re-login after that). 2. Ensure that step 1. was successful (e.g. by using the "id" command). 3. kermit -l /dev/ttyUSB0 Actual Results: Kermit gives an error "can't open device". Using "set line /dev/ttyUSB0" in kermit's interactive mode gives a more precise error message: "Sorry, write access to UUCP lockfile directory denied." Expected Results: kermit should have created the lock file and open /dev/ttyUSB0 A workaround is to change the group of /run/lock to "dialout" (and to add the current user to this group). But this change is lost after every reboot. Possibly related to https://bugzilla.opensuse.org/show_bug.cgi?id=624290 ("ckermit from contrib repository does not use lockdev, so cannot write to /var/lock"). The packet installed is: $ rpm -q ckermit --info Name : ckermit Version : 9.0.302 Release : 150000.3.3.1 Architecture: x86_64 Install Date: Mo 08 Apr 2024 09:44:42 CEST Group : Hardware/Modem Size : 2621762 License : BSD-3-Clause Signature : RSA/SHA256, Fr 01 Apr 2022 13:39:36 CEST, Key ID 70af9e8139db7c82 Source RPM : ckermit-9.0.302-150000.3.3.1.src.rpm Build Date : Fr 01 Apr 2022 13:39:14 CEST Build Host : goat10 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC <https://www.suse.com/> URL : http://www.kermitproject.org/ Summary : A Combined Serial and Network Communication Software Package Description : C-Kermit is a combined serial and network communication software package offering a consistent, medium-independent, and cross-platform approach to connection establishment, terminal sessions, file transfer, character-set translation, and automation of communication tasks. Distribution: SUSE Linux Enterprise 15 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1222505 https://bugzilla.suse.com/show_bug.cgi?id=1222505#c1 --- Comment #1 from Christian Eggers <ceggers@arri.de> --- minicom is also affected. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1222505 Luigi Baldoni <aloisio@gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aloisio@gmx.com -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1222505 https://bugzilla.suse.com/show_bug.cgi?id=1222505#c5 Jaan Rebane <jaan_r@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jaan_r@yahoo.com --- Comment #5 from Jaan Rebane <jaan_r@yahoo.com> --- Could be fixed by adding /run/lock folder to lock group. But I don't know whether changing /run/lock group from lock to root was intentional. See comment number 3 from bug 1226807: https://bugzilla.opensuse.org/show_bug.cgi?id=1226807#c3 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1222505 https://bugzilla.suse.com/show_bug.cgi?id=1222505#c6 Martin Burnicki <martin.burnicki@meinberg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.burnicki@meinberg.de --- Comment #6 from Martin Burnicki <martin.burnicki@meinberg.de> --- I've just encountered a similar problem with uucp. I'm using commands like cu -l /dev/ttyS0 -s 19200 to run a simple terminal on the konsole. That worked fine until OS 15.5. Now, in 15.6, I get an error $ cu -l /dev/ttyS0 -s 19200 cu: creat (/run/lock/uucp/TMP0000001f35): Permission denied cu: /dev/ttyS0: Line in use The problem is in the permissions of the lock directory, which is now by default: $ l /run/lock/uucp/ drwxr-x--- 2 uucp uucp 40 17. Jan 13:04 ./ drwxrwxr-x 6 root root 200 17. Jan 13:02 ../ Of course the current user is member of groups uucp and dialout, but write permission is by default only for the uucp *user*, but not for the uucp *group*. Changing the permissions from 750 to 770 fixes the problem for me: $ l /run/lock/uucp/ insgesamt 0 drwxrwx--- 2 uucp uucp 40 17. Jan 15:56 ./ drwxrwxr-x 6 root root 200 17. Jan 13:02 ../ I'm not sure if this is the right place to add this information, or if it had been better to open a new issue. I added it here because this issue was also about serial port locking. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com