Package: minicom Version: 2.7.1-1+b1 Severity: normal When minicom checks for a lockfile (e.g. /var/lock/LCK..modem0), it only considers lockfiles that are readable (by the current user). If the lockfile isn't readable, minicom will proceed as if the lockfile didn't exist, causing a collision with the application already accessing the port/device.
Expected behavior would be that minicom considers the port/device busy if it finds a lockfile, regardless of whether it is readable or not. -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages minicom depends on: ii libc6 2.28-10 ii libtinfo6 6.1+20181013-2+deb10u2 Versions of packages minicom recommends: ii lrzsz 0.12.21-10 minicom suggests no packages. -- no debconf information
