@leamas-alec Any ideas on a proper fix?
--
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:
Confirmed still reproducible with 16.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880766
Title:
ubiquity and grub-install: fails to install grub on software RAID
To manage notifications
Yes, via the PPA. Guess I should have waited for the trusty-proposed...
:-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323391
Title:
Update to 0.27.1 point release
To manage notifications
I've preformed the test case on an otherwise unaltered 0.27 install and
everything I've tried so far works fine - recommend releasing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323391
Title:
I've confirmed that, at least for me, the latest fixes (0.27.1) indeed
resolves this issue. Anyone else still seeing this?
** Changed in: mythbuntu
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Changeset 25876a76e (MythTV 0.27.1 on 2014-05-25) might have fixed this, at
least for some users.
More details here: https://code.mythtv.org/trac/ticket/7958
** Bug watch added: code.mythtv.org/trac/ #7958
http://code.mythtv.org/trac/ticket/7958
--
You received this bug notification because
*** This bug is a duplicate of bug 1298610 ***
https://bugs.launchpad.net/bugs/1298610
Howdy, and thanks for your bug report. I believe Bug #1298610 contains
the planned fixed, so I am marking this bug as a duplicate of that.
** This bug has been marked a duplicate of bug 1298610
trusty
I believe this has been confirmed by another user, and by a third in a
VM. Not sure if this is ubiquity or mysql.
** Description changed:
Package: mysql-server (and possibly other mysql-related packages)
- Upgraded from 12.04 LiveCD, 64-bit version. On completion of apparently
- successful
Steve, I start with Mythbuntu 10.04 in most cases. I believe Bug
#937196 was done on a real machine, but I'd have to go back and check.
If I get a chance tonight, I'll try to double check.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Changing back to confirmed for the following reasons:
1) people are still seeing it (and not just on 10.04, apparently)
2) people might not update their 10.04 install before doing the upgrade
** Changed in: ifupdown (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
Setting to confirmed since user responded to question.
** Changed in: grub2 (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982425
Title:
grub don't
sorry for the delay - been working non-stop for 7 days. Attached are
the logs from BEFORE the reboot where you end up at the grub prompt.
This is done in a VM. I also captured /boot/grub
** Attachment added: dist-upgrade.tar
** Attachment added: boot.dir.tar.gz
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/978464/+attachment/3096711/+files/boot.dir.tar.gz
** Changed in: grub2 (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is easily reproducible with a VM (install 10.04 and then do the
10.04 updates).
** Changed in: grub2 (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just ran into this again and completely forgot about it... and people comment
how good my memory is.
I'm most certainly not the only person that has run into this either - here is
another example with a different package:
https://answers.launchpad.net/ubuntu/+source/update-
** Changed in: grub2 (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978464
Title:
Upgrade 10.04 to 12.04 Beta 2 failed, grub issue
To manage
** Changed in: grub2 (Ubuntu)
Milestone: None = ubuntu-12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978464
Title:
Upgrade 10.04 to 12.04 Beta 2 failed, grub issue
To manage
Should be fixed in final 12.04 release. If you want to pick it up
sooner, you can enable the mythbuntu-repos (which I highly recommend
doing anyway).
** Changed in: mythtv (Ubuntu)
Status: Triaged = Fix Released
** Changed in: mythtv (Ubuntu)
Milestone: None = ubuntu-12.04
--
You
Howdy, and thank you for taking the time to help improve Mythbuntu by
opening this ticket. There have been quite a number of bug fixes made
to the 0.24.x version you are running - I would suggest enabling the
Mythbuntu repos, which will pick up those fixes. You can find out more
by clicking
** Changed in: mythtv (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949291
Title:
mythbackend crashed with SIGSEGV in MediaServer::~MediaServer()
To
A fix has been applied upstream which should appear in tomorrow's 12.04
repo build, as well as the final 12.04 build. If you don't have repo's
installed, I highly encourage it: http://mythbuntu.org/auto-builds
** Changed in: mythtv (Ubuntu)
Status: Triaged = Fix Released
** Changed in:
*** This bug is a duplicate of bug 962981 ***
https://bugs.launchpad.net/bugs/962981
I suspect it a duplicate of bug #962981, and since you can't reproduce
it currently, we'll just go with that assumption. Thanks for the reply!
** This bug has been marked a duplicate of bug 962981
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. I've forwarded the important information to the MythTV
developers - we'll see what they find!
** Bug watch added: code.mythtv.org/trac/ #10564
http://code.mythtv.org/trac/ticket/10564
** Also affects: mythtv via
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. I've forwarded the important information to the MythTV
developers - we'll see what they find!
** Bug watch added: code.mythtv.org/trac/ #10565
http://code.mythtv.org/trac/ticket/10565
** Also affects: mythtv via
Howdy, and thank you for taking the time to help improve Mythbuntu by
opening this ticket. I've forwarded the important information to the
MythTV developers - we'll see what they come up with!
** Bug watch added: code.mythtv.org/trac/ #10554
http://code.mythtv.org/trac/ticket/10554
** Also
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. I have submitted the important information to the MythTV
developers - we'll see what they can find!
** Bug watch added: code.mythtv.org/trac/ #10555
http://code.mythtv.org/trac/ticket/10555
** Also affects: mythtv
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. I've forwarded the important information to the MythTV
developers - we'll see what they can find!
** Bug watch added: code.mythtv.org/trac/ #10556
http://code.mythtv.org/trac/ticket/10556
** Also affects: mythtv
Unfortunately the developer was not able to uncover any problems with
the logs attached. If you are able to reproduce this again, please feel
free to attach new crash logs here, or better yet, open a new ticket.
If you can get it to crash upon demand, a proper crash dump captured
with gdb would
Kenneth E. DeLeo, can you describe what you might have been doing when
this crash was generated? Was it when the frontend first fired up? Were
you moving around the menus? Opening a screen (recordings? videos?
schedules?)? Or maybe starting up a video or recording for playback? The
log doesn't
jcarlosmiguel, can you describe what you might have been doing when this
crash was generated? Was it when the frontend first fired up? Were you
moving around the menus? Opening a screen (recordings? videos?
schedules?)? Or maybe starting up a video or recording for playback?
The log doesn't
*** This bug is a duplicate of bug 962981 ***
https://bugs.launchpad.net/bugs/962981
Todd Howe , can you describe what you might have been doing when this
crash was generated? Was it when the frontend first fired up? Were you
moving around the menus? Opening a screen (recordings? videos?
*** This bug is a duplicate of bug 962981 ***
https://bugs.launchpad.net/bugs/962981
Sorry for the incorrect question Todd... pasting error! Were you
restarting the frontend when it crashed, or did it crash when you hit
enter to change the password, or ...? A bit more detail would be nice.
Kim Tyler, can you describe what you might have been doing when this
crash was generated? Was it when the frontend first fired up? Were you
moving around the menus? Opening a screen (recordings? videos?
schedules?)? Or maybe starting up a video or recording for playback? The
log doesn't seem to
https://github.com/MythTV-
Themes/Mythbuntu/commit/43d37072e6a1deaa06ddce0a9828711fcfd54325
** Changed in: mythbuntu
Status: Expired = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://github.com/MythTV-
Themes/Mythbuntu/commit/43d37072e6a1deaa06ddce0a9828711fcfd54325
** Changed in: mythtv (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Visibility changed to: Public
** Attachment removed: ThreadStacktrace.txt
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/949291/+attachment/2830598/+files/ThreadStacktrace.txt
** Attachment removed: Stacktrace.txt
** Bug watch added: code.mythtv.org/trac/ #10472
http://code.mythtv.org/trac/ticket/10472
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/10472
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is a relatively new remote and is not supported by lirc yet. I
searched the internet for that device ID and found others using it
successfully after recompling their kernel with a minor change.
Example:
http://forums.gentoo.org/viewtopic-p-6980174.html
** Changed in: lirc (Ubuntu)
This bug should have bee marked as incomplete some time ago because
upstream is unable to diagnose the problem with the logs attached to
this ticket. Please collect new logs of mythtv-setup crashing (not the
backend) and attach them here.
Others are welcome to do so, or open new tickets.
thank
** Changed in: mythtv-status (Ubuntu)
Status: Confirmed = Triaged
** Changed in: mythtv-status (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/945582
When I got this to happen, I did a fresh Mythbuntu 10.04.1 install and
did not do the megaload of updates before issuing do-release-upgrade
-d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937196
2.5 years later, and this bug appears to be unfixed.
I'm doing 10.04 LTS upgrade testing to 12.04. I installed 10.04 and
then tell it to install updates (before upgrading to 12.04). During the
update, I end up stuck at Configuring grub-pc window in update-
manager. It will not let me continue
Public bug reported:
Attempting to upgrade from Mythbuntu 10.04 to 12.04. Here is the
important part of the upgrade log output. Complete logs will be
attached, and if more info is needed, please just ask!
dpkg: dependency problems prevent configuration of ifupdown:
ifupdown depends on
** Tags added: dist-upgrade lucid2precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937196
Title:
10.04 LTS - 12.04 upgrade failed due to ifupdown
To manage notifications about this bug go to:
** Attachment added: apt.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/937196/+attachment/2763108/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937196
Title:
** Attachment added: apt-term.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/937196/+attachment/2763107/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937196
** Attachment added: main.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/937196/+attachment/2763109/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937196
Title:
** Attachment added: history.log
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/937196/+attachment/2763119/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937196
** Attachment added: apt-clone_system_state.tar.gz
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/937196/+attachment/2763120/+files/apt-clone_system_state.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 883618 ***
https://bugs.launchpad.net/bugs/883618
** This bug has been marked a duplicate of bug 883618
Natty Console upgrade useless.. XSet warnings all over the screen
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Marking as Triaged and high since this will affect a larger number of
users in the 10.04 LTS - 12.04 LTS transition. superm1 confirmed this
is still occuring in 12.04. His bug #933991 has screenshot and logs (it
is now marked as dup of this bug).
** Changed in: update-manager (Ubuntu)
Is this an xorg-server bug or upgrade-manager? Bug #883618 appears to
be the same problem, and still occurs on precise upgrades.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881725
Title:
xset:
Upstream closed this bug, probably with good reason. Haven't heard of
this happening in recent versions, and even if we did, it would need to
be reproduced and a backtrace caught on a 0.24, and preferrably 0.25
system. If this reoccurs, please open a new ticket.
** Changed in: mythtv (Ubuntu)
Marking as confirmed since there is a second report - but we really need
a backtrace for this ticket to go anywhere.
** Changed in: mythtv (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment removed: Stacktrace.txt
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/908744/+attachment/2647357/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908744
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Was this crash reproducible for you, or did you try again and
get past that point? Unfortunately, through no fault of your own, it
appears that the debugging information that was captured is invalid, so
we will likely
Howdy, and thank you for helping to improve Mythbuntu and MythTV by
submitting this ticket. I've forwarded the important information to the
developers and we'll see what they have to say!
** Bug watch added: code.mythtv.org/trac/ #10239
http://code.mythtv.org/trac/ticket/10239
** Also
** Bug watch added: code.mythtv.org/trac/ #10228
http://code.mythtv.org/trac/ticket/10228
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/10228
Importance: Unknown
Status: Unknown
** Visibility changed to: Public
--
You received this bug notification because you
With all possible due respect, I pretty strongly disagree with the
opinion status. Everything I placed in the bug description is fact.
This is an enhancement / feature request, not an opinion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. I have not yet attempted to reproduce this in 11.10, but I do
see it when adding mythtv to a base Ubuntu 11.04 system.
** Changed in: mythtv (Ubuntu)
Importance: Undecided = Low
** Changed in: mythtv (Ubuntu)
Public bug reported:
The package included on the 11.10 disk should probably be labelled
0.24.1 rather than 0.24.0.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: mythtv (not installed)
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion:
** Changed in: mythtv (Ubuntu)
Importance: Undecided = Low
** Changed in: mythtv (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/868890
Title:
mythtv package
Anyone that hasn't already done this LTS upgrade isn't likely to now,
and no-one seems to be focused on fixing this.
** Changed in: mythbuntu-meta (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Howdy, and thank you for helping to improve MythTV and Mythbuntu by
opening this ticket. There have been a number of bug fixes to the 0.24
branch since the build that you are using - can you enable the Mythbuntu
repo and report back if the problem still exists. You can find out more
here:
And to answer your question about falling back to 0.23, that is only
possible with backups - which MythTV typically creates automatically on
version upgrades. Of course, restoring that backup from that time would
restore the database (recording schedules and shows watched) to what you
had at that
Howdy, and thank you for helping to improve MythTV by opening this ticket. The
version of MythTV which you are running is a bit outdated - there have been a
number of bug fixes to 0.24, including to mythvideos. I would highly suggest
following the directions at:
Hmmm... if /etc/default/apport had enabled set to 1 as described in
the previous link, I would have thought it would request to submit it
for you when the crash happened.
If there is a crash report in /var/crash, then I believe apport-bug
/var/crash/filename.crash will cause it to submit that
If it is crashing, then we can try to submit logs upstream, but the
developers will really, really want to see the crash report (which
apport should offer to submit for you when it crashes - and when it
does, it will open a new ticket as well as attach the logs).
--
You received this bug
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, upstream developers will need a bit more
information about the crash. Could you please make sure apport is
enabled and update to the latest version of the debug packages by
following the basic backtrace
Looks like this will be finally fixed in 0.25, whenever that happens.
** Changed in: mythtv (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/550544
Should be fixed no later than when 0.25 is released...
** Changed in: mythtv (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728809
Title:
Should be fixed whenever 0.25 gets released...
** Changed in: mythtv (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/490920
Title:
mythfilldatabase
** Changed in: lirc (Ubuntu)
Importance: Undecided = Critical
** Changed in: lirc (Ubuntu)
Status: New = Triaged
** Changed in: lirc (Ubuntu)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Marked as triaged since the cause is documented. Medium since it
affects users first impressions of Ubuntu and Unity.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Triaged
** Changed in: compiz (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification
Least we think this is completely resolved, this just occurred on my up-
to-date 10.04/Lucid system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581173
Title:
indicator-sound-service eating CPU
Howdy, and thank you for helping to improve Mythbuntu and MythTV by
opening this ticket. I've forwarded this report upstream - we'll see if
it is solvable with the debug information that was submitted.
** Changed in: mythtv (Ubuntu)
Status: New = Triaged
** Bug watch added:
Howdy, and thank you for helping to improve MythTV and Mythbuntu by
opening this ticket. I have linked this ticket to a related upstream
bug. While this problem is annoying, it does not affect system
operation at all.
** Changed in: mythtv (Ubuntu)
Importance: Medium = Low
** Changed in:
Howdy, and thank you for helping to improve Mythtv and Mythbuntu by
opening this ticket - and especially for attaching a patch! I've
forwarded this upstream.
** Bug watch added: code.mythtv.org/trac/ #9598
http://code.mythtv.org/trac/ticket/9598
** Also affects: mythplugins via
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, through no fault of your own, attached stacktrace
is not useful to the developers. Could you please update to the latest
version of the debug packages by following the basic backtrace
directions outlined
Not sure how this ticket didn't get noticed. I forwarded it upstream.
** Bug watch added: code.mythtv.org/trac/ #9555
http://code.mythtv.org/trac/ticket/9555
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/9555
Importance: Unknown
Status: Unknown
** Changed in:
*** This bug is a duplicate of bug 660833 ***
https://bugs.launchpad.net/bugs/660833
** This bug has been marked a duplicate of bug 660833
Mythfrontend and Xorg crash/restart back to login screen when starting
playback/LiveTV
* You can subscribe to bug 660833 by following this link:
*** This bug is a duplicate of bug 708950 ***
https://bugs.launchpad.net/bugs/708950
** This bug has been marked a duplicate of private bug 708950
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 708950 ***
https://bugs.launchpad.net/bugs/708950
** This bug is no longer a duplicate of bug 638670
mythconverg_backup.pl assert failure: *** glibc detected *** /usr/bin/perl:
double free or corruption (!prev): 0x01000f00 ***
** This bug has
Howdy, and thank you for helping to improve Mythtv and Mythbuntu by
opening this ticket, as well as the previous ones that you've opened on
the same topic which I've closed as duplicates of this one. You have
been the only one reporting this issue that I can see, so it seems most
likely that
We really do appreciate you opening this ticket to help improve
Mythbuntu, but it needs to be closed for a number of reasons. The
biggest one is that the upstream MythTV developers have limited
resources and have turned their efforts to newer versions and and are no
longer fixing bugs on this
** Changed in: pidgin (Ubuntu)
Status: Confirmed = Triaged
** Changed in: pidgin (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/539516
Title:
Pidgin
Reporter: do you have any way to double check that your hardware is
functional (windows?)
** Summary changed:
- V4L DVB Problems
+ i2c errors with af9015 / tda18271 (V4L DVB)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error aspect comes from the fact that at compile time, it was told
to expect those drivers to be available, but they are not. In order
to have one package for the masses, it has to be enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Does not look like upstream will be fixing this anytime in the
foreseeable future. If you'd like them to go away, you'll need to
install the VDPAU drivers, or else just ignore them.
** Changed in: mythtv (Ubuntu)
Importance: Low = Wishlist
** Changed in: mythtv (Ubuntu)
Status:
(or recompile the package without vdpau enabled)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/664559
Title:
VDPAU Error in mythfrontend.log although using radeon
--
ubuntu-bugs mailing list
Howdy, and thank you for helping to improve Mythbuntu and mythtv by
opening this ticket. I've confirmed this occurring in the latest
release (0.24), so I've forwarded it upstream.
** Changed in: mythtv (Ubuntu)
Importance: Undecided = Low
** Changed in: mythtv (Ubuntu)
Status: New =
** Changed in: cdrom-detect (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/582427
Title:
cdrom-detect fails when using usb storage as install device
--
** Bug watch added: Debian Bug tracker #608327
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608327
** Also affects: cdrom-detect via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608327
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Upstream claims this problem was fixed in cdrom-detect, so the remaining
issue may be the 7-zip long file name problem that is described in Bug
234185 (i.e., you may not be able to certain utilities, such as
UNetbootin). Rob, which burning utilities have you tried?
--
You received this bug
do-release-upgrade -m desktop, although I'm not entirely sure that has
to do with the price of tea in China. It isn't like this message is
unique to this upgrade procedure - Google turns up plenty of other
people and launchpad bugs with this message.
** Changed in: eglibc (Ubuntu)
Thanks for reporting back!
** Changed in: mythtv (Ubuntu)
Status: Incomplete = Invalid
--
Doesn't remove cron jobs on removal
https://bugs.launchpad.net/bugs/669440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Howdy, and thank you for helping to improve MythTV by opening this
ticket. Unfortunately, through no fault of your own, the attached
stacktrace is not useful to the developers. Could you please update to
the latest version of the debug packages by following the basic
backtrace directions outlined
It would be most helpful if those that have not already reported the
results of the following could please do so:
1. trying to adjust the profiles so that you aren't using XvMC
2. disabling whatever video driver you are using
--
Mythfrontend and Xorg crash/restart back to login screen when
Michael Martin-Smucker, have you tried changing profile at all? It may
be more related to XvMC usage rather than Nvidia usage.
--
mythtv crashes on some HD channels, crashes causes user to be logged out
https://bugs.launchpad.net/bugs/660833
You received this bug notification because you are a
*** This bug is a duplicate of bug 638670 ***
https://bugs.launchpad.net/bugs/638670
** This bug has been marked a duplicate of bug 638670
mythconverg_backup.pl assert failure: *** glibc detected *** /usr/bin/perl:
double free or corruption (!prev): 0x01000f00 ***
* You can
1 - 100 of 1080 matches
Mail list logo
