FS#15835 - New install of arch w/xorg/kde fails to enable keybd and mouse at log-in

Attached to Project: Arch Linux
Opened by Ray Clancy (lilsirecho) - Thursday, 06 August 2009, 17:46 GMT
Last edited by Jan de Groot (JGC) - Friday, 07 August 2009, 00:26 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Installed archlinux yesterday evening with ftp install of x86-64.

Install followed by install of xorg and Kde via pacman.

After kde install, keyboard and mouse inoperative at log-in.

This would impact all newly installed systems.

Note that it affects recent upgrades as well.



Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:See recent pacman post re: subject.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 07 August 2009, 00:26 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Input hotplugging is documented in the wiki, post_install/post_upgrade points to this wiki.
Adding hal to default daemon list is not an option.
Comment by Ray Clancy (lilsirecho) - Thursday, 06 August 2009, 17:48 GMT
See the following post:http://bbs.archlinux.org/viewtopic.php?id=77400
Comment by Aaron Griffin (phrakture) - Thursday, 06 August 2009, 17:52 GMT
Is this because hal is not running?
Comment by Roman Kyrylych (Romashka) - Thursday, 06 August 2009, 18:41 GMT
post your xorg logfile, config file and DAEMONS list
Comment by Roman Kyrylych (Romashka) - Thursday, 06 August 2009, 18:45 GMT
also, there are lots of useful info at http://wiki.archlinux.org/index.php/Xorg_input_hotplugging
Comment by Jan de Groot (JGC) - Thursday, 06 August 2009, 19:15 GMT
Please provide information: logfiles, configuration files, etc. I'm starting to consider closing support requests without information in the near future.
Comment by Ray Clancy (lilsirecho) - Thursday, 06 August 2009, 19:38 GMT
Thanks for comments gents...

If hal is required, it must be that the install is deficient in not establishing it as a required package/and/or, it is not running for some obscure reason.

Since the package is supplied by the install, some notification that hal must be included in the Daemons of rc.conf is mandatory for new installers.

This need for hal is understood but perhaps not by new users, notwithstanding that they be knowledgeable about linux.

Therefore, this bug was generated to show a need or a reminder in the install/run procedure for the hal package.

Submitted in good faith......
Comment by Aaron Griffin (phrakture) - Thursday, 06 August 2009, 19:43 GMT
Does hal fix the issue?

hal is not actually required (I don't use it), but this issue is obscure. There are flags you can add to xorg.conf to tell it not to use hal.

If this actually solves the issue, then we need to make this nuance a bit more visible.
Comment by Jan de Groot (JGC) - Thursday, 06 August 2009, 20:21 GMT
The installation or upgrade of xorg-server points to the wiki about input configuration. If you don't create an xorg.conf that disables hal, you will need hal for input devices. The 1.6 series of xorg-server wait until hal comes online, while 1.5 aborts autoconfig if hal isn't enabled. I think the wiki link should be enough documentation. This is also why I ask you for logfiles and configuration files, as we can't troubleshoot anything without that information.
Comment by Aaron Griffin (phrakture) - Thursday, 06 August 2009, 20:29 GMT
Perhaps we can make the message more clear? "If you are having keyboard or mouse issues, please visit <blah> for more info on input configuration" ?
Comment by Ray Clancy (lilsirecho) - Thursday, 06 August 2009, 22:44 GMT
The issue was solved by adding hal to the Daemons in rc.conf.

In my view, having hal as a permanent entry in Daemons is preferable to the present arrangement.

Having an excess Daemon is no biggee but no keyboard or mouse is catastrophic.

Those in the know can delete the daemon as desired.

Perhaps this is worth a shot?
Comment by Aaron Griffin (phrakture) - Thursday, 06 August 2009, 22:53 GMT
I don't understand what a "permanent entry" means. If you mean it should be in the default rc.conf, then we need to install hal and dbus by default, to solve an X issue on all machines that might not even run X. We're getting a little silly here.

I don't want to do any hand holding on this one. Personally, I find it very stupid on Xorg's part the way they handled this. If hal isn't running, why not fallback to the "old way"?

Let's just worry about making sure the documentation and notifications are up to snuff.
Comment by Ray Clancy (lilsirecho) - Friday, 07 August 2009, 00:24 GMT
Perhaps those who don't use X and know that hal isn't needed can delete hal.

I suggest that the inclusion of hal permits the performance of all installs including those with X complications and those without X. A daemon not used is no serious matter............

I have no further comments. Thanks to all.

Loading...