Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#24467 - [inputattach] rc.d script broken?
Attached to Project:
Community Packages
Opened by Simon Bachmann (lupylucke) - Friday, 27 May 2011, 11:28 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 31 May 2011, 10:22 GMT
Opened by Simon Bachmann (lupylucke) - Friday, 27 May 2011, 11:28 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 31 May 2011, 10:22 GMT
|
DetailsDescription:
The script to start inputattach (/etc/rc.d/inputattach) does not parse the options in the IAPARAMS array correctly: the script currently starts one inputattach instance for every "word" (meaning whitespace separated sequence) in the array instead of one instance for every element. IOW, with the simple inputattach configuration IAPARAMS=( "--mouseman /dev/ttyS0" ) the /etc/rc.d/inputattach script calls inputattach twice. Once with only the '--mouseman' option, and once with only '/dev/ttyS0'. Well, actually only the first call is done, which fails with the error message "inputattach: must specify device", after that the script exits. For a quite simple fix see attached patch 
inputattach.diff
(0.4 KiB)
|
This task depends upon