Bug 114427

Summary: suseplugger: on first login ask for configure kbd port
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Danny Al-Gaaf <dalgaaf>
Component: KDEAssignee: Stephan Kulow <coolo>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P2 - High CC: asklein, bugz57, coproscefalo, meissner
Version: Beta 4   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Danny Al-Gaaf 2005-08-31 15:00:07 UTC
After first login to KDE on a new fresh install of BETA 4 suseplugger popup a 
"New Hardware Found" dialog for "i8042 Kbd Port". This should imo not happen 
since this is the keyboard of the laptop and should be set up at installation.
Comment 1 Danny Al-Gaaf 2005-08-31 16:43:58 UTC
*** Bug 114463 has been marked as a duplicate of this bug. ***
Comment 2 Danny Al-Gaaf 2005-09-01 12:36:38 UTC
*** Bug 114688 has been marked as a duplicate of this bug. ***
Comment 3 Stephan Kulow 2005-09-01 15:24:19 UTC
well, is it configured correctly or not? /var/lib/hardware/udi... 
Comment 4 Danny Al-Gaaf 2005-09-01 18:00:17 UTC
*** Bug 114743 has been marked as a duplicate of this bug. ***
Comment 5 Azael Avalos 2005-09-01 21:58:21 UTC
I just updated from Beta3 to Beta4 and that message appears also, along with
some others (usb mouse, ps2 mouse, modem), I didn't configured the modem on
Beta3 so I guess the modem message its ok, but the other two mices were already
configured (unless config files were replaced during update) but the message
about the keyboard appeared 3 times on 3 different windows.

Comment 6 Volker Kuhlmann 2005-09-02 05:34:40 UTC
Same here: clean install of beta4, popups appear for configuring keyboard port 
(what for?), USB HID interface (what's that anyway, USB works fine with the 
mouse attached to it), ethernet card (done during install and working fine), 
modem/com port. 
 
When I click on "yes" (otherwise these things keep on popping up afetr each 
boot), it also asks for the root password, but with the exception of ethernet 
and modem, which start the corresponding yast module, nothing else happens. 
Comment 7 Gernot Hillier 2005-09-03 19:19:45 UTC
Same here. This is a new install of 10.0b4 (private PC).  
On first login, I'm informed about: 
 
1) New Hardware Found - "Maus i8042 Aux Port" (i.e. Mouse) 
2) New Hardware Found - Network Interface 
3) New Hardware Found - "Tastatur i8042 Kbd Port" (i.e. Keyboard) 
4) New Hardware Found - "Modem 16550A-compatible COM port" 
5) New Hardware Found - "Modem 16550A-compatible COM port" (yes, 2 times) 
 
ref 1): After clicking Yes, I was asked for root pwd, but then nothing 
happened 
ref 2): After clicking Yes, the YaST network config module appeared 
ref 3): same as for mouse - root pw, then nothing 
ref 4): After clicking Yes, the YaST modem config module appeard 
ref 5): see 4. 
 
ref 1) + 3) mouse and modem were certainly correctly configured. However. 
there are no files for them in /var/lib/hardware/udi. Should there be files? 
 
ref 2): I have only one network card and it was already configured at boot. 
File is in /var/lib/hardware 
 
ref 4) + 5) I have no modem. Only serial ports with nothing connected to them. 
No files for them in /var/lib/hardware either. 
 
This is really nasty... Feels like windows... 
 
 
Comment 8 Volker Kuhlmann 2005-09-03 23:25:54 UTC
The "new hardware" windows keep on popping up after every reboot. Not sure 
whether "don't show new hardware" will get rid of them because the box freezes 
X stone-dead when left to itself... meaning all that's needed for X to hang 
itself is wait. Kernel and networking is fine. All user processes can be 
killed except kfountain.kss (zombie), and X (also zombie). Reboot required. 
The load indicator in kpanel is frozen on 100% so the freeze happens before 
the login is completed. 
 
Changing priority to high, this has to be fixed for RC. 
Comment 9 Danny Al-Gaaf 2005-09-04 15:17:01 UTC
@Gernot Hiller: Only a little hint: you can't assign a bug for somebody. You can 
only reassign a bug. If the person accept and set the bug to assigned is his own 
decision.
Comment 10 Stephan Kulow 2005-09-06 08:55:13 UTC
this was fixed - and hopefully Yast will be fixed one day too. 
 
@Danny: if a bug is in NEEDINFO, it's only possible to go to ASSIGNED. 
Comment 11 Danny Al-Gaaf 2005-09-06 12:13:33 UTC
coolo: no, you can reassign the bug back to the assignee