^fails. If I add the lirc group, then I can run 'sg dialout lirc-setup',
and setup, and even make ir receiver react, but testing by irw still
does not display anything. Is there some guide for what has changed so
that setting up correctly would be easier?
--
You received this bug notification
I did already
# 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/
as superuser and
'systemctl disable
I tried running lirc-setup on fresh 18.04 install, but it fais as group
lirc does not exist.
--
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/1788235
Title:
lirc broken on 18.04
Status
I upgraded from 16.04 to 18.04 and lirc does not work anymore. systemd shows
errors such as "lircd-0.10.0[928]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*"
I suppose it is a bug, as lirc should work after upgrade without manual
reconfiguration.
--
You received this bug
** Description changed:
- MythTV Frontend becomes unresponsive, if you switch to a channel that
+ MythTV Frontend becomes unresponsive, if you switch to a TV channel that
does not have broadcast.
+
+ After a while, program returns to main menu, and a dialog tells: "Error
+ opening jump program
Public bug reported:
MythTV Frontend becomes unresponsive, if you switch to a channel that
does not have broadcast.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mythtv-frontend 2:0.28.0+fixes.20160413.15cf421-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux
Public bug reported:
Setup prompts to stop the backend, but ps command tells it runs even
after choosing to stop it.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mythtv-backend 2:0.28.0+fixes.20160413.15cf421-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux
Public bug reported:
I have this in /etc/apache2/sites-available/mythweb.conf :
# If you intend to use authentication for MythWeb (see below), you will
# probably also want to uncomment the following rules, which
** Description changed:
Steps to reproduce:
Start mythtv frontend with single display on.
Use xrandr to extend desktop to cover two displays. (The displays have
different aspect ratios.)
Go to media library and start playback.
Expect aspect ratio of the video to be correct (as it
Public bug reported:
1. Choose chromekey or softblend OSD renderer in Video-playback setup.
2. Watch TV, then press up arrow or down arrow to change the channel of
which info is shown. Repeat.
3. Alternatively, while watching TV, press i twice to get channel info.
Then do 2.
4. Channel icon is
** Attachment added: "Screenshot of corrupted channel icon"
https://bugs.launchpad.net/mythbuntu/+bug/1530856/+attachment/4543834/+files/Screenshot%20-%2004.01.2016%20-%2014.18.01.png
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to
Public bug reported:
Steps to reproduce:
Start mythtv frontend with single display on.
Use xrandr to extend desktop to cover two displays. (The displays have
different aspect ratios.)
Go to media library and start playback.
Expect aspect ratio of the video to be correct (as it was with single
** Summary changed:
- XFCE bar is visable over Mythfrontend on a fresh 14.04 install
+ XFCE bar is visible over Mythfrontend on a fresh 14.04 install
** Description changed:
- The XFCE bar is visable over mythfrontend on a fresh install.
+ The XFCE bar is visible over mythfrontend on a fresh
** Description changed:
The radio plays, however. Nothing was shown in the guide for the radio
channel, though. This is DVB-T radio channel, not internet radio
- channel.
+ channel. I tried to play another radio channel, for which was more shown
+ in program guide. It did not play, but
Public bug reported:
The radio plays, however. Nothing was shown in the guide for the radio
channel, though. This is DVB-T radio channel, not internet radio
channel.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: mythtv-frontend 2:0.27.4+fixes.20150116.3b43903-0ubuntu0mythbuntu2
[origin:
Are you sure? I just installed Mythbuntu from 64bit image and it has
pulseaudio running.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1383783
Title:
If I pause playback, pulseaudio takes
I did the trick told in #1. It worked first in 14.04, but not anymore
even if /etc/init/mythtv-backend.conf is still same. As for #7, service
mythbackend start don't work either: mythbackend: unrecognized
service What is wrong?
--
You received this bug notification because you are a member of
I don't know. I am using 14.04, but I have enabled MythTV updates
repository for version 0.27, and Mythbuntu updates repository and
installed updates.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
The problem was that for some reason backend IP address was changed to
something else than localhost, but the problem was solved once I changed
it to 127.0.0.1 again in backend setup. I just don't have an idea what
could have changed it back to local netwoek addresss and why, cause I
did not.
--
Public bug reported:
OS: Mythbuntu 14.04; Audio: Intel NM10/ICH7 (rev 2)
Pulseaudio takes significantly CPU during playback, especially, if
Pulseaudio:default is chosen as the audio output device. However, it
takes even more CPU, if you pause playback. I see no reason for such
high CPU usage.
Public bug reported:
OS: Mythbuntu 14.04
Sorry, if this is a mixed bug report, but if you know how to split this
into separate bug reports against separate packages, please do so and
link them here.
In audio settings...
If I use Pulseaudio:default as audio output device, ALSA:default as
Mixer
Confirmed in Mythbuntu 14.04.
** Changed in: mythbuntu
Status: New = Confirmed
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1181335
Title:
Menu bar still showing after reboot
Public bug reported:
If the aspect ratio of display differs from the aspect ratio of video to
show, there are black borders visible. But if you have e.g. web browser
open covering whole display, and you switch to it and back by Alt-
Tabulator, parts of the web browser window remain visible in the
This seems to be fixed in ubuntu 12.04. Keys have different names,
though.
** Changed in: lirc (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
This seems to be fixed in ubuntu 12.04.
** Changed in: lirc (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/514780
Title:
Lirc does not work
As for BIOS, I have updated it long time ago, and I suppose it is still latest
version.
$ lshal | grep firmware
system.firmware.release_date = '09/08/2009' (string)
system.firmware.vendor = 'Phoenix Technologies Ltd.' (string)
system.firmware.version = '11CA.M015.20090908.RHU' (string)
And the computer is NC10. But that is not the only computer that this
bug occurs in.
--
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 different
As for resume taking so long time, it seems it is an issue with the dvb
device.
--
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 different ttyUSB
Here's the data. Probably not relevant, but resume took more than a
minute.
** Attachment added: dmesg after fresh boot, suspend and resume
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+attachment/2181690/+files/dmesg2
--
You received this bug notification because you are a
Bug is still present in ubuntu 11.04.
Note that the recommended way to stop and start lirc in ubuntu nowdays
is sudo service lirc stop and sudo service lirc start,
respectively.
The presented workaround is not ideal for irxevent and irexec daemons,
since it may be that the user user is not at
*** This bug is a duplicate of bug 359356 ***
https://bugs.launchpad.net/bugs/359356
** This bug has been marked a duplicate of bug 359356
USB device attached to different ttyUSB after resume from suspend to RAM
--
You received this bug notification because you are a member of Mythbuntu
Tested this in ubuntu 11.04. The device name is not changed, and lirc
works after resume, if neither irexec nor irxevent is running. If either
one is running, device is changed in resume. A workaround is to unplug
and re-plug the USB device. Then /dev/ttyUSB0 exists again and lirc
works. The
In 10.10 it did not work for me: No output from irw.
--
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/517304
Title:
Lirc does not work; no remote's button presses visible in irw's
If you use irxevent or irexec, their respective daemons are killed in
conjunction with stopping lirc. To automatically re-run these I could only run
DISPLAY=:0.0 su user -c irxevent --daemon irexec --daemon
where user is your user name, in resume|thaw case after starting lirc daemon.
I suppose
To be more specific, also irxevent and irexec worked after resume in
9.04, when applying comment #7.
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
You received this bug notification because you are a member of Mythbuntu
Bug
And the workaround does not work in 10.04 so I don't know how to make
10.04 work as well as 9.04.
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
You received this bug notification because you are a member of Mythbuntu
Bug Team,
I can not reproduce this in 10.04.
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in ubuntu.
Status in “lirc”
Oh, I can reproduce it: I just have to have irxevent running.
Note: If I have irexec running, but no irxevent, the device is not changed in
resume, but lirc does not work anyway.
--
USB device attached to different ttyUSB after resume from suspend to RAM
https://bugs.launchpad.net/bugs/359356
Seems to work better in 10.04. I still have to manually add
REMOTE_DEVICE=/dev/ttyUSB0 in /etc/lirc/hardware.conf to make it work
for my remote control.
--
Lirc does not work; no remote's button presses visible in irw's output
https://bugs.launchpad.net/bugs/517304
You received this bug
39 matches
Mail list logo
