[Bug 1843988] Re: python library installed into site-packages instead of into dist-packages
You are indeed right. Python libraries are not multilib, and should live in /usr/lib/python3/site-packages. Will fix, but the process starts at the Debian side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843988 Title: python library installed into site-packages instead of into dist- packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1843988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832885] Re: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1
The core issue here is the dependency in vdr. There is a ticket [1] about this. Otherwise, the simple work-around is uninstall the lirc package. This is an old bug. I see no new reports or comments lately, which seems to indicate that it is fixed in current release. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012274 ** Bug watch added: Debian Bug tracker #1012274 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012274 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832885 Title: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1832885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768291] Re: lirc is flooding the syslog with two lines each second
Filed vdr issue: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1012274 ** Bug watch added: Debian Bug tracker #1012274 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012274 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768291 Title: lirc is flooding the syslog with two lines each second To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1768291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843988] Re: python library installed into site-packages instead of into dist-packages
Sorry for late reply. The python module contains binary. architecture-dependent code and can for that reason not be installed in /usr/lib/python3/ due to overall multi-arch requirements. That said, the official Debian documents I find are not explicit on how to install these kind of modules. Sending a message to debian-devel in an attempt to get this sorted out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843988 Title: python library installed into site-packages instead of into dist- packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1843988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768291] Re: lirc is flooding the syslog with two lines each second
lirc does not spam the log if correctly configured. The repeated messages is a actually a feature since it's an easy way to detect status when configuring and hot-plugging a device. The basic issue here is if lirc is pulled in as a dependency. It should not, it's designed to be used by users which actually have the need. The only rdepends I find in Sid is a Recommends in the vdr package. I'll file an issue about that. Once this is fixed, no-one will have lirc installed "by accident" so to speak. For users which does not use lirc there are two options. One is to remove the package completely, this should be possible on all installations since there are no hard rdepends, just a Recommends in the vdr package. The other is to disable lircd.socket and lircd.uinput using systemctl. This is nothing special, it's standard system service configuration. Besides the R: lirc in the vdr package I thus still don't see any actual bug here. What *could* be considered is to add some info to the logged message about disabling services to get rid of it. Allowing a unused service to continue to run as root without spamming the log is wrong for security and performance reasons. Hence, just writing the log message once is IMHO not a viable alternative. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768291 Title: lirc is flooding the syslog with two lines each second To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1768291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778569] Re: ir-keytable -c -w /etc/rc_keymaps/file
Late comment: vlc does not depend on lirc any more, so this should not happen to new installations. Work around for existing installations is to either remove the lirc package or simply disable lircd.socket, lircd.service and lircd-uinput using systemctl. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778569 Title: ir-keytable -c -w /etc/rc_keymaps/file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1778569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817441] Re: lirc ITE8713 not working
[sorry for late walking through bugs] Have you tried the installation instructions as described in the upstream docs[1] ? [1] https://www.lirc.org/html/configuration-guide.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817441 Title: lirc ITE8713 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1817441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
@gunnarhj: Not least, thanks also to you. Sorry for oversight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
@ddstreet: Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
** Description changed: [Impact] The Kinetic 5.6.2 is the latest upstream release available. In order to keep the official packaging relevant this needs to be backported since users otherwise are relegated the upstream PPA where the packaging is not optimal (no source package, no review, etc). [Scope] This is about backporting opencpn 5.6.2 from Kinetic to Focal/20.04 [Other Info] 5.6.2+dfsg is in Debian Testing/Bookworm. It is also backported to - bullseye/backports and buster/backports. See #1971109 for the + bullseye/backports and buster/backports. See bug 1971109 for the backporting to jammy. Package sources: https://gitlab.com/leamas/opencpn/-/tree/focal- backports - Package is already backported and should be eligible for a regular update like this. - Openpcn is a leaf package, no reverse dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
** Patch added: "Debdiff against kinetic" https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+attachment/5591260/+files/kinetic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
I need a sponsor... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] [NEW] [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
Public bug reported: [Impact] The Kinetic 5.6.2 is the latest upstream release available. In order to keep the official packaging relevant this needs to be backported since users otherwise are relegated the upstream PPA where the packaging is not optimal (no source package, no review, etc). [Scope] This is about backporting opencpn 5.6.2 from Kinetic to Focal/20.04 [Other Info] 5.6.2+dfsg is in Debian Testing/Bookworm. It is also backported to bullseye/backports and buster/backports. See #1971109 for the backporting to jammy. Package sources: https://gitlab.com/leamas/opencpn/-/tree/focal- backports - Package is already backported and should be eligible for a regular update like this. - Openpcn is a leaf package, no reverse dependencies. ** Affects: opencpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
@ddstreet: Thanks for review and uploading! Will try to remember. Next opportunity is backporting 5.6.2 to focal.,.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
As for 1): My initial description could and should have been better. I'm actually not aware of bugs that can and should be fixed by point patches. That is, the description is wrong. The core problem the backport tries to address is that OpenCPN users (thousands, for sure) are accustomed to using a PPA [1] These packages are not really "packaged" in the sense we are used to, there is no source package, no review, etc -- it's basically the auto-generated output from cmake/cpack. However, the PPA is up to date with the latest releases. If we want to offer proper repos instead, backports are necessary to make the official packaging useful. Until we get this running there are no issues reported through the Ubuntu channels. If I look in upstream there are of course all sorts of problems which are solved by latest release. But I honestly don't (yet) see the value of point-patching any of these. Of course, user input in upstream or here might change the situation. I am certainly prepared to handle this by updating the 5.6.0 package if/when the situation occurs. On a sidenote, 5.6.2 is backported not only to Bullseye but also Buster. [1] https://launchpad.net/~opencpn/+archive/ubuntu/opencpn -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
To start with 2): Application downloads plugins from external sources. There are not that many plugins available for jammy yet, and the Focal plugins are actually compatible so the patch makes these plugins available also for Jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
Ah, right. And yes, we want that patch. Sorry for the mess. Need to improve... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
My bad, sorry, still learning. It is not until now I understand the role of the debdiff, that this is what you as sponsor upload. These two debdiffs are basically the same thing compared to different baselines. However, "my" diff is probably far easier to review being much smaller. If this is reason enough to upload that instead is something I cannot judge. Likewise, I don't know whether it is acceptable to use such a diff in this context. So, in the end, which diff to use is really something I must leave in your hands. Have still another backport one in my plans, kinetic -> focal. But I waited to file this until I had been through this process once more. Will not forget the debdiff next time, promise! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
Hm... are you confused by the fact that the diff in the upload queue is against 5.6.0+dfsg1-1 (huge!) whereas the debdiff here is against kinetic i. e., 5.6.2+dfsg-1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
Hej Gunnar, On 07/05/2022 15:28, Gunnar Hjalmarsson wrote: > Hey, Alec, that debdiff you added differs from what I uploaded. What > now? Should I use the debdiff in a new upload? > Administrativa problem Hur ser din debdiff ut? --alec PS: När skall jag lära mig att bifoga den till ärendet från början? DS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
** Attachment added: "Debdiff against kinetic" https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+attachment/5587227/+files/debdiff.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
** Summary changed: - [BPO] Backport opencpn 5.6.2 from Kinetic + [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic
** Description changed: [Impact] The current release misses several important bugfixes available in the Kinetic 5.6.2 package. Thus it forces users to the PPA at https://launchpad.net/~opencpn/+archive/ubuntu/opencpn. While more recent, this not properly packaged and reviewed, lacking a source package etc. [Scope] This is about backporting opencpn 5.6.2 from Kinetic to Jammy/22.04 [Other Info] - 5.6.2+dfsg is in Debian Testing/Bookworm. The Bullseye backport is - currently awaiting review on mentors.debian.net + 5.6.2+dfsg is in Debian Testing/Bookworm. The Bullseye backport is currently awaiting review on mentors.debian.net + EDIT: The Bullseye backport is accepted Package sources: https://gitlab.com/leamas/opencpn/-/tree/jammy- backports - Package is already backported and should be eligible for a regular update like this. - Openpcn is a leaf package, no reverse dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic
I need a sponsor... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic
Not a WIP any more as far as I know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic
Package update and looks good. Not -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic
This is still a WIP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] [NEW] [BPO] Backport opencpn 5.6.2 from Kinetic
Public bug reported: [Impact] The current release misses several important bugfixes available in the Kinetic 5.6.2 package. Thus it forces users to the PPA at https://launchpad.net/~opencpn/+archive/ubuntu/opencpn. While more recent, this not properly packaged and reviewed, lacking a source package etc. [Scope] This is about backporting opencpn 5.6.2 from Kinetic to Jammy/22.04 [Other Info] 5.6.2+dfsg is in Debian Testing/Bookworm. The Bullseye backport is currently awaiting review on mentors.debian.net Package sources: https://gitlab.com/leamas/opencpn/-/tree/jammy- backports - Package is already backported and should be eligible for a regular update like this. - Openpcn is a leaf package, no reverse dependencies. ** Affects: opencpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@Mattia: Thanks for review and uploading. I guess the review boils down to that while the delta against Jammy is reasonable small it could and should have been smaller. I can nothing but agree. Of course, there are some explanations. Doubt they are interesting, though. If I get this right this was the final roadblock, and the package is now under way without any big delays. Which means that I have completed my first backport after stirring up quite some dust. Hopefully, it might be smoother next time. Thanks to all of you who helped me here: Dan, Hjalmar and Mattia. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@teward, @gunnarhj: Ah, right, this is similar to the Debian process. Looking at that queue is somewhat scary, I see an entry from 2021-10-28. Can just hope this goes faster. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@gunnarhj: Now, it was some days since you sponsored me, thanks for that. However, I still don't see it in focal-backports, at least not when browsing. Is this normal i. e., how long am I supposed to wait before package becomes visible? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@Mattia: OK, will do. Still learning. Seems that having a discussion on ubuntu-devel is fruitful in many ways, though ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
Deleted: Swedish talk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@gunnar: I found the bogus debian/ files. It's in the upstream sources, used for PPA builds. The strange thing is that "gbp buildpackage" works without problems which has made the package sail through all Debian checks. Anyway, the package is repackaged, so it's just to add debian to the directories to strip. Will do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@Gunnar: Man tackar (a. k. a. thanks for sponsoring)! > Please unsubscribe ~ubuntu-sponsors from this bug. Done > One oddity is that the orig.tar.xz file includes a debian/ folder WTF?! Something is rotten in pristine-tar, will check again. Thanks for notifying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@dan: I can understand if this thing take too much time for you. I'm just a newbie which runs into obstacles others doesn't know about -- that's what newbies do. Also, this discussion does not really belong to the issue. Should we start a thread on ubuntu-devel instead, to get more eyes on it? Continue here? or? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
Turns out that this application process is a interesting chicken and egg problem ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
Havn't tried that one, doing it now... result: "You are not allowed to edit this page." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
> Since you have a LP account, I'm pretty sure you should be able to create a wiki page for yourself. Nope. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
I guessed something like that. However, to be able to do it I need to be member of the Ubuntu Wiki Editors Team. My application for that is pending: https://launchpad.net/~ubuntu-wiki-editors. I have so far tried to learn the virtue of patience in the Debian community. I have my background in Fedora, and the longish Debian processes is, well, fostering your character. Guess Ubunti is the same... Thanks for all support! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
I'll try to make an application. F -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
...irst step is to become member of the wiki group. Waiting for that,,, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
Sllly me read on the wrong place. Sigh. And thanks. But the devil is in the details. That paragraph links to the process described in https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess. But there is no description for this case. Any idea how this application should be done? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
hm... when I read https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess, the "Debian Developers applying for Per-Package upload rights" paragraph, the first sentence is "The DMB has establised a procedure for interested Debian Developers to gain upload rights to their packages" As I read this, it's pretty clear. But I could of course be wrong, and so can of the documentation. Thoughts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@Dan: thanks for input, just what I needed. PPU rights... I first need to become a DD. I have so far said no to this, but is about to reconsider. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
@Dan: Thanks for review! > While Debian uses 'Closes:', Ubuntu uses 'LP:', so this should be Done > technically, debhelper 13 is in focal-backports (and even bionic- backports), but if you don't actually need level 13 it's fine to reduce it in the backport. Actually, it turns out the I did need it in a way. I had dropped override_dh_missing which is default in 13 but not in 12. It's now back in place, and the compat-level == 12 is OK as far as I can see. > I see focal has opencpn-plugins_5.0.0+dfsg-1_all.deb, which is a dummy transitional package, but there's no corresponding opencpn-plugins package in later releases. Good catch, which my Debian reviews missed... Anyway, I followed your advice and made the Breaks: and Replaces: unconditional. Update smoke test seems OK. > If not you may need to find a sponsor Yes, I need a sponsor; assuming this is the hard part. Had one contact (Gianfranco) but he seems unavailable. Is there a formal process for getting in touch with a sponsor, like the mentors site and RFS bugs in Debian? Or should I drop a mail in the ubuntu-backports mailnig list? Or? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
FWIW, the corresponding Debian backport to bullseye-backports is accepted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport 5.6.0 from Jammy
Adding the Debian backport checklist - Current version is two versions behind. As a result, upstream directs all users to the PPA, a packaging which does not meet basic standards. Ergo: backporting is meaningful. - The package has a substantial user base although this for now means the PPA users. - Package is available in Debian Bookworm and Jammy. - Opencpn is a leaf package, no reverse dependencies. - No other Ubuntu backports exist. - I also maintain the Debian package and is also fairly active in the upstream project. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport 5.6.0 from Jammy
** Description changed: [Impact] The current release is so old that it is unusable. Thus it forces users to the PPA at https://launchpad.net/~opencpn/+archive/ubuntu/opencpn. While more recent, this not properly packaged and reviewed, lacking a source package etc. [Scope] This is about backporting 5.6.0 from Jammy to Focal/20.04 [Other Info] 5.6.0 is in Debian Testing. The Bullseye backport is currently in the backports new queue. + + Package sources: https://gitlab.com/leamas/opencpn/-/tree/focal- + backports -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport 5.6.0 from Jammy
** Patch added: "Debdiff against jammy" https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+attachment/5550319/+files/opencpn.debdiff ** Description changed: [Impact] - The current release is so old that it is unusable. Thus it forces users to the - PPA at https://launchpad.net/~opencpn/+archive/ubuntu/opencpn. While more recent, - this not properly packaged and reviewed, lacking a source package etc. + The current release is so old that it is unusable. Thus it forces users + to the PPA at https://launchpad.net/~opencpn/+archive/ubuntu/opencpn. + While more recent, this not properly packaged and reviewed, lacking a + source package etc. [Scope] This is about backporting 5.6.0 from Jammy to Focal/20.04 + [Other Info] - [Other Info] - - 5.6.0 is in Debian Testing. The Bullseye backport is currently in the backports new queue. + 5.6.0 is in Debian Testing. The Bullseye backport is currently in the + backports new queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] [NEW] [BPO] Backport 5.6.0 from Jammy
Public bug reported: [Impact] The current release is so old that it is unusable. Thus it forces users to the PPA at https://launchpad.net/~opencpn/+archive/ubuntu/opencpn. While more recent, this not properly packaged and reviewed, lacking a source package etc. [Scope] This is about backporting 5.6.0 from Jammy to Focal/20.04 [Other Info] 5.6.0 is in Debian Testing. The Bullseye backport is currently in the backports new queue. ** Affects: opencpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/comments/16 is a beginning... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791409] Re: LIRC not working on Ubuntu 18.04
Basically, it isn't buggy but requires manual intervention when updating. A script called lirc-setup is however broken. It's primary use-case is fresh installs rather than updates which have no need for it. A workaround to make it wotk could be found in comment #2. Some users have had problems with duplicated keys caused by the lirc- uinput.service running. Stopping the service fixes this (it is not enabled by default in recent updates). However, the main problem is users claiming that lirc should work as before without changes after a fully unattended update. I have done what I can to describe that this is not the case... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791409] Re: LIRC not working on Ubuntu 18.04
> I suppose it is a bug, as lirc should work after upgrade without manual reconfiguration. No it should not, as apparent if you read the comkplete discussion in this bug or, more on the spot, bug #1788235. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791409] Re: LIRC not working on Ubuntu 18.04
That said, if someone filed a bug against lirc because lirc-setup is broken, that bug is certainly valid. But IMHO, that's a very different story. And since there is a usable work-around it would probably just be closed as fixed upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791409] Re: LIRC not working on Ubuntu 18.04
The main issue described in this bug is bogus, as apparent from bug #1788235 However, the configuration script lirc-setup *is* indeed broken . This is fixed in Debian upstream from 0.10.1, but hasn't trickled down. That said, users will still need to read README.Debian, and the process to configure lirc is still very different from what it used to be. Also, most users updating does not need lirc-setup. I'm considering closing this bug as a duplicate or just invalid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
> Kodi definitely works with the latest versions of Lirc and the problem i > is very easy to fix so stop downgrading your systems to an older version of > Lirc Right. > The problem is Kodi defaults to looking for a Lirc socket at /dev/lircd which > doesn’t exist anymore. Has anyone cared to file a bug against kodi on this? > 3. Modify the /lib/systemd/system/lircd.service to create a symlink > from /dev/lircd to /var/run/lirc/lircd each time the lircd.service or > system is restarted: Please, no. The files in /lib/systemd/system should not be tampered with, they are replaced on package update without mercy. Instead, copy /lib/systemd/system/lircd.service to /etc/systemd/system and modify that copy (it overrides the /lib/systemd one). Also note that lirc_options.conf supports code: stanzas which are executed as root before lircd is launched. Linking could be done here instead of patching the service file. And, finally: the /dev directory is just not aimed for this kind of files, it's supposed to be handled by udev. So, creating links here should be avoided if at all possible. > e.g: sudo systemctl disable lircd-uinput.service Indeed. Debian upstream by default disables this service in last update. Using 'systemctl disable --now lircd-uinput.service' is probably the best to both stop and disable. > What I still cannot get working is the lirc-setup app (which replaces dpkg-reconfigure lirc) Also this is fixed in debian upstream. Until it trickles down, the dirty work-around is something like: # libdir=/usr/lib/x86_64-linux-gnu/python3.6/site-packages # cp /usr/share/lirc/python-pkg/config.py $libdir/lirc # ln -s $libdir/lirc /usr/lib/python3/dist-packages/ # ln -s $libdir/lirc-setup /usr/lib/python3/dist-packages/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778569] Re: ir-keytable -c -w /etc/rc_keymaps/file
To further investigate this issues, a question is if the main lirc package is installed. If so, the lircd.socket, lircd.service and lircd- uinput.services should be disabled and stopped. If problem persists, with or without liblircclient installed, this should be re-assigned to the kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778569 Title: ir-keytable -c -w /etc/rc_keymaps/file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1778569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791409] Re: LIRC not working on Ubuntu 18.04
This is fixed in debian upstream. Until this trickles down, the walk- around is something like # libdir=/usr/lib/x86_64-linux-gnu/python3.6/site-packages # cp /usr/share/lirc/python-pkg/config.py $libdir/lirc # ln -s $libdir/lirc /usr/lib/python3/dist-packages/ # ln -s $libdir/lirc-setup /usr/lib/python3/dist-packages/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
So, changing status. @xekon: dpkg-reconfigure doesn't do anything at all... ** Changed in: lirc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
> @»ekon, @Alec, thanks for your comments, reading those it looks like you are stating that there is no real bug, just that the changes in the software and its configuration files confused users that were used to the old way? E.g nothing that needs to be resolved? Right, from my point of view this should be closed as not-a-bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
@seb128: The missing UI refers to the reconfiguration UI which was part of lirc up to 0.9.0. This reflected even older code containing kernel modules where lirc was rebuilt from source depending on configuration. Nowadays lirc is a just a server with configuration files and there is no need to make anything special at configuration time. There are new tools available to assist in configuration, but these can and should be used after installation. Bottom line seems to be that the expectation was that nothing is changed. However, it is. The decision to make a breaking change was not taken lightly, it actually took several years, but eventually it became necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
Seems that we agree that the idea that lirc as of 18.04 is "broken" is plain wrong. The problem is about making a correct upgrade which involves manual steps as described in README.Debian (with a notification in the upgrade message). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
> Is there more documentation at a website that I could read to learn more? The official site is http://lirc.org. Among other things, here is an updated Configuration Guide. > I am particularly interested in the info about the raw events from the socket. At the same site there is info on the APIs, in particular the Client API. The problem is that Kodi uses the raw events (documented in lircd(8)) instead of using that API. Changing this in a stable application as Kodi requires some serious thinking to not break existing setups -- using the proper client API functionality must basically be opt-in, I guess. That said, scanning the docs will reveal the functionality in the API which is missing in the raw socket interface. The first step should be to file a bug against Kodi for not using the API and the corresponding loss of lirc functionality (and, ironically, added configuration complexity). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
> While I am sure LIRC has a lot of uses. I would wager 90% of its users are using kodi. This might be the truth as seen from the kodi community. However, from an upstream lirc point of view I cannot really see that the number of kodi users are dominating in any way. > forgot a couple steps, here was all of them: While these steps worked for you, other users will have other needs. That said, disabling/stopping lircd-uinput might be a good idea in many cases. The last update to lirc has it disabled by default. > also some discussion here: https://forum.kodi.tv/showthread.php?tid=324727 That discussion is utterly confused and does not mention the need to migrate (manual or automatic) the old 0.9.0 setup to the new one. Also, some users in that thread are using the default driver while other seem to be using the devinput one. No one seems to be reading the documentation, but still seems to be able to establish the "fact" that lirc is broken. If it was possible to file a bug against the Kodi community overall I would consider doing that ;) On top of that Kodi is the one and only application which misuses lirc by using the raw events from the socket -- this makes lirc seriously crippled compared to the real stuff. I filed a bug on this long ago, but at a glance it seems to be lost. Unless there is more input I will close this as not-a-bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
Now, considering these reports one cannot IMHO really say that lirc is 'broken'. What could be said is that the upgrade to the new version requires manual steps, none of which mentioned in this report. The manual steps are documented in the file /usr/share/doc/lirc/README.Debian.gz -- this is presented in the upgrade message for lirc. >From xekon's note it's clear that the new lirc installation is using the default setup. It just cannot work as expected. However, the documentation is pretty clear and there is even a migration script. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685394] Re: hp media center remote not responding
Oops... seems that the default lircd.conf only requires .conf suffix, not lircd.conf. All solved, my bad. ** Changed in: lirc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685394 Title: hp media center remote not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1685394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685394] Re: hp media center remote not responding
Glad that it works for you. The question is just how... As noted in the README, from 0.9.4 all lircd.conf files needs names like mce.lircd.conf i. e., with a lircd.conf suffix. The default lircd.conf files only includes files with this suffix. That said, a custom lircd.conf could of course include anything. Given the overall situation, this is more like a support request than a bug, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685394 Title: hp media center remote not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1685394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685646] Re: 'dpkg-reconfigure lirc' doesn't work as expected.
The package contains a README.Debian.gz file which explains the changes done. A reference to this file was displayed when you upgraded lirc, but perhaps you missed it (such things happens, for sure). The update 0.9.0 -> 0.9.4 is a breaking update requiriung manual intervention as described in this file. Have you read it and performed the manual steps described therein? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685646 Title: 'dpkg-reconfigure lirc' doesn't work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1685646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685394] Re: hp media center remote not responding
At a closer look, the configuration seems messy. E. g., /etc/lirc/lirc.conf includes a file from /usr/share/lirc/configs, a directory not present in 0.9.4. Have you worked through the necessary manual upgrade steps as described in /usr/share/doc/lirc/README.Debian.gz? Note that the missing remotes in /usr/share/lirc/configs are available in the lirc-compat-remotes packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685394 Title: hp media center remote not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1685394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685646] Re: 'dpkg-reconfigure lirc' doesn't work as expected.
Previous versions needed some configuration to basically make a conditional compilation. Possibly, submitter expects the configuration menu as of 0.9.0. However, there is no such menu in 0.9.4 - all configuration is done after installation using regular configuration files Given this, my provisionary conclusion is that this should be closed as not-a-bug unless there is more input. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685646 Title: 'dpkg-reconfigure lirc' doesn't work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1685646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4
For the sake of order, this bug should be re-assigned to the kernel package instead of the user-space lirc package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 206495] Re: hvr-1100 is not configured properly
This bug is 8 years old, The primary culprits hald and hardware.conf are gone and this bugf shouldI MHO be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206495 Title: hvr-1100 is not configured properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/206495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358817] Re: Add irexec,irxevent,... to session
So,I'm not allowed set it to wontfix. Setting Incomplete, please change you don't want this bug to be closed. ** Changed in: lirc (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/358817 Title: Add irexec,irxevent,... to session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/358817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 934023] Re: mceusb remote stops working after lucid->precise upgrade
Setting Incomplete to let bug expire. Please change if you don't wan bug to expire- ** Changed in: lirc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934023 Title: mceusb remote stops working after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/934023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358817] Re: Add irexec,irxevent,... to session
After a second thought I think this is wontfix. Setting up lirc is a complex task, and enabling a service in the standard session GUI tools is a small problem compared to other. Also, the 'parse .lircrc'approach just don't work since applications can store them anywhere. And does so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/358817 Title: Add irexec,irxevent,... to session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/358817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Re-assigning to kernel - this is teh way to clarify whether it's a bug or just documented behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204769] Re: /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in hardware.conf
Closing as fixed, since release 0.9.4c does not use sysV scripts or hardware.conf. ** Changed in: lirc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/204769 Title: /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in hardware.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/204769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Now, suspend-resume is about the kernel, the extra modules secion. But which iof them? Just don't know. ** Package changed: lirc (Ubuntu) => linux-lts-xenial (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505705] Re: irexec isn't started automatically on existing installs
As for the lirc part, the last 0.9.4 release solves this since the lircd output socket is created at an very early point in the boot sequence. lircd is started using socket activation when irexec or some otther client connects to the socket. So, no race is possible. IMHO, mysql should do the same, and might indeed have so already. Don't know, closing as fixed. ** Changed in: lirc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/505705 Title: irexec isn't started automatically on existing installs To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/505705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 786743] Re: Lack of support for Multiple receivers
This do belong to mythbuntu since it's about the automatic generation of config files. Still unsure which of the mythbuntu packages, sorry. ** Package changed: lirc (Ubuntu) => mythbuntu-common (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/786743 Title: Lack of support for Multiple receivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythbuntu-common/+bug/786743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 786743] Re: Lack of support for Multiple receivers
At second thogt this is a mythbuntu issue, re-assigning. Please note that that from 0.9.4 lirc no longer supports hardware.conf. In short, each lircd instance is configured as a systemd service. There is also a ren lirc_options.conf file which defines default values for command line options. See upstream documentation at http://lirc.org. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/786743 Title: Lack of support for Multiple receivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythbuntu-common/+bug/786743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 517743] Re: Check the TRANSMITTER logic for errors w/ lirc-mceusb
The last release 0.9.4c dos not support hardware.conf anymore, so this is bug is obsoleted. Closing as "FixReleased", short of better options. ** Changed in: lirc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/517743 Title: Check the TRANSMITTER logic for errors w/ lirc-mceusb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/517743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330203] Re: Add Winfast 2000XP ir remote settings to lirc
The last version of lirc 0.9.4c sort of resolves this problem by not bundling the remote definitions. From 0.9.2+, the remote definitions lives at http://sf.net/p/lirc-remotes. Closing bug as fixed. lirc (0.9.4b-0.1) experimental; urgency=medium * Non-maintainer upload. * First shot on major upstream updates. - Re-packaged from scratch based on new dh primitives. - Thanks for help on debian-mentors! * New upstream release 0.9.4 - Release 0.9.1 .. 0.9.3 was never packaged. - Old 'lirc' service split into separate systemd services: lircd.service, lircmd.service and irexec.service. - Remote definitions moved out of lirc to new project lirc-remotes; affects large number of LP issues. - Builds also on FreeBSD 10.3. - Fixes "Not updated to last version" (Closes: #777199), LP: #1443590. - Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140). - Fixes "/var/run/lirc contents disappear..." (Closes: #676343). - Fixes "lircrcd segfaults" (Closes: #780062). - Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091). - Fixes "Prompting due to modified conffiles..." (Closes: #655969). - Fixes "LIRC installs bad udev rule" (Closes: #804397), users depending on this rule will need to explicitly start lircd. - Fixes "lirc init script can create circular symlinks", LP: #698007. - Fixes "Update Uploaders List (Closes: #762554). - Fixes "Please switch to libftdi1" (Closes: #810370). - Fixes LP: #153457 "iguanaIR support not functional". - Fixes LP: #460027 "using lirc init script restart function fails sometimes". - Fixes LP: #499588 "lirc udev rule causes unreliable startup". - Fixes LP: #567519 "lircd(8) mentions non-existent /dev/input/uinput". - Fixes LP: #1029604 "mce remote doesn't work due to out of date lircd.conf.devinput". - Fixes LP: #1312287 "lircd start problem". * The built-in irman support is moved to the lirc-drv-irman package. * Revised package structure: keep old liblircclient0 (renamed to liblirc-client0). Adding new packages liblirc0, liblirc-dev and lirc-doc. Former liblircclient-dev merged into new liblirc-dev. * Don't overwrite existing lircd.conf file. * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann] * Add handling of obsolete 0.9.0 udev rule restarting lircd * Old lircd output socket link /dev/lirc dropped. Use /var/run/lirc/lircd. * Updated copyright * Update compiler flags: -Wl,as-needed + hardening [Stefan Lippers-Hollmann] * Avoid negative architecture deps like [!hurd] (Closes: #634807) [Stefan Lippers-Hollmann] * Add patch 0007-tools-remove-configs-symlink.patch + explicit link to walk around #801719 (dh_python3 shortcomings). * Last parts of libirman dependencies removed. * Changing Vcs-* headers to point to upstream packaging branch. * Fixes existing large number of upgrade bugs. * Enhance hardening flags. * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg therein. * Tested (build-wise) on stretch and sid. -- Alec Leamas <leamas.a...@gmail.com> Thu, 26 May 2016 11:14:25 +0100 ** Changed in: lirc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/330203 Title: Add Winfast 2000XP ir remote settings to lirc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/330203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334144] Re: [Intrepid AMD64] lirc daemon fails to load at startup
Anyway, we believe this is fixed in last update lirc-0.9.4c: - The udev rule restarting lircd when /dev/lirc0 is created is removed. - 0.9.4 sports a much simpler systemd setup, which certainly can have problems but not this. Closing lirc (0.9.4b-0.1) experimental; urgency=medium * Non-maintainer upload. * First shot on major upstream updates. - Re-packaged from scratch based on new dh primitives. - Thanks for help on debian-mentors! * New upstream release 0.9.4 - Release 0.9.1 .. 0.9.3 was never packaged. - Old 'lirc' service split into separate systemd services: lircd.service, lircmd.service and irexec.service. - Remote definitions moved out of lirc to new project lirc-remotes; affects large number of LP issues. - Builds also on FreeBSD 10.3. - Fixes "Not updated to last version" (Closes: #777199), LP: #1443590. - Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140). - Fixes "/var/run/lirc contents disappear..." (Closes: #676343). - Fixes "lircrcd segfaults" (Closes: #780062). - Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091). - Fixes "Prompting due to modified conffiles..." (Closes: #655969). - Fixes "LIRC installs bad udev rule" (Closes: #804397), users depending on this rule will need to explicitly start lircd. - Fixes "lirc init script can create circular symlinks", LP: #698007. - Fixes "Update Uploaders List (Closes: #762554). - Fixes "Please switch to libftdi1" (Closes: #810370). - Fixes LP: #153457 "iguanaIR support not functional". - Fixes LP: #460027 "using lirc init script restart function fails sometimes". - Fixes LP: #499588 "lirc udev rule causes unreliable startup". - Fixes LP: #567519 "lircd(8) mentions non-existent /dev/input/uinput". - Fixes LP: #1029604 "mce remote doesn't work due to out of date lircd.conf.devinput". - Fixes LP: #1312287 "lircd start problem". * The built-in irman support is moved to the lirc-drv-irman package. * Revised package structure: keep old liblircclient0 (renamed to liblirc-client0). Adding new packages liblirc0, liblirc-dev and lirc-doc. Former liblircclient-dev merged into new liblirc-dev. * Don't overwrite existing lircd.conf file. * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann] * Add handling of obsolete 0.9.0 udev rule restarting lircd * Old lircd output socket link /dev/lirc dropped. Use /var/run/lirc/lircd. * Updated copyright * Update compiler flags: -Wl,as-needed + hardening [Stefan Lippers-Hollmann] * Avoid negative architecture deps like [!hurd] (Closes: #634807) [Stefan Lippers-Hollmann] * Add patch 0007-tools-remove-configs-symlink.patch + explicit link to walk around #801719 (dh_python3 shortcomings). * Last parts of libirman dependencies removed. * Changing Vcs-* headers to point to upstream packaging branch. * Fixes existing large number of upgrade bugs. * Enhance hardening flags. * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg therein. * Tested (build-wise) on stretch and sid. -- Alec Leamas <leamas.a...@gmail.com> Thu, 26 May 2016 11:14:25 +0100 ** Changed in: lirc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/334144 Title: [Intrepid AMD64] lirc daemon fails to load at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/334144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913527] Re: Remote control "Rosewill RHRC-11001" doesn't work
At a second thought; Since it's now supported, let's close bug ** Changed in: lirc (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: lirc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913527 Title: Remote control "Rosewill RHRC-11001" doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/913527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238032] Re: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc)
expiring manually ** Changed in: lirc (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/238032 Title: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc) To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/238032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663651] Re: Streamzap remote control not operating correctly
Expiring ** Changed in: lirc (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/663651 Title: Streamzap remote control not operating correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567512] Re: uinput broken for at least Mac mini
If/when you do, please file a new bug. This one is too old and cluttered. Closing, as fixed in 0.9.4c lirc (0.9.4b-0.1) experimental; urgency=medium * Non-maintainer upload. * First shot on major upstream updates. - Re-packaged from scratch based on new dh primitives. - Thanks for help on debian-mentors! * New upstream release 0.9.4 - Release 0.9.1 .. 0.9.3 was never packaged. - Old 'lirc' service split into separate systemd services: lircd.service, lircmd.service and irexec.service. - Remote definitions moved out of lirc to new project lirc-remotes; affects large number of LP issues. - Builds also on FreeBSD 10.3. - Fixes "Not updated to last version" (Closes: #777199), LP: #1443590. - Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140). - Fixes "/var/run/lirc contents disappear..." (Closes: #676343). - Fixes "lircrcd segfaults" (Closes: #780062). - Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091). - Fixes "Prompting due to modified conffiles..." (Closes: #655969). - Fixes "LIRC installs bad udev rule" (Closes: #804397), users depending on this rule will need to explicitly start lircd. - Fixes "lirc init script can create circular symlinks", LP: #698007. - Fixes "Update Uploaders List (Closes: #762554). - Fixes "Please switch to libftdi1" (Closes: #810370). - Fixes LP: #153457 "iguanaIR support not functional". - Fixes LP: #460027 "using lirc init script restart function fails sometimes". - Fixes LP: #499588 "lirc udev rule causes unreliable startup". - Fixes LP: #567519 "lircd(8) mentions non-existent /dev/input/uinput". - Fixes LP: #1029604 "mce remote doesn't work due to out of date lircd.conf.devinput". - Fixes LP: #1312287 "lircd start problem". * The built-in irman support is moved to the lirc-drv-irman package. * Revised package structure: keep old liblircclient0 (renamed to liblirc-client0). Adding new packages liblirc0, liblirc-dev and lirc-doc. Former liblircclient-dev merged into new liblirc-dev. * Don't overwrite existing lircd.conf file. * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann] * Add handling of obsolete 0.9.0 udev rule restarting lircd * Old lircd output socket link /dev/lirc dropped. Use /var/run/lirc/lircd. * Updated copyright * Update compiler flags: -Wl,as-needed + hardening [Stefan Lippers-Hollmann] * Avoid negative architecture deps like [!hurd] (Closes: #634807) [Stefan Lippers-Hollmann] * Add patch 0007-tools-remove-configs-symlink.patch + explicit link to walk around #801719 (dh_python3 shortcomings). * Last parts of libirman dependencies removed. * Changing Vcs-* headers to point to upstream packaging branch. * Fixes existing large number of upgrade bugs. * Enhance hardening flags. * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg therein. * Tested (build-wise) on stretch and sid. -- Alec Leamas <leamas.a...@gmail.com> Thu, 26 May 2016 11:14:25 +0100 ** Changed in: lirc (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/567512 Title: uinput broken for at least Mac mini To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/567512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 626633] Re: Missing MCE remote from default config file
The patch is for kernel code, reassigning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/626633 Title: Missing MCE remote from default config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/626633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 597955] Re: LIRC not listed remote: Mediagate MG-IR01BK, Remote model #:RC126, Receiver model #:IR605.
Any news on this? Otherwise, without further input, I suggest this is closed. ** Changed in: lirc (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/597955 Title: LIRC not listed remote: Mediagate MG-IR01BK, Remote model #:RC126, Receiver model #:IR605. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/597955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 626633] Re: Missing MCE remote from default config file
Possibly , wrog version ** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/626633 Title: Missing MCE remote from default config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/626633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150480] Re: lirc needs an upstart init script
This bug is old. The last release 0.9.4c addresses the issues here with a new systemd setup. It also ships updated sysV scripts, split into three services. Closiing lirc (0.9.4b-0.1) experimental; urgency=medium * Non-maintainer upload. * First shot on major upstream updates. - Re-packaged from scratch based on new dh primitives. - Thanks for help on debian-mentors! * New upstream release 0.9.4 - Release 0.9.1 .. 0.9.3 was never packaged. - Old 'lirc' service split into separate systemd services: lircd.service, lircmd.service and irexec.service. - Remote definitions moved out of lirc to new project lirc-remotes; affects large number of LP issues. - Builds also on FreeBSD 10.3. - Fixes "Not updated to last version" (Closes: #777199), LP: #1443590. - Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140). - Fixes "/var/run/lirc contents disappear..." (Closes: #676343). - Fixes "lircrcd segfaults" (Closes: #780062). - Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091). - Fixes "Prompting due to modified conffiles..." (Closes: #655969). - Fixes "LIRC installs bad udev rule" (Closes: #804397), users depending on this rule will need to explicitly start lircd. - Fixes "lirc init script can create circular symlinks", LP: #698007. - Fixes "Update Uploaders List (Closes: #762554). - Fixes "Please switch to libftdi1" (Closes: #810370). - Fixes LP: #153457 "iguanaIR support not functional". - Fixes LP: #460027 "using lirc init script restart function fails sometimes". - Fixes LP: #499588 "lirc udev rule causes unreliable startup". - Fixes LP: #567519 "lircd(8) mentions non-existent /dev/input/uinput". - Fixes LP: #1029604 "mce remote doesn't work due to out of date lircd.conf.devinput". - Fixes LP: #1312287 "lircd start problem". * The built-in irman support is moved to the lirc-drv-irman package. * Revised package structure: keep old liblircclient0 (renamed to liblirc-client0). Adding new packages liblirc0, liblirc-dev and lirc-doc. Former liblircclient-dev merged into new liblirc-dev. * Don't overwrite existing lircd.conf file. * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann] * Add handling of obsolete 0.9.0 udev rule restarting lircd * Old lircd output socket link /dev/lirc dropped. Use /var/run/lirc/lircd. * Updated copyright * Update compiler flags: -Wl,as-needed + hardening [Stefan Lippers-Hollmann] * Avoid negative architecture deps like [!hurd] (Closes: #634807) [Stefan Lippers-Hollmann] * Add patch 0007-tools-remove-configs-symlink.patch + explicit link to walk around #801719 (dh_python3 shortcomings). * Last parts of libirman dependencies removed. * Changing Vcs-* headers to point to upstream packaging branch. * Fixes existing large number of upgrade bugs. * Enhance hardening flags. * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg therein. * Tested (build-wise) on stretch and sid. -- Alec Leamas <leamas.a...@gmail.com> Thu, 26 May 2016 11:14:25 +0100 lirc (0.9.0~pre1-1.2) unstable; urgency=medium ** Changed in: lirc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/150480 Title: lirc needs an upstart init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/150480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
This bug is old. The loast release (0.9.4c - zesty) deals with this. Actually the default configuration (--driver devinput --device auto) should cover the devinput case. Here is also new documentation on how to setup the default driver (also available at http://lirc.org/html/configuration- guide.html. Clsoing. lirc (0.9.4b-0.1) experimental; urgency=medium * Non-maintainer upload. * First shot on major upstream updates. - Re-packaged from scratch based on new dh primitives. - Thanks for help on debian-mentors! * New upstream release 0.9.4 - Release 0.9.1 .. 0.9.3 was never packaged. - Old 'lirc' service split into separate systemd services: lircd.service, lircmd.service and irexec.service. - Remote definitions moved out of lirc to new project lirc-remotes; affects large number of LP issues. - Builds also on FreeBSD 10.3. - Fixes "Not updated to last version" (Closes: #777199), LP: #1443590. - Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140). - Fixes "/var/run/lirc contents disappear..." (Closes: #676343). - Fixes "lircrcd segfaults" (Closes: #780062). - Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091). - Fixes "Prompting due to modified conffiles..." (Closes: #655969). - Fixes "LIRC installs bad udev rule" (Closes: #804397), users depending on this rule will need to explicitly start lircd. - Fixes "lirc init script can create circular symlinks", LP: #698007. - Fixes "Update Uploaders List (Closes: #762554). - Fixes "Please switch to libftdi1" (Closes: #810370). - Fixes LP: #153457 "iguanaIR support not functional". - Fixes LP: #460027 "using lirc init script restart function fails sometimes". - Fixes LP: #499588 "lirc udev rule causes unreliable startup". - Fixes LP: #567519 "lircd(8) mentions non-existent /dev/input/uinput". - Fixes LP: #1029604 "mce remote doesn't work due to out of date lircd.conf.devinput". - Fixes LP: #1312287 "lircd start problem". * The built-in irman support is moved to the lirc-drv-irman package. * Revised package structure: keep old liblircclient0 (renamed to liblirc-client0). Adding new packages liblirc0, liblirc-dev and lirc-doc. Former liblircclient-dev merged into new liblirc-dev. * Don't overwrite existing lircd.conf file. * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann] * Add handling of obsolete 0.9.0 udev rule restarting lircd * Old lircd output socket link /dev/lirc dropped. Use /var/run/lirc/lircd. * Updated copyright * Update compiler flags: -Wl,as-needed + hardening [Stefan Lippers-Hollmann] * Avoid negative architecture deps like [!hurd] (Closes: #634807) [Stefan Lippers-Hollmann] * Add patch 0007-tools-remove-configs-symlink.patch + explicit link to walk around #801719 (dh_python3 shortcomings). * Last parts of libirman dependencies removed. * Changing Vcs-* headers to point to upstream packaging branch. * Fixes existing large number of upgrade bugs. * Enhance hardening flags. * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg therein. * Tested (build-wise) on stretch and sid. -- Alec Leamas <leamas.a...@gmail.com> Thu, 26 May 2016 11:14:25 +0100 ** Changed in: lirc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/787735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663497] Re: Transmitter (irsend) broken in 10.10
indeed the kernel,media subsystem,possibly wrong version ** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/663497 Title: Transmitter (irsend) broken in 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/663497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454371] Re: Hauppauge HVR-1600 Remote Not Detected
Perhaps wrong kernel version, duuno. But it's the kernel, media susbsystem. ** Package changed: lirc (Ubuntu) => linux-lts-utopic (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/454371 Title: Hauppauge HVR-1600 Remote Not Detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/454371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238032] Re: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc)
..unless there is more input -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/238032 Title: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc) To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/238032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238032] Re: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc)
Same expired goes for lirc... ** Changed in: lirc (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/238032 Title: lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc) To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/238032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991116] Re: lirc does not work/start
Does this mean that the bug is gone after updating hardware.conf? ** Changed in: lirc (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991116 Title: lirc does not work/start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/991116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
