Bug 6507 - fatal crash when trying to delete nonexisting modem
fatal crash when trying to delete nonexisting modem
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: rp3 (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-10-29 12:59 EDT by frese01
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-05 22:51:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description frese01 1999-10-29 12:59:47 EDT
rp3 reported a fatal crash (core dump) when I
tried to delete the only registered modem on ttyS0.
(When running rp3 for the first time, the modem
which is really on ttyS1 was misdetected on ttyS0,
probably because it was in use at the time.).
The only way I was able to get rid of the ttyS0
modem entry was to delet /etc/wvdial.conf
Comment 1 Michael K. Johnson 1999-10-29 14:07:59 EDT
As far as "misdection" goes, you are correct that it cannot
detect a modem that is currently in use.  There's not much of
a way around that, unfortunately.  It just didn't look at that
device that was in use and took the next best.  If there really
was not a modem on that device, it should have told you that it
couldn't automatically detect a modem, and was offering you its
best guess...

The fatal crash, I think, is fixed in our current development
sources.  We're trying to track down a different bug before
doing a new release.
Comment 2 Michael K. Johnson 1999-11-01 17:49:59 EST
We are releasing rp3-1.0.1-1 as an errata update to Red Hat
Linux 6.1.  Please see if it fixes this bug for you.  We expect
it to do so, but it's always possible that we fixed a different
bug from the one you are experiencing.
Comment 3 Michael K. Johnson 1999-11-05 22:51:59 EST
We'll assume that rp3-1.0.1 fixes this problem.  Please reopen
this bug report if you find otherwise.  Thanks!

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