Bug#687090: systemd udev files breaks recognition pointer device to X
Am 12.02.2013 09:55, schrieb Kamil Jońca: Sorry for late reply. Important notice: It looks like, problem is solved with Package: systemd New: yes State: installed Automatically installed: no Version: 44-8 Priority: extra Section: admin tested on 2 systems: fresh installation on my laptop, and PC on which problem was noticed. Ok, I guess we can close this bug then. Michael Biebl bi...@debian.org writes: On 18.11.2012 22:27, Kamil Jońca wrote: Michael Biebl bi...@debian.org writes: On 09.09.2012 17:20, Kamil Jonca wrote: Package: systemd Version: 44-4 Severity: normal There is simple laser pointing device. When systemd udev files are installed - this device is not visible to X server. What exactly do you mean by not visible to the X server? This device behaves as degenerated keyboard - has two buttons which produce Prior/Next and b/F5 (when holding down) keys. With systemd udev files xev does not signal any keys, when buttons are pressed. Moreover X server when restarde does not write anything about this device to logs. When I remove these files X server found this device. Can you try the following: systemctl enable udev-settle.device --8---cut here---start-8--- sudo systemctl enable udev-settle.device [sudo] password for kjonca: Operation failed: No such file or directory --8---cut here---end---8--- Yeah, this was a typo, I meant systemctl enable udev-settle.service (not .device) --8---cut here---start-8--- Failed to issue method call: Launch helper exited with unknown return code 1 --8---cut here---end---8--- Hm, strange. Is this reproduible? Looks like your dbus installation not working properly. Yes, it's reproductioble. It's quite possible that dbus installation is broken. (Maybe it's avahi? - Turned off by me) What's the output of systemctl status dbus.service dbus.socket signature.asc Description: OpenPGP digital signature
Bug#687090: systemd udev files breaks recognition pointer device to X
Michael Biebl bi...@debian.org writes: Am 12.02.2013 09:55, schrieb Kamil Jońca: Sorry for late reply. Important notice: It looks like, problem is solved with Package: systemd New: yes State: installed Automatically installed: no Version: 44-8 Priority: extra Section: admin tested on 2 systems: fresh installation on my laptop, and PC on which problem was noticed. Ok, I guess we can close this bug then. Yes, I think so. [...] Can you try the following: systemctl enable udev-settle.device --8---cut here---start-8--- sudo systemctl enable udev-settle.device [sudo] password for kjonca: Operation failed: No such file or directory --8---cut here---end---8--- Yeah, this was a typo, I meant systemctl enable udev-settle.service (not .device) --8---cut here---start-8--- sudo systemctl enable udev-settle.service [sudo] password for kjonca: ln -s '/lib/systemd/system/udev-settle.service' '/etc/systemd/system/basic.target.wants/udev-settle.service' --8---cut here---end---8--- --8---cut here---start-8--- Failed to issue method call: Launch helper exited with unknown return code 1 --8---cut here---end---8--- Hm, strange. Is this reproduible? Looks like your dbus installation not working properly. Yes, it's reproductioble. It's quite possible that dbus installation is broken. (Maybe it's avahi? - Turned off by me) What's the output of systemctl status dbus.service dbus.socket --8---cut here---start-8--- systemctl status dbus.service dbus.socket Failed to get D-Bus connection: No connection to service manager. --8---cut here---end---8--- (also as root via sudo) KJ -- http://blogdebart.pl/2009/12/22/mamy-chorych-dzieci/ Ummm, well, OK. The network's the network, the computer's the computer. Sorry for the confusion. -- Sun Microsystems -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687090: systemd udev files breaks recognition pointer device to X
On 18.11.2012 22:27, Kamil Jońca wrote: Michael Biebl bi...@debian.org writes: On 09.09.2012 17:20, Kamil Jonca wrote: Package: systemd Version: 44-4 Severity: normal There is simple laser pointing device. When systemd udev files are installed - this device is not visible to X server. What exactly do you mean by not visible to the X server? This device behaves as degenerated keyboard - has two buttons which produce Prior/Next and b/F5 (when holding down) keys. With systemd udev files xev does not signal any keys, when buttons are pressed. Moreover X server when restarde does not write anything about this device to logs. When I remove these files X server found this device. Can you try the following: systemctl enable udev-settle.device and the reboot and test again The only issue I can think of is that this is related to device permissions, which means /lib/udev/rules.d/70-uaccess.rules would be involved. When you are logged in, and before you plugin the device, what is the output of systemd-loginctl? Hm: --8---cut here---start-8--- Failed to issue method call: Launch helper exited with unknown return code 1 --8---cut here---end---8--- Hm, strange. Is this reproduible? Looks like your dbus installation not working properly. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#687090: systemd udev files breaks recognition pointer device to X
On 09.09.2012 17:20, Kamil Jonca wrote: Package: systemd Version: 44-4 Severity: normal There is simple laser pointing device. When systemd udev files are installed - this device is not visible to X server. What exactly do you mean by not visible to the X server? When I remove these files X server found this device. Which udev rules files did you remove explicitly? The only issue I can think of is that this is related to device permissions, which means /lib/udev/rules.d/70-uaccess.rules would be involved. When you are logged in, and before you plugin the device, what is the output of systemd-loginctl? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#687090: systemd udev files breaks recognition pointer device to X
Michael Biebl bi...@debian.org writes: On 09.09.2012 17:20, Kamil Jonca wrote: Package: systemd Version: 44-4 Severity: normal There is simple laser pointing device. When systemd udev files are installed - this device is not visible to X server. What exactly do you mean by not visible to the X server? This device behaves as degenerated keyboard - has two buttons which produce Prior/Next and b/F5 (when holding down) keys. With systemd udev files xev does not signal any keys, when buttons are pressed. Moreover X server when restarde does not write anything about this device to logs. When I remove these files X server found this device. Which udev rules files did you remove explicitly? mv -vi /lib/udev/rules.d/71-seat.rules /lib/udev/rules.d/71-seat.rules-- The only issue I can think of is that this is related to device permissions, which means /lib/udev/rules.d/70-uaccess.rules would be involved. When you are logged in, and before you plugin the device, what is the output of systemd-loginctl? Hm: --8---cut here---start-8--- Failed to issue method call: Launch helper exited with unknown return code 1 --8---cut here---end---8--- KJ -- http://blogdebart.pl/2010/03/17/dalsze-przygody-swinki-w-new-jersey/ I'd love to go out with you, but I never go out on days that end in `Y.' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
