this happened in the kernel
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fa5dc29c1fcc9151c3bcfd9e291a2899ae15f61d
commit fa5dc29c1fcc9151c3bcfd9e291a2899ae15f61d
Author: Sean Young
Date: Mon Nov 21 19:55:53 2016 -0200
[media] lirc_serial: move out of stagin
Hello, this works correctly here, please try to be more verbose
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1685646
@jyoder are you still working on it?
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/441150
Title:
Please support auto-detection, à la gnome-lirc-properties
Status in lirc package in U
** Changed in: lirc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/591441
Title:
default config file directory is wrong for lircd
** Changed in: lirc (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/441150
Title:
Please support auto-detection, à la gnome-lirc-properties
S
** Changed in: lirc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/783202
Title:
lircmd is not started properly by lirc init scrip
closing
** Changed in: lirc (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/204960
Title:
[Hardy] Lirc devinput (linux-input-layer) broken
closing then
** Changed in: lirc (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/206495
Title:
hvr-1100 is not configured properly
Status
** Summary changed:
- Yakkety version of transcode needed (removal causes unmet depdendencies)
+ Yakkety version of transcode needed (removal causes unmet dependencies)
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to MythTV.
https://bu
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
marking as fix released due to comment 5
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/454586
Title:
package lirc 0.8.6-0ubuntu2 kernel oops on removal
Status in lirc package in Ubu
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
Hi, can you please try again with the latest lirc from zesty (a.k.a. upcoming
17.04 version), and set the status back to "new" in case you still experience
such issue?
You can also try it from my ppa, where I backported it to xenial and yakkety
releases (16.04 and 16.10)
https://launchpad.net/~c
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to li
You can also try it from my ppa
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/996953
Title:
lirc
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to li
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed
I agree, I tested lirc in a pbuilder chroot environment
** Changed in: lirc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1092677
Title:
C
** Package changed: lirc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1247410
Title:
lirc not working / kernel bug
Status in Linux:
New
Status in linux
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to li
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed
please try again with the latest lirc from zesty, and set the status
back to "new" in case you still experience such issue
** Changed in: lirc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to li
** Changed in: lirc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1203483
Title:
package lirc 0.9.0-0ubuntu3 failed to install/upgrad
grep irexec . -R |grep sbin
./systemd/irexec.service:ExecStart=/usr/sbin/irexec /etc/lirc/irexec.lircrc
this seems a bug indeed
sbin_PROGRAMS = lirc-lsplugins
bin_PROGRAMS= ircat \
irexec \
** Changed in: lirc (Ubuntu)
Status: New => Confir
outdated lirc version
** Changed in: lirc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1637606
Title:
package liblirc-client0 0.9.4c-1 failed
Install: libebur128-1:amd64 (1.1.0-1, automatic), liblirc-client0:amd64
(0.9.4c-1, automatic)
outdated and broken lirc version
** Changed in: lirc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to
maybe you had the broken version still around your system.
now that the fix landed on updates, I guess only people who did the upgrade
yesterday between 10 hours where the package was buggy might suffer from this
bug.
(and meh, it is not even alpha, so I won't try to debug it further, unless more
why? there is no liblircclient in Ubuntu at all
rmadison liblircclient
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1636775
Title:
package liblirc-client0 (not installed) failed to i
Fixed yesterday, with the 0.9.4c-1ubuntu1 upload
** Changed in: lirc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1636775
Title:
pa
Graham syncd it, and it built correctly
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1630453
Title:
[Yakkety +1] Sync lirc 0.9.4b-0.1 (main) from Debian experimental
(main)
Status
@jbicha, I uploaded it on my ppa, and I'll upload in experimental as soon as
ftpmaster is back
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/costamagnagianfranco-ppa/+packages
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed
I hope to fix the FTBFS soon, I already asked the maintainer
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1630453
Title:
[Yakkety +1] Sync lirc 0.9.4b-0.1 (main) from Debian experime
Public bug reported:
[Yakkety +1] Please sync lirc 0.9.4b-0.1 (main) from Debian experimental
(main)
Explanation of the Ubuntu delta and why it can be dropped:
* Multiarchify the library packages.
* Multiarchify the library packages.
* debian/lirc.postinst, debian/lirc.templates, debian/po:
Hi, can anybody let this package migrate?
autopkgtest for dbconfig-common 2.0.4: amd64: Regression ♻ , armhf: Regression
♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
currently 4 packages are blocked because of it:
gnash
boinc
vtk
mythtv
--
You received this bug notifica
70 matches
Mail list logo
