We all appreciate the effort you've spent on this so far in trying to
help improve MythTV (and Mythbuntu). Unfortunately, the developers
upstream have stopped focusing on 0.21 and older reports in preparation
for a 0.22 release later this year. And as you saw, branch changes must
be relatively lo
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
update-manager usability: Remove "Update is complete" wording
https://bugs.launchpad.net/bugs/254477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
Update-manager marks upgrades as completed even if they aren't
https://bugs.launchpad.net/bugs/254480
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
I intended on forwarding a different bug to paper cuts rather than this
one... but since it is already here, I'll let you all decide if it is
worthy. This one may be more than a trival fix.
--
Update-manager marks upgrades as completed even if they aren't
https://bugs.launchpad.net/bugs/254480
Y
Thanks to all three of you for updates. Sounds like the common theme is
EIT. I may have found the offending code, and if that is indeed the
source of the problem you all are having, it has been changed in 0.22.
For those that are interested, you'll notice that the following
changeset describes fi
@Kevin,
Sorry, you are correct - I missed the mythcommflag angle somehow while I was
rushing around this morning. I'm more than happy to leave this open for a
while longer if you all can continue helping to debug it.
I did leave something out of my note earlier: MythContext:DBError() has been
@NickFox: is this reproducable?
** Changed in: mythbuntu
Status: New => Incomplete
--
mythtv-status crashed with SIGSEGV in Perl_sv_upgrade()
https://bugs.launchpad.net/bugs/366501
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sure - a first step would certainly be to subscribe to the weekly
0.21-fixes as described on the web page above, and 9.04 includes newer
openchrome drivers. If it is fixed, there, then it is likely fixed on
0.22. If not, upstream would only be interested if this is still
occuring 0.22 though. Yo
I disagree that this should been posted to the forums. Some
documentation on the command should have been posted before it gets
pushed out as a half-approved method of upgrading.
To add to the confusion, the "mode" mentioned UpdateManagerFaq and on the Bug
#222048 seem to say it is required to h
Public bug reported:
Binary package hint: apport
Apport has marked Bug#420628 and Bug#420932 as duplicates of Bug#415922
(apparently a private bug, because I can't access it). In doing so, it
removed the attachments of the public bugs, so now others can't study
them.
Two possible solutions:
1.
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).
Richcrook, did removing the -k from the script help?
--
lirc_mceusb2 module not loading correctly after system shutdown
https://bugs.launchpad.net/bugs/336107
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Howdy all, I kinda doubt it is a problem with the database or the query
itself. The messed up date makes me think of something like a corrupted
pointer - most likely in the EIT code since that is the point in common
for you all. A corrupted pointer will result in lots things being
messed up in m
It might or might not yield anything helpful, but someone might try
running with with -v eit,siparser (either one or both) logging turned
on overnight. Might produce some really large log files, so be sure to
turn it off in the morning!
--
mythbackend silently fails with QSqlQuery::exec: empty
Fixed upstream in 0.22
** Changed in: mythbuntu
Status: Confirmed => Fix Committed
--
mythwelcome screen not displayed at manual start
https://bugs.launchpad.net/bugs/260429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. The error in dpkg terminal log is:
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
another process: Resource temporarily unavailable
This was due to a concurrent access to the debconf database.
** Changed in: maxima (Ubuntu)
Importance: Undecided => Medium
** Changed in: maxima (Ubuntu)
Status: Confirmed => Triaged
--
Error in CONDITIONS::CLCS-UNIVERSAL-ERROR-HANDLER [or a callee]: Caught fatal
error [memory may be damaged]
https://bugs.launchpad.net/bugs/303587
You receive
*** This bug is a duplicate of bug 303587 ***
https://bugs.launchpad.net/bugs/303587
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported, so it is
being marked as such. Please look at the other bug report to see if
t
*** This bug is a duplicate of bug 303587 ***
https://bugs.launchpad.net/bugs/303587
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported, so it is
being marked as such. Please look at the other bug report to see if
t
Howdy, and thank you for helping to improve Ubuntu by opening this
ticket (and especially for attaching a patch)!
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
--
grub-reboot does not restore previous default after reb
Howdy, and thank you for helping to improve Mythbuntu. Unfortunately (or
fortunately, depending on your perspective), there is nothing that mythtv can
do about firmware loading. Reloading mythtv packages won't fix this problem
either... doing so simply provides another opportunity for the int
I too was unable to reproduce this. If you are still able to cause this
to happen and can attach additional information, please feel free to re-
open this ticket. Thanks!
** Changed in: gnupg (Ubuntu)
Status: Incomplete => Invalid
--
gpg --gen-key gpg: Segmentation fault caught ... exit
Howdy, and thank you for helping to improve things by opening this ticket.
Usually during distribution upgrades, the upgrade process will put up a window
or two for config files that are different or have changed. Is it possible
that it put that window up and you selected "Replace" rather than
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Since Mythbuntu uses the stock Ubuntu kernel, there is nothing
that the Mythbuntu project can do to fix this. Forwarding to Ubuntu
kernel.
** Project changed: mythbuntu => linux
** Bug watch added: Linux Kernel Bug Tr
Appears to be low risk. Ubuntu kernel team may want to pull in this in
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
Kernel 2.6.32 will break up ACPI wakealarm
https://bugs.launchpad.net/bugs/507457
You received
This may be the actual commit that Andrew mentions in the upstream bug:
http://bugzilla.kernel.org/show_bug.cgi?id=14889
** Bug watch added: Linux Kernel Bug Tracker #14889
http://bugzilla.kernel.org/show_bug.cgi?id=14889
--
Kernel 2.6.32 will break up ACPI wakealarm
https://bugs.launchpad.n
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed => Triaged
--
HP 2140 Lid Close Not Detected
https://bugs.launchpad.net/bugs/376793
You received this bug notification because you are a member of U
** Visibility changed to: Public
** Changed in: cron (Ubuntu)
Status: New => Confirmed
--
cron crashed with SIGSEGV in _init()
https://bugs.launchpad.net/bugs/508272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Visibility changed to: Public
--
cron crashed with SIGSEGV in _init()
https://bugs.launchpad.net/bugs/506634
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
https://lists.ubunt
** Visibility changed to: Public
--
cron crashed with SIGSEGV in _init()
https://bugs.launchpad.net/bugs/445018
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
https://lists.ubunt
Nick Hill, are you still working on this? Thanks!
--
Crontab accepts files with no newline before EOL/EOF. Cron ignores file
https://bugs.launchpad.net/bugs/118168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Howdy Richard,
Thank you for helping to improve Ubuntu by opening this ticket.
I see that there is a stack trace with symbols against this bug, but has this
problem reoccurred in the 2+ years since you filed it? I do not see any other
reports of something similar, so this seems to have only occ
*** This bug is a duplicate of bug 447080 ***
https://bugs.launchpad.net/bugs/447080
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported, so
it is being marked as a duplicate. Please look at the other bug
*** This bug is a duplicate of bug 447080 ***
https://bugs.launchpad.net/bugs/447080
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported, so
it is being marked as a duplicate. Please look at the other bug
*** This bug is a duplicate of bug 447080 ***
https://bugs.launchpad.net/bugs/447080
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported, so
it is being marked as a duplicate. Please look at the other bug
*** This bug is a duplicate of bug 447080 ***
https://bugs.launchpad.net/bugs/447080
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported, so
it is being marked as a duplicate. Please look at the other bug
Confirming. Happened to me on first boot after upgrading from 9.10 to
10.04 alpha 2.
The stack trace on this bug is not valid, but since this bug has the
most subscribers and also indicates over 60 people are affected (when
you include "also affects me" from the duplicates), it seems we should
u
Howdy, and thank you for helping to improve Ubuntu by opening this
ticket. Unfortunately, through no fault of your own, the debugging
information which was automatically collected does not contain any
useful hints as to the cause of this crash.
In addition, this particular bug appears to have been
*** This bug is a duplicate of bug 428238 ***
https://bugs.launchpad.net/bugs/428238
** This bug has been marked a duplicate of bug 428238
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache() -
mythfilldatabase assert failure: *** glibc detected ***
/usr/bin/mythfill
*** This bug is a duplicate of bug 428238 ***
https://bugs.launchpad.net/bugs/428238
** This bug has been marked a duplicate of bug 428238
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache() -
mythfilldatabase assert failure: *** glibc detected ***
/usr/bin/mythfill
** Summary changed:
- (SIGSEGV in MythDB::ClearSettingsCache) mythfilldatabase assert failure: ***
glibc detected *** /usr/bin/mythfilldatabase: corrupted double-linked list:
0x085b28a0 ***
+ mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache() -
mythfilldatabase assert f
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. There have been a few important fixes to mythtv since the 9.10
mythbuntu release. Can you can capture latest bug fixes by enabling the
auto-builds as described here: http://www.mythbuntu.org/auto-builds ?
Please note
** Changed in: file-roller (Ubuntu)
Importance: Undecided => Wishlist
--
"Open With..." functionality in File Roller should lead to a submenu instead of
a dedicated window
https://bugs.launchpad.net/bugs/482654
You received this bug notification because you are a member of Ubuntu
Bugs, which
KyL416: it would be somewhat helpful if you could describe the need for
1.2.6, since it is actually quite old. Would it make more sense to get
something much more updated (Musepack SV8 libraries and tools. see
http://www.musepack.net/index.php?pg=src)?
Debian semi-related bug-report: http://bugs
Unfortunately it looks like this is going nowhere unless someone picks
up the upstream patch and updates it for current trunk.
** Changed in: mythtv (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: mythbuntu
Status: Confirmed => Won't Fix
--
[Hardy] mythtv-osd doesn't recogn
*** This bug is a duplicate of bug 460579 ***
https://bugs.launchpad.net/bugs/460579
** This bug has been marked a duplicate of bug 460579
Disabling pulse audio causing problems
--
mythtv frontend hogs audio device
https://bugs.launchpad.net/bugs/480457
You received this bug notification
** Changed in: ubuntu
Importance: Undecided => Wishlist
--
[needs-packaging] Wayland
https://bugs.launchpad.net/bugs/483001
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
http
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
Unsupported FM and Analog TV card Avermedia Super 007
https://bugs.launchpad.net/bugs/478473
You received this bug notification because you are a member of Ubuntu
B
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. I'm closing this bug for two reasons:
1. The stack trace appears to be useless (no debug symbols available)
2. This is the only report we've seen for this type of crash, so it is either a
one-off crash, or possibly a c
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could both of you please open new tickets after following
the "basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#De
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could both of you please open new tickets after following
the "basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#De
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could you please open a new ticket after following the
"basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#Debugging
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could you please open a new ticket after following the
"basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#Debugging
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could you please open a new ticket after following the
"basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#Debugging
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could you please open a new ticket after following the
"basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#Debugging
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could you please open a new ticket after following the
"basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#Debugging
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could you please open a new ticket after following the
"basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#Debugging
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could you please open a new ticket after following the
"basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#Debugging
0.21 is receiving no development time or resources, so I am closing this
ticket.
If this is still reproducable, could you please open a new ticket after
following the "basic backtrace" directions outlined at the link below?
http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages
Than
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could you please open a new ticket after following the
"basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#Debugging
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Could you reply back with a bit more info:
1. Have you updated to the latest version (preferrably auto-builds, described
here: http://www.mythbuntu.org/auto-builds) after the official release?
2. After updating, have y
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Could you reply back with a bit more info:
1. Have you updated to the latest version (preferrably auto-builds, described
here: http://www.mythbuntu.org/auto-builds) after the official release?
2. After updating, have y
Fix is committed to 10.04 and will appear on the next alpha release.
Question is still open if this will be backported to 9.10.
** Changed in: mythtv-status (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: mythtv-status
Status: Confirmed => Fix Committed
** Summary change
Did comment #3 resolve the issue for you? Please report back either
way. Thanks!
** Changed in: mythtv (Ubuntu)
Status: New => Incomplete
--
Mythfrontend freezes after upgraded Kubuntu 9.04 -> 9.10
https://bugs.launchpad.net/bugs/485800
You received this bug notification because you are
** Changed in: gclcvs (Ubuntu)
Importance: Undecided => High
** Changed in: gclcvs (Ubuntu)
Status: Confirmed => Triaged
--
gclcvs segfaults during clc initialization
https://bugs.launchpad.net/bugs/411073
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Changed in: libsvm (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: libsvm (Ubuntu)
Status: New => Triaged
--
Please sync libsvm (2.90-1) with Debian testing
https://bugs.launchpad.net/bugs/500045
You received this bug notification because you are a member of Ubuntu
Bugs, w
Setting as incomplete since a maintainer is awaiting a response from the
original reporter.
** Changed in: mythtv (Ubuntu)
Importance: Undecided => Medium
** Changed in: mythtv (Ubuntu)
Status: New => Incomplete
--
package mythtv-database 0.22.0+fixes22594-0ubuntu1 failed to install/u
Support for Antec Veris RM100 and RM200 was released and is included in 9.10:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/karmic/lirc/karmic/revision/37
** Changed in: lirc (Ubuntu)
Milestone: None => ubuntu-9.10
--
Antec Veris isn't supported natively, even though all the right modu
Sasa and Dirk, thank you for hunting down this ticket to add your
useful info. Could one of you please open a new ticket since this one
is closed? After doing that, please:
1. Post that bug number to this ticket so that it is easy for others to find
2. Dirk, please add to that ticket if you are
Howdy, and thank you for helping to improve Mythbuntu by opening this
bug. Unfortunately, through no fault of your own, the traces contained
in this report are incomplete. Future PPA-based builds (see
http://www.mythbuntu.org/auto-builds) will hopefully have better
trace info. Please don't let
Hello Jonnanthan, are you working on a code or script patch? If so,
please assign the bug to you. If not, its status should probably remain
triaged rather than "In progress" since "In progress" gives the
impression someone is working on a patch.
** Changed in: msttcorefonts (Ubuntu)
Importanc
Upstream has a report on this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549882
** Bug watch added: Debian Bug tracker #549882
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549882
** Changed in: msttcorefonts (Ubuntu)
Importance: Undecided => Critical
** Changed in: msttcorefonts
*** This bug is a duplicate of bug 464422 ***
https://bugs.launchpad.net/bugs/464422
** This bug has been marked a duplicate of bug 464422
fail to complete upgrade jaunty > karmic ttf-mscorefonts-installer
--
install msttcorefont failed
https://bugs.launchpad.net/bugs/469986
You receive
*** This bug is a duplicate of bug 464422 ***
https://bugs.launchpad.net/bugs/464422
** This bug has been marked a duplicate of bug 464422
fail to complete upgrade jaunty > karmic ttf-mscorefonts-installer
--
relatively virgin karmic final release issuing "sudo apt-get install
ubuntu-r
*** This bug is a duplicate of bug 464422 ***
https://bugs.launchpad.net/bugs/464422
** This bug has been marked a duplicate of bug 464422
fail to complete upgrade jaunty > karmic ttf-mscorefonts-installer
--
package ttf-mscorefonts-installer 3.0 failed to install/upgrade: subprocess
i
*** This bug is a duplicate of bug 464422 ***
https://bugs.launchpad.net/bugs/464422
** This bug has been marked a duplicate of bug 464422
fail to complete upgrade jaunty > karmic ttf-mscorefonts-installer
--
package ttf-mscorefonts-installer 3.0 failed to install/upgrade
https://bugs.l
*** This bug is a duplicate of bug 464422 ***
https://bugs.launchpad.net/bugs/464422
** This bug has been marked a duplicate of bug 464422
fail to complete upgrade jaunty > karmic ttf-mscorefonts-installer
--
package ttf-mscorefonts-installer 3.0 failed to install/upgrade: subprocess
i
** Summary changed:
- fail to complete upgrade jaunty > karmic ttf-mscorefonts-installer
+ package ttf-mscorefonts-installer 3.0 failed to install/upgrade
--
package ttf-mscorefonts-installer 3.0 failed to install/upgrade
https://bugs.launchpad.net/bugs/464422
You received this bug notificatio
Howdy, 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 MythTV developers have turned their efforts to
the next version (0.22) and beyond and are no longer fixing bugs on
0.21.
The Mythbuntu t
Howdy, we really do appreciate you opening this ticket to help improve
Mythbuntu, but we need to close this ticket since no response has been
received to the previous question. If this problem is still occurring,
please do not hesitate to re-open this ticket with the requested
information.
Tha
Howdy, 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 MythTV developers have turned their efforts to
the next version (0.22) and beyond and are no longer fixing bugs on
0.21.
The Mythbuntu t
Confirming since upstream appears to be interested in this bug.
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Confirmed
--
Recording will not commence until a PMT is set.
https://bugs.launchpad.net/bugs/229797
You received this bug notification because you are a member of Ubuntu
Bu
This is indeed something upstream plans to tackle, but it most certainly
won't be in 0.21, and is VERY unlikely to be in (or backported to) 0.22.
** Changed in: mythtv (Ubuntu)
Status: New => Confirmed
--
Add pulseaudio output support
https://bugs.launchpad.net/bugs/311328
You received th
** Visibility changed to: Public
--
mythbackend crashed with SIGSEGV in _int_malloc()
https://bugs.launchpad.net/bugs/449465
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
https:
** Changed in: mythbuntu
Status: Fix Committed => Fix Released
--
ARGS line in /etc/defaults/mythbackend causes init script to hang
https://bugs.launchpad.net/bugs/450278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Public bug reported:
Binary package hint: mythtv
It appears that the version string no longer contains the upstream
changeset. I haven't checked "mythbackend --version", but here is what
the backend log has in it:
2009-10-16 19:53:01.374 mythbackend version: tags/release-0-22-rc1 []
www.mythtv.
** Changed in: mythtv (Ubuntu)
Status: New => Fix Committed
--
Bogus version in mythbackend.log
https://bugs.launchpad.net/bugs/455525
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.
Looks like this button is not designed to change the recording
schedule... it simply causes the duplicate detector to forget about that
show so that it *could* re-record it: http://www.gossamer-
threads.com/lists/mythtv/users/395009
Without studying all the possibilities, at first glance it seems
Fix was released in 9.10 RC.
** Changed in: mythbuntu
Status: In Progress => Fix Released
--
avi extension configured for default player (mplayer)
https://bugs.launchpad.net/bugs/445984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
@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:
https://bugs.launchpad.net/ub
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 abo
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
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:
Up
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 Ubu
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 about
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 af
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 v
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 via
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 be
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 seem
801 - 900 of 1068 matches
Mail list logo
