Bug 79276 - beta 2 serial mouse interaction issues
beta 2 serial mouse interaction issues
Status: CLOSED DUPLICATE of bug 80115
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-xfree86 (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
:
Depends On:
Blocks: 79579
  Show dependency treegraph
 
Reported: 2002-12-09 09:15 EST by R P Herrold
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:50:17 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 R P Herrold 2002-12-09 09:15:35 EST
Follow on bug under beta 2 of Gingin
 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=78809

For some reason, the serial mouse is not being pulled out of the config file,
and gpm is being killed.

I restarted gpm, and moved the mouse to confirm its presence in console mode
before running redhat-config-xfree86

Then:

* ddcprobe returned bogus values:
ID:   GSM427d
Name: None
HorizSync: -268377405--268376112
VertSync:  -268376112--268370092

Traceback (most recent call last):
  File "/usr/share/redhat-config-xfree86/xconf.py", line 1091, in ?
    xconfig = generate_xconfig(hardware_state)
  File "/usr/share/redhat-config-xfree86/xconf.py", line 855, in
generate_xconfig
    get_option(corepointer, "Device").val = "/dev/" + mouse.getDevice()
TypeError: cannot concatenate 'str' and 'NoneType' objects


checking /dev:

Subject: mouse-there

lrwxrwxrwx    1 root     root            5 Dec  8 21:55 /dev/mouse -> ttyS0

and it killed the mouse as well.

bizarre
Comment 1 Brent Fox 2002-12-23 02:15:17 EST

*** This bug has been marked as a duplicate of 80115 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:50:17 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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