Your message dated Sun, 21 Jun 2026 05:45:23 +0200
with message-id <[email protected]>
and subject line Re: Bug#979422: minicom does not consider port busy if
lockfile isn't readable (existence isn't enough)
has caused the Debian Bug report #979422,
regarding minicom does not consider port busy if lockfile isn't readable
(existence isn't enough)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
979422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979422
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
This bug appears to be fixed since minicom-2.9-1.
I'm closing this bug report.
Martin
On Wed, Jan 06, 2021 at 15:09:48 +0100, Björn Wiberg wrote:
> 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
--- End Message ---
