Howdy Thomas,
Yes, please do try "true" and disabling the "brute force". If that
resolves the issue for you, obviously it still needs to be understood
how or why it got set to false. On the assumption it does help, the
first suspect in your case is likely going to be btlirc - any chance
you coul
** Attachment added: "AptOrdering.txt"
https://bugs.launchpad.net/bugs/657079/+attachment/1679378/+files/AptOrdering.txt
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/657079/+attachment/1679379/+files/Dependencies.txt
** Attachment added: "Df.txt"
https://bug
Public bug reported:
Binary package hint: lirc
Happened during updates process
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: lirc 0.8.6-0ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Arch
Hi Marc,
I am the author of the bug with brute force work-around, and on my computer the
command ends up with this:
to...@amelie:~$ cat /etc/lirc/hardware.conf | grep START_LIRC
START_LIRCD="false"
#START_LIRCMD="false"
START_LIRCMD=""
If it is necessary, I can try to change it to "true", disabl
Hi Marc,
[ d...@mediapc /etc/lirc ]$ cat hardware.conf | grep START_LIRC
START_LIRCD="true"
#START_LIRCMD="false"
START_LIRCMD=""
Thanks
Dave
--
Can't start lirc: "lircd: can't open or create /var/run/lirc/lircd.pid"
https://bugs.launchpad.net/bugs/474701
You received this bug notification be
To those of you that have encountered this, please report back here if
your hardware.conf file has START_LIRCD="true" or not.
--
Can't start lirc: "lircd: can't open or create /var/run/lirc/lircd.pid"
https://bugs.launchpad.net/bugs/474701
You received this bug notification because you are a memb
If you are running 0.24 and still running into this problem after
investigating the items I outlined above, then it would be good for
you to collect as much information as possible - upstream is still
very focused on 0.24 and I am sure would like to fix this issue.
--
Video frame buffer failed t
I've attached the logs - this is a pretty new install, only a couple of
weeks old.
Thanks,
Todd
--
/dev/lirc0 disappeared after upgrade from 2.6.35-20 to -22
https://bugs.launchpad.net/bugs/655512
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscri
** Attachment added: "dpkg log, latest"
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/655512/+attachment/1678949/+files/dpkg.log
--
/dev/lirc0 disappeared after upgrade from 2.6.35-20 to -22
https://bugs.launchpad.net/bugs/655512
You received this bug notification because you are a mem
** Attachment added: "dpkg log, part 2"
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/655512/+attachment/1678950/+files/dpkg.log.1
--
/dev/lirc0 disappeared after upgrade from 2.6.35-20 to -22
https://bugs.launchpad.net/bugs/655512
You received this bug notification because you are a m
** Attachment added: "apt history log, part 2"
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/655512/+attachment/1678948/+files/history.log.1.gz
--
/dev/lirc0 disappeared after upgrade from 2.6.35-20 to -22
https://bugs.launchpad.net/bugs/655512
You received this bug notification becaus
** Attachment added: "apt history log, latest"
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/655512/+attachment/1678947/+files/history.log
--
/dev/lirc0 disappeared after upgrade from 2.6.35-20 to -22
https://bugs.launchpad.net/bugs/655512
You received this bug notification because you
Pushed to my SRU test PPA at https://launchpad.net/~pitti/+archive/sru-
test. Please give it a spin and let me know how it goes. Thanks!
** Changed in: xfce4-session (Ubuntu Maverick)
Status: Triaged => In Progress
** Changed in: xfce4-session (Ubuntu Maverick)
Assignee: (unassigned)
13 matches
Mail list logo
