No it is not after all... This is the reason we needed to stop GDM... :) To find if this is an exclusive access problem on gdm or not... Obviously lirc is just not configured properly.
You are basing your ir remote on event6 (which could change simply by re-arranging hardware or even on startup...) What you need to do is reconfigure LIRC. sudo dpkg-reconfigure lirc Make sure you select the correct input device for your video card / remote control. You are getting an exclusive access problem probably on the wrong hardware (**event 6) Try this: When configuring lirc, ensure that you choose /dev/by-path/pci*****IR**** I can't remeber the exact path for this setting, but it will come up in the list when you reconfigure lirc... with ****IR**** I mean to try and find the device that has the IR specified in it. Good Luck! On Mon, Mar 30, 2009 at 9:37 AM, k0per.nik <aca.blago...@gmail.com> wrote: > Well, this command seems to do nothing but stopping GDM from working! When > I type 'irw' still nothing happens! > Let me demonstrate you changes in daemon log: > > when I type 'sudo /etc/init.d/lirc restart' I get: > > Mar 30 08:27:39 gryphon lircd-0.8.3[8823]: caught signal > Mar 30 08:27:40 gryphon lircd-0.8.3[9102]: lircd(userspace) ready > > then I type 'irexec' and get: > > Mar 30 08:27:47 gryphon lircd-0.8.3[9102]: accepted new client on > /dev/lircd > Mar 30 08:27:47 gryphon lircd-0.8.3[9102]: initializing '/dev/input/event6' > > then I type 'irw' and get: > > Mar 30 08:30:37 gryphon lircd-0.8.3[9102]: accepted new client on > /dev/lircd > > but when I press buttons on my remote, I still get no output! > > Maybe the problem I have is not associated with this bug in any way! > > -- > lirc based applications can not get exclusive access to /dev/input > interface > https://bugs.launchpad.net/bugs/164627 > You received this bug notification because you are a direct subscriber > of the bug. > -- lirc based applications can not get exclusive access to /dev/input interface https://bugs.launchpad.net/bugs/164627 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
