Bug 903753 - Minicom prints lockdev related garbage when the serial device disappears (hot unplug) and can't be terminated with Ctrl+A|Q until Ctrl+C is pressed
Summary: Minicom prints lockdev related garbage when the serial device disappears (hot...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: minicom
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-24 18:41 UTC by Jaromír Cápík
Modified: 2016-02-01 01:57 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-18 13:49:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
terminal snapshot (961 bytes, text/plain)
2013-01-24 18:41 UTC, Jaromír Cápík
no flags Details

Description Jaromír Cápík 2013-01-24 18:41:02 UTC
Created attachment 686915 [details]
terminal snapshot

Description of problem:
Minicom prints lockdev related garbage when the serial device disappears due to a hot unplug and can't be terminated with Ctrl+A|Q until Ctrl+C is pressed.
Terminal snapshot is attached.


Version-Release number of selected component (if applicable):
minicom-2.6.1-2.fc19
lockdev-1.0.4-0.4.20111007git.fc17

How reproducible:
always

Steps to Reproduce:
1. configure minicom to work with ttyUSB*
2. start minicom
3. unplug the USB device
  
Actual results:
-lockdev warnings on the screen messing the screen
-minicom can't be terminated with Ctrl+A|Q until Ctrl+C is pressed

Expected results:
-no warnings
-minicom can be terminated with Ctrl+A|Q

Comment 1 Fedora End Of Life 2013-04-03 19:23:30 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Jaromír Cápík 2014-01-31 18:19:38 UTC
The lockdev warnings are fixed in minicom-2.6.2-2 and later.

Comment 3 Fedora End Of Life 2015-01-09 22:03:34 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-18 13:49:28 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.