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 se
*** 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?
sched
*** 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 ind
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 here
** 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 man
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"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/978464/+att
** 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, wh
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 up
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: m
*** 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
mythfro
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
h
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
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 notifi
*** 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, which
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)
Import
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:
Marverick Mythbuntu RC did not have trouble when I reported Bug #651800
--
[Maverick] ubuntu-bug fails when reporting a bug about ubiquity
https://bugs.launchpad.net/bugs/653046
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
I should have noted that my report against ubiquity was done from the
live-cd environment, not a installed system.
--
[Maverick] ubuntu-bug fails when reporting a bug about ubiquity
https://bugs.launchpad.net/bugs/653046
You received this bug notification because you are a member of Ubuntu
Bugs,
Marking as Triaged since there is a valid looking stack trace. Lots of
reports in a VERY short period of time is worrisome for major impact, so
marking importance as critical for now. If it is determined to have
lower impact that what I think, feel free to lower importance.
** Changed in: upower
*** This bug is a duplicate of bug 604809 ***
https://bugs.launchpad.net/bugs/604809
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 604809
upowerd crashed with SIGSEGV in idevice_get_uuid()
* You can subscribe to bug 604809 by following this link:
https:/
*** This bug is a duplicate of bug 604809 ***
https://bugs.launchpad.net/bugs/604809
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 604809
upowerd crashed with SIGSEGV in idevice_get_uuid()
* You can subscribe to bug 604809 by following this link:
https:/
*** This bug is a duplicate of bug 604809 ***
https://bugs.launchpad.net/bugs/604809
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 604809
upowerd crashed with SIGSEGV in idevice_get_uuid()
* You can subscribe to bug 604809 by following this link:
https:/
*** This bug is a duplicate of bug 604809 ***
https://bugs.launchpad.net/bugs/604809
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 604809
upowerd crashed with SIGSEGV in idevice_get_uuid()
* You can subscribe to bug 604809 by following this link:
https:/
*** This bug is a duplicate of bug 604809 ***
https://bugs.launchpad.net/bugs/604809
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 604809
upowerd crashed with SIGSEGV in idevice_get_uuid()
* You can subscribe to bug 604809 by following this link:
https:/
Oops, wrong one
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 604809
upowerd crashed with SIGSEGV in idevice_get_uuid()
* You can subscribe to bug 604809 by following this link:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/604809/+subscribe
** This
Confirmed this behavior on post-install Mythbuntu 10.10 RC.
Leaving as status new because I'm what this should really be against:
1. Apport, for not gracefully handling a permission problem (but if this a
unique case, is having apport handle this the right thing to do vs. some other
solution?)
*** This bug is a duplicate of bug 546407 ***
https://bugs.launchpad.net/bugs/546407
** This bug has been marked a duplicate of bug 267488
apport should let the user see the crash details even if some packages are
obsolete
* You can subscribe to bug 267488 by following this link:
https:/
Howdy, and thank you for helping to improve Ubuntu by opening this ticket.
This is similar to Bug #267488, but that one simply requests the user to be
able to view the crash information.
This ticket requests the ability to override and submit the ticket anyway. I
know that I personally need th
Howdy, and thank you for helping to improve Ubuntu by opening this
ticket. I believe it is a duplicate of Bug 546407, so I am marking it
as such.
--
Vicious cycle: apport will not process reports for "obsolete packages" due to
failed upgrades
https://bugs.launchpad.net/bugs/563750
You received
*** This bug is a duplicate of bug 474701 ***
https://bugs.launchpad.net/bugs/474701
Howdy, and thank you for helping to improve Ubuntu by opening this
ticket. I believe this issue is the same as Bug #474701, so I'm going
to mark it as a duplicate of that one.
** Changed in: lirc (Ubuntu)
There definitely seems to be something amiss here. Bug #480555 has a
brute force work-around (he added the following code to /etc/rc.local
before final exit 0):
if [ ! -d /var/run/lirc ]; then
sudo mkdir /var/run/lirc
sudo ln -s /dev/lircd /var/run/lirc/lircd
fi
** Changed in: li
*** This bug is a duplicate of bug 474701 ***
https://bugs.launchpad.net/bugs/474701
** This bug is no longer a duplicate of bug 480555
No /var/run/lirc/lircd created, only /dev/lircd
** This bug has been marked a duplicate of bug 474701
Can't start lirc: "lircd: can't open or create /va
** 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 a
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 not
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: Triage
(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
ubunt
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
** 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
Ti
** 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 notificatio
** 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 notification
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.
https://bugs.launchpad.net/bugs/
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-
manager/+question/1
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
*** 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
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 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 packag
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 Ubun
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 t
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 h
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 affects
** 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
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.
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)
** 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 a
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 y
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)
St
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 upstart
** 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.
http
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
Ti
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
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://bugs.launchpad.net/bug
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.
https://bugs.launchpa
** 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"
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/949291/
** 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
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:
A distribution upgrade of Mythbuntu 10.04 to 10.10 results in the
following message which is decidedly not user friendly. It shows up
during installation of the 10.10 packages:
"xscreensaver and xlockmore must be restarted before upgrading
One or more running instances of x
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/647278/+attachment/1633573/+files/Dependencies.txt
--
Poorly handled upgrade of libc6
https://bugs.launchpad.net/bugs/647278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: update-manager
I'm doing a "graphical" distribution upgrade with "update-manager -d"
from 10.04 to beta 10.10. During the "installing the upgrade" step of
libc-bin, it shows what it calls a "terminal window", and within it is
the text based installer (dp
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/647283/+attachment/1633594/+files/Dependencies.txt
--
No instructions on how to click "OK" in package configuration
https://bugs.launchpad.net/bugs/647283
You received this bug notification because you are a member of Ub
Your dpkgTerminalLog has the following in it, which indicates that
either mysql is not running, or the password you are using to try to
connect to it is not correct. If the password in
/etc/mythtv/config.xml is not working for you, there is a suggested
course of action at the bottom of the error m
Howdy, and thank you for helping to improve Mythbuntu and mythtv by
opening this ticket. I have forwarded this bug report upstream.
If you get a chance, it might turn out to be helpful to the developers
if you coudl try to collect a short back-end log with --verbose
important,general,eit during t
Apparently this part of the code has changed considerably after the 0.23
release, so this issue is unlikely to be addressed in 0.23, and so would
need to be reproduced on 0.24 (which is still under heavy development).
If you have the ability to try this on a test partition (or system), it
would be
Tommi, while 0.24 works well for some people, there are a number of open
issues - so if there is a chance that you will need to revert back to
0.23.1, be sure to back up your database before upgrading to 0.24.
Changing to incomplete since upstream has said it needs to be reproduced
on 0.24
** Cha
Thank you for reporting back. Marking as fixed (abet in a future
release - likely 11.04).
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Fix Released
--
mythfrontend crashes when EPG changes (same as #613547)
https://bugs.launchpad.net/bugs/629852
You received this bug notification
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: my
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" d
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 notifica
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
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:
http://www.mythtv.org/wiki/Debu
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: http://
Bob, thank you for finding that problem. Adding kernel task in hopes
that they can make this change since it is super low risk.
** Changed in: lirc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lirc (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu)
Importanc
Looks like Ubuntu kernel will need to be patched on its own - Upstream
developer agreed that the proposed fix in this bug is proper for Ubuntu
since there no easy way to pull from upstream since code has changed:
(10:33:06 AM) j-rod: that code did go upstream, but has subsequently changed
(10:36:1
Thank you for reporting back.
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Fix Released
--
mythfrontend crashes on starting playback of some DVB recordings
https://bugs.launchpad.net/bugs/623039
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Howdy, and thank you for helping to improve MythTV and Ubuntu by opening
this ticket. Others that have encountered a similar problem have
noticed that changing playback profiles to one that does NOT use XvMC
has resolved this issue. Could you please try that, and perhaps other
profile options, an
*** This bug is a duplicate of bug 660833 ***
https://bugs.launchpad.net/bugs/660833
I am going to mark this bug as a duplicate of another one since it
appears to be the same issue. Please continue any discussion there.
** This bug has been marked a duplicate of bug 660833
mythtv crashes
*** This bug is a duplicate of bug 660833 ***
https://bugs.launchpad.net/bugs/660833
Howdy, and thank you for helping to improve MythTV and Ubuntu by opening
this ticket. Could you please report what video card you are using, and
if you are loading any video drivers, what version they are? T
Howdy, and thank you for helping to improve MythTV and Ubuntu by opening
this ticket. Others that have encountered a similar problem have noticed
that changing playback profiles to one that does NOT use XvMC has
resolved this issue. Could you please try that, and perhaps other
profile options, and
*** This bug is a duplicate of bug 665336 ***
https://bugs.launchpad.net/bugs/665336
Howdy, and thank you for helping to improve MythTV and Ubuntu by opening
this ticket. A later bug was created which has more extensive debug
logs, so I'm going to mark this one as a duplicate of that. Please
Howdy, and thank you for helping to improve MythTV and Ubuntu, not only
for opening this ticket, but figuring out some work-arounds. As a
result, I'm marking this ticket as confirmed.
** Changed in: mythtv (Ubuntu)
Importance: Undecided => High
** Changed in: mythtv (Ubuntu)
Status: Ne
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 =>
901 - 1000 of 1068 matches
Mail list logo
