[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/421276
Glenn, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/
Just to tell ya I solved my problem by changing my mainboard.
I went from the NVIDIA chipset to an AMD chipset my problems were
past tense :-)
dunno of course if you've got a NVIDIA chipset but it's worth a try to
change the mainboard...
Just me 2 cents
GRTZ GoofY
On 3/18/2010 12:54 PM,
I'm seeing this problem too. Occasionally (maybe once a week) the
frontend stops responding to IR commands. I believe it is only
happening while watching video (ie. live tv or a recording, not while
the frontend is displaying menu).
Running top shows nothing unusual (90%+ idle). I ran an
This is not sounding like a Mythbuntu bug. It is either hardware
conflicts or perhaps a kernel problem. For those of you experiencing
it, it would be best if you could figure out how to reproduce it on
demand and attach logs comparing both states. Perhaps online searches
would yield more info
Solved for me, Finally! I upgraded my TV to an LCD which required a higher
resolution. This made my remote virtually unusable, 1 or 2 key presses and it
was done. I figured it must be a problem with my myth frontend just not having
enough muscle. Fortunately I had an extra computer I could
It is a hardware problem. I have experienced this on multiple
motherboards / ram sets - multiple computers and as seen from this bug
report, many people have this problem. Not sure what fixed it in your
scenario, maybe it is an incompatibility with a specific subset of
hardware, or maybe
I still get the occasional delay after a keypress if I've been using the remote
a lot, maybe a second or two. I think with my previous setup the remote would
have stopped working at that point, with the extra memory and CPU it just gives
me a slight delay.
With my previous setup if the remote
The problem I am experiencing is not a delay -- it just simply stops
working, completely, which is why i believe it is a software problem
(for me at least). My HTPC is running a fairly new processor, quad
core, and 8gb ram, new mobo, etc. I'll have to try your fix, logging in
via ssh, and see if
I agree with Brett, I've got a similar setup quad core, 8GB 5TB.
It seems that for some reason the USB bus resets which causes the remote to
stop functioning.
lines of reasoning -- because the remote still shows the LED that it receives
commandos. The module is not UN-loadable eg hangs. After a
Must be a different problem then. I could never diagnose mine properly though
since the problem would disappear as soon as I logged in with remote desktop.
Good luck with it, it's a frustrating problem.
--
USB remote stops working
https://bugs.launchpad.net/bugs/421276
You received this bug
Please also see BUG 484796.
I filed the same 'bug behavior'.
My description though is on the end of the bug report.
If there's someone who's able to tell how to turn on debugging in this
case please share the knowledge.
To the bug maintainer?
I experienced this matter also in 9.04 9.10 all
I too am having this problem, although I can confirm that it is not a
problem with other IR signals coming into the reciever -- it happened to
me while only using the IR remote (to control xbmc). I seem to
experience the problem 5-15 minutes after starting and, as others have
stated, restarting
As requested above,
/etc/lirc/hardware.conf:
--
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE=Windows Media Center Transceivers/Remotes (all)
REMOTE_MODULES=lirc_dev lirc_mceusb
REMOTE_DRIVER=
REMOTE_DEVICE=/dev/lirc0
REMOTE_SOCKET=
I've been trying to narrow down the cause of this and one idea I have is
that my television's remote control is messing things up. I use the TV
remote to adjust the volume on my TV. It doesn't instantly kill my
Mythtv remote but it seems that if I avoid using my TV remote I don't
have the issue.
I'm having the same issue in 9.04 I'm using a XBOX remote with a XBOX DVD
receiver modified with a USB cable. The remote will randomly stop working. It
might work for an hour, or maybe a minute. Often if it stops working I can walk
away for 5 minutes, come back and it works again.
I would also want to see the output of the following information:
1) /etc/lirc/hardware.conf
2) lsusb
3) /var/log/syslog
--
USB remote stops working
https://bugs.launchpad.net/bugs/421276
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mythbuntu
Status: New = Incomplete
--
USB remote stops working
https://bugs.launchpad.net/bugs/421276
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Howdy, and thank you for helping to improve Mythbuntu. You mention
others having this problem - pointers to those discussions might be
somewhat helpful in knowing what has been tried and what has not. Also,
it would be helpful to know exactly which version(s) you are running
(kernel, lirc, etc).
19 matches
Mail list logo
