[Mythbuntu-bugs] [Bug 1633871] Re: Mythtv frontend stuck in restart loop (code 139) after update to Ubuntu 16.10

2016-11-03 Thread heynnema
Same problem here. If you start mythfrontend in terminal, you'll probably see a stack smashing error. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to mythtv in Ubuntu. https://bugs.launchpad.net/bugs/1633871 Title: Mythtv frontend st

Re: [Mythbuntu-bugs] [Bug 934023] Re: mceusb remote stops working after lucid->precise upgrade

2016-11-03 Thread Mario Limonciello
This change in the new lirc to drop hardware.conf is going to break a lot of people that upgrade to zesty. That has been part of Ubuntu for a very long time... On Thu, Nov 3, 2016, 17:11 Alec Leamas <934...@bugs.launchpad.net> wrote: > Setting Incomplete to let bug expire. Please change if you d

[Mythbuntu-bugs] [Bug 358817] Re: Add irexec, irxevent, ... to session

2016-11-03 Thread Alec Leamas
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 Mythbuntu Bug Team, which is subscribed to lirc in

[Mythbuntu-bugs] [Bug 358817] Re: Add irexec, irxevent, ... to session

2016-11-03 Thread Alec Leamas
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 recei

[Mythbuntu-bugs] [Bug 934023] Re: mceusb remote stops working after lucid->precise upgrade

2016-11-03 Thread Alec Leamas
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 Mythbuntu Bug Team, which is subscribed to mythbuntu-lirc-generator in Ubuntu. http

[Mythbuntu-bugs] [Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM

2016-11-03 Thread Alec Leamas
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 Mythbuntu Bug Team, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to

[Mythbuntu-bugs] [Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM

2016-11-03 Thread Alec Leamas
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 Mythbuntu Bug Team, which is subscribed to lirc in Ubuntu. http

[Mythbuntu-bugs] [Bug 204769] Re: /etc/init.d/lirc requires TRANSMITTER_DEVICE to be set in hardware.conf

2016-11-03 Thread Alec Leamas
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 Mythbuntu Bug Team, which is subscribed to lirc in Ubuntu. https://bugs.launchp

[Mythbuntu-bugs] [Bug 505705] Re: irexec isn't started automatically on existing installs

2016-11-03 Thread Alec Leamas
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,

[Mythbuntu-bugs] [Bug 786743] Re: Lack of support for Multiple receivers

2016-11-03 Thread Alec Leamas
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 u

[Mythbuntu-bugs] [Bug 786743] Re: Lack of support for Multiple receivers

2016-11-03 Thread Alec Leamas
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 Mythbuntu Bug Team, which

[Mythbuntu-bugs] [Bug 517743] Re: Check the TRANSMITTER logic for errors w/ lirc-mceusb

2016-11-03 Thread Alec Leamas
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 Mythbuntu Bug Team,

[Mythbuntu-bugs] [Bug 1639036] [NEW] If configured as a remote backend, mythtv-backend.service should start after network-online.target

2016-11-03 Thread Eduard Iten
Public bug reported: I had the problem that my remote frontend said "Could not connect to mythbackend context" or something similar. In the command line output there was a connection denied error. When I restarted the backend service, everything went smooth. Now I changed the line After=mysqld.se

[Mythbuntu-bugs] [Bug 654160] Re: mceusb RC not working

2016-11-03 Thread Oniboy
Thanks for finally getting to this bug but unfortunately I no longer have the hardware or software this relates to. Unless this is still relevant to someone else this should probably be closed. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscri

[Mythbuntu-bugs] [Bug 775618] Re: Lirc is conflicted by some default ir-controlling module so that it only sends keyboard input

2016-11-03 Thread Niklas Rosenqvist
Hi Alec! I have no way of following up on this any longer, sorry! Feel free to close it! -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/775618 Title: Lirc is conflicted by some default