Bug 61481

Summary: aumix printing debugging info that messes up screen
Product: [Retired] Red Hat Public Beta Reporter: Jonathan Kamens <jik>
Component: gpmAssignee: wdovlrrw <brosenkr>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: skipjack-beta1CC: billc, david.balazic, ejb
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-04-06 05:41:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Kamens 2002-03-20 12:51:07 UTC
I have:

aumix-2.7-8
gpm-1.20.0-1

Every time I start up aumix, I get a debugging message which messes up the
screen display:

aumix*** debug ***:
[/usr/src/build/78046-i386/BUILD/gpm-1.20.0/src/liblow.c(202)]:++

Comment 1 Mike A. Harris 2002-03-22 02:53:44 UTC
Not an aumix problem.  These are gpm debug messages.

Comment 2 Bill Nottingham 2002-03-26 20:08:24 UTC
*** Bug 61990 has been marked as a duplicate of this bug. ***

Comment 3 David Balažic 2002-03-27 09:38:35 UTC
I see this in Skipjack, so I changed the Product.

Comment 4 Bill Crawford 2002-03-29 02:28:22 UTC
Seen this on my desktop (ASUS A7V, Athlon, SB Live!) too.


Comment 5 Jay Berkenbilt 2002-04-06 05:41:24 UTC
This problem is still present in skipjack beta-2 at least with my configuration.
 I have an HP Omnibook 6100.  From /etc/modules.conf:

alias sound-slot-0 maestro3
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1
|| :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :

From /etc/sysconfig/hwconf:

class: AUDIO
bus: PCI
detached: 0
driver: maestro3
desc: "ESS Technology|ES1988 Allegro-1"
vendorId: 125d
deviceId: 1988
subVendorId: 103c
subDeviceId: 001a
pciType: 1


Comment 6 Bernhard Rosenkraenzer 2002-04-09 17:48:05 UTC
Fixed by reverting to version from 7.2