Bug 3454 - Certain programs crash Linux just starting
Summary: Certain programs crash Linux just starting
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sndconfig
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-06-14 14:05 UTC by rri0189
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-07-12 17:22:02 UTC

Attachments (Terms of Use)

Description rri0189 1999-06-14 14:05:09 UTC
There is a library used in RH Linux 6.0 to produce fake-GUI
in text mode.  It is used by linuxconf sometimes (when not
in X or when not run by root), and by sndconfig always.  I
have no idea of what its name is, or what other programs may
use it, or whether it is from RH or someone else.  It's not
simply curses; I have curses programs that work fine.  It
works OK when X is not running (e.g., when booted
single-user), but when a program using this package
(whatever its name may be) runs on my system in a console
window (e.g., open a window, type "sndconfig" and hit
Return), its logical screen flashes into place in the window
for a fraction enough of a second (enough to read one or two
words and see that the program is starting) and then my
entire screen turns black and there is nothing for it but
the Reset button and fsck.

I cannot make any attempt to make practical use of a system
with such a bug lying in wait, and with no knowledge of what
other programs may trigger it.  RH Installation support says
it ain't their problem.  W95 tells me that my video board is
a "S3 ViRGE 325 PCI".

Comment 1 Jay Turner 1999-06-14 17:23:59 UTC
Could you send us some debugging output from one of these crashes?
Without that, I really cannot attempt to recreate your problem.

Comment 2 rri0189 1999-06-14 19:44:59 UTC
You'll have to tell me how to go about it.  All I'm seeing now is a
quick and total system crash, with no visible information.  Is there a
trace I can turn on with a reasonable hope of surviving fsck?

In the meantime, can you help me narrow down the problem so that I can
ask intelligent questions?  Do you know what the name of this fake-GUI
library used by linuxconf and sndconfig is?  Where it's from?  Where
else it's used?

Comment 3 Bill Nottingham 1999-06-14 21:34:59 UTC
It's called newt, and it shouldn't be doing anything silly, AFAIK.
Is gpm running on your system?

One thing that can help is if you can telnet into the machine after
the display locks... can you do this?

------- Additional Comments From   06/14/99 18:03 -------
gpm is installed.  I can't say offhand whether it's

I'm not on any sort of LAN -- this is my home
system -- so I can't literally telnet in.  I
suppose I can get a crossover cable and use a
dumb-terminal program on my laptop to get in
through a serial port, but it will take me a day or
two, if only to buy the cable.

For what it's worth, Ctrl-Alt-Del is dead, but I've
used Linux so little thus far that I don't even
know whether that's normal.

------- Additional Comments From   06/14/99 19:16 -------
In the meantime, here's one additional piece of information.  The
failure only occurs under gnome.  kde, anotherlevel and failsafe are
all OK.

Comment 4 Bill Nottingham 1999-06-15 21:57:59 UTC
That's really strange that it would crash in gnome and
not kde, etc.

One way to tell if gpm is running is to do
'ps aux | grep gpm' before you run
whatever - this will show something like:

root       528  0.0  0.4  1112  300 ttyS0    S    17:34   0:00 gpm -t

if it is...

Comment 5 rri0189 1999-07-01 14:39:59 UTC
Sorry about the delay, but my computer and I had a deadline to deal
with, and playing with Linux had to go on the back burner.

I, too, was puzzled by the discrepancy between environments, until it
occurred to me that one difference would be the font used for terminal
windows.  I changed fonts, and, hey presto! the problem vanished.
Fortunately/unfortunately, I also cannot reproduce the problem any

Comment 6 Preston Brown 1999-07-12 17:22:59 UTC
problem seems to have corrected itself.

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