The default permission restriction for /dev/uinput also affects AVRCP
devices connected via bluetooth to control the a2dp signal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/312957
Title:
CWiid
In order to work whatever the rule number you choose you could use the
:= operator :
KERNEL==uinput, MODE:=0666
For an explanation read man 7 udev :
:=
Assign a value to a key finally; disallow any later changes, which
may be used to prevent changes by any later
@Arturo
I have several other rules in there, the one with the lowest number is
called 45-something.rules, so I named mine 45-wminput.rules. After
this wminput still needed to be run with sudo.
Eventually, I fixed this by editing sudoers and allowing there for
wmimput to run with sudo without
I believe you should use the highest number of the rules, not the
lowest. In Karmic I had rules with 45-*.rules and 70-*.rules. When I
created a 45-wminput.rules nothing changed, but using 70-wminput.rules
fixed the problem.
But now, I'm on Lucid and I just have one rule before adding wminput, so
@gfnord Danny's solution worked for me in Lucid. You also have to sudo
modprobe uinput or add it in /etc/modules.
Which other rules do you have in /etc/udev/rules.d/ ?
--
CWiid Version 0.6.00 unable to open uinput
https://bugs.launchpad.net/bugs/312957
You received this bug notification
I tried Danny's instructions in Lucid Lynx 10.04 and they doesn't work.
wminput still needs sudo to run.
--
CWiid Version 0.6.00 unable to open uinput
https://bugs.launchpad.net/bugs/312957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I was able to fix this in Ubuntu Karmic Koala 9.10.
What I did was went to the directory
/etc/udev/rules.d/
And looked at what files were there one was
70-net.rules
So when I created my wminput rules I went to terminal and typed sudo
gedit then when it opens you have root control then you
Also I can only assume that the same principle would apply to other versions
like if you were running it one 9.04
I also have cWiid 6.00
--
CWiid Version 0.6.00 unable to open uinput
https://bugs.launchpad.net/bugs/312957
You received this bug notification because you are a member of Ubuntu
It seems that the rules editing workaround doesn't work anymore in
ubuntu 9.10 karmic koala...
Even with adding these two rows :
KERNEL==uinput, MODE=0666
KERNEL==uinput, GROUP=group
uinput has only these rights :
crw-r-
--
CWiid Version 0.6.00 unable to open uinput
I think this is appropriate. It does sound like one should expect this
to get fixed anytime soon, but the bug seems valid, confirmed, and an
imporant one for the package.
** Changed in: cwiid (Ubuntu)
Importance: Undecided = High
Status: Invalid = Confirmed
--
CWiid Version 0.6.00
should/should not expect ...
--
CWiid Version 0.6.00 unable to open uinput
https://bugs.launchpad.net/bugs/312957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Known behavior with no good solution at the moment. Closing bug.
** Changed in: cwiid (Ubuntu)
Status: Incomplete = Invalid
--
CWiid Version 0.6.00 unable to open uinput
https://bugs.launchpad.net/bugs/312957
You received this bug notification because you are a member of Ubuntu
Bugs,
How does we don't know how to fix it make the bug invalid?
--
CWiid Version 0.6.00 unable to open uinput
https://bugs.launchpad.net/bugs/312957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Funny, I would have been fine with 'input insertion SHOULD require
root privileges for security reasons' or something like that, but I'm
going to have to go with Scott's rhetorical question on this.
--
CWiid Version 0.6.00 unable to open uinput
https://bugs.launchpad.net/bugs/312957
You
You're right, that was undiplomatically stated. uinput insertion SHOULD
require root privs. Fundamentally, this is insecure and automatically
adding users to groups and so on doesn't change this. Short of finding
a way to remove uinput requirements, there's no way to secure this app.
This is probably due to permissions. uinput can listen and inject
keystrokes, so by default it's restricted to root.
The manpage has a few suggestions on how to work around this; try sudo
wminput and see if it still errors out.
If sudo fails, can you attach the output of lsmod?
** Changed in:
Ok, it works with sudo. Now, how do I use it without sudo, like groups and
all that?
--also, if you could help me so I don't have to run xsane as root to scan
things in, I would appreciate that immensely as well.
--
CWiid Version 0.6.00 unable to open uinput
From man wminput:
Place the following line in a file in /etc/udev/rules.d (see the
documentation for your distro for the recommended file for local rules)
to allow anyone on the system to use uinput:
KERNEL==uinput, MODE=0666
A more secure method uses the following line to allow anyone
18 matches
Mail list logo
