@leamas-alec Any ideas on a proper fix?
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235
Title:
lirc broken on 18.04
Status in lirc package in Ubuntu:
Confirmed
Bug
Yes, via the PPA. Guess I should have waited for the trusty-proposed...
:-(
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythtv in Ubuntu.
https://bugs.launchpad.net/bugs/1323391
Title:
Update to 0.27.1 point release
Status in
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 Mythbuntu
Bug Team, which is subscribed to mythtv in Ubuntu.
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 Mythbuntu
Bug Team, which is subscribed
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
Howdy, and thank you for helping to improve Mythbuntu and MythTV by
opening this ticket. If you have not already, please be sure to enable
the repos to pick up the proposed fixed that Karl mentions (see
http://www.mythbuntu.org/repos for more info).
** Changed in: mythbuntu
Importance:
** Summary changed:
- mythfrontend.real crashed with SIGSEGV in _int_malloc()
+ mythfrontend 0.24 crash after resuming from bookmark
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/689300
Howdy, and thank you for helping to improve Mythbuntu, not only by
opening this ticket, but suggesting a solution. With a proposed
solution, I'm marking this as Triaged.
** Changed in: mythbuntu
Status: New = Triaged
** Changed in: mythbuntu
Importance: Undecided = High
--
You
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/mythbuntu/+bug/890038/+attachment/2596061/+files/CoreDump.gz
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/890038
Title:
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. I've forwarded the details to the developers - we'll see if
they can find anything!
** Bug watch added: code.mythtv.org/trac/ #10598
http://code.mythtv.org/trac/ticket/10598
** Also affects: mythtv via
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 Mythbuntu
Bug Team, which is subscribed to mythtv in Ubuntu.
https://bugs.launchpad.net/bugs/949291
Title:
mythbackend crashed with SIGSEGV in
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 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 Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
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 Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
** 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 Mythbuntu
Bug
Focus is on the upcoming 0.25 release of MythTV (which will be included
in Ubuntu 12.04) and the original reporter does not find the problem
there.
** Changed in: mythbuntu
Importance: High = Low
** Changed in: mythbuntu
Status: Incomplete = Won't Fix
--
You received this bug
I was told that if the bug is not apparent in 0.25, then a bug against
0.24 would likely be closed on their Trac system anyway.
If the cause of the bug was very apparent, there is a chance it would
be fixed in 0.24, but your statement is quite accurate - the
developers focus is on 0.25 at this
thank dekarl for pointing to the change!
** Changed in: mythbuntu
Status: New = Fix Released
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/923785
Title:
mythweb 0.25 apache config
Howdy, and thank you for helping to improve Mythbuntu by opening this ticket.
Unfortunately, these crash type bugs are typically rejected unless there is a
core dump or threadtrace information. If a crash is reproducible, then logs
are sometimes enough... I would suggest starting mythtv-setup
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 Mythbuntu
Bug Team, which is subscribed to mythtv-status in 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)
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 Mythbuntu
Bug Team, which is subscribed to
Yes, the -v playback would be useful (in fact, necessary).
If you can update your vlc, or install mplayer
(http://www.silicongadget.com/guides/software-guides/multimedia-software-guides/update-mplayer-on-ubuntu/2119/),
that would also be helpful to understand if it is a problem
specifically with
** 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 Mythbuntu
Bug Team, which is subscribed to MythTV.
Howdy, and thank you for helping to improve MythTV, not only by opening
this ticket, but also forwarding the bug upstream. I copied your log
file and traces upstream as well so that the developers there can
continue looking at it.
** Changed in: mythbuntu
Importance: Undecided = High
**
There have been a few improvements added to the -fixes branch. Can you
please re-test? If it still fails, please verify the disk works great
with external applications (mplayer or vlc), and if so, capture a new
log with -v playback on the frontend command line.
--
You received this bug
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
** Visibility changed to: Public
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/567688
Title:
Frontend formatting issues
Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
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
And make sure the display is turned on during boot-up.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/888202
Title:
Mythbuntu 11.10 does not switch away from splash on startup (Fresh
Public bug reported:
Problem:
Using 11.10 .iso and requesting a FE-only install, mythbackend is still
installed at the end of the process.
Expected:
To minimize disk space usage at all times, mythtv-backend should not be
installed at all, but if that is not possible, it should at least be
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 Mythbuntu
Bug Team, which is subscribed to mythtv in Ubuntu.
https://bugs.launchpad.net/bugs/868890
Title:
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 Mythbuntu
Bug Team, which is subscribed to
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
Do you have a way to change languages at all (i.e, if you hit your menu
button on your remote, can you select different audio tracks, and/or
select the root or alternative menus and get to language selection)?
** Changed in: mythbuntu
Importance: High = Low
** Changed in: mythbuntu
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 upstream MythTV developers have turned their
efforts to newer versions and and are no longer fixing bugs on this
version of MythTV.
The
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/mythbuntu/+bug/764754/+attachment/2061028/+files/CoreDump.gz
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/764754
Title:
I'm going to mark this one as fixed because upstream has fixed a number
of LiveTV issues. If you get another crash after updating to the latest
versions of 0.24, absolutely please submit a new bug. Thank you!
** Changed in: mythbuntu
Status: New = Fix Released
--
You received this bug
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
Sorry for the delay - I've forwarded this upstream. They may have
already fixed it, in which case this'll just be closed.
** Bug watch added: code.mythtv.org/trac/ #9907
http://code.mythtv.org/trac/ticket/9907
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/9907
Howdy, and thank you for opening this ticket - I've forwarded the issue
upstream.
** Bug watch added: code.mythtv.org/trac/ #9908
http://code.mythtv.org/trac/ticket/9908
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/9908
Importance: Unknown
Status: Unknown
**
Howdy, and thank you for opening this ticket. When you say crashes, do
you mean that the frontend completely stops and either takes you back to
the window manager, or restarts? If so, does apport give you the
opportunity to submit a crash report? You can check /var/crash to see
if there is a
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/mythbuntu/+bug/709607/+attachment/1813798/+files/CoreDump.gz
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/709607
Title:
Looks like this will finally be fixed when 0.25 gets released someday.
** Changed in: mythbuntu
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to MythTV.
https://bugs.launchpad.net/bugs/718166
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 Mythbuntu
Bug Team, which is subscribed to MythTV.
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 Mythbuntu
Bug Team, which is subscribed to MythTV.
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 Mythbuntu
Bug Team, which is subscribed to mythtv in Ubuntu.
https://bugs.launchpad.net/bugs/490920
Title:
** 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 Mythbuntu
Bug Team, which is subscribed
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 both for reporting and confirming this issue. Do
either of you know, either from yourself or other reports you've found
elsewhere if this afflicts Wubi installs on standard Ubuntu?
** Changed in: mythbuntu
Status: New = Confirmed
--
You received this bug
** Description changed:
After performing an apt-get update apt-get upgrade today (1/19),
mythbackend is no longer stable. There is no exiting information
contained in the mythbackend.log file, however there are numerous
reports of MainServer, Warning: Unknown socket closing MythSocket
mythwelcome stands out: Can you try stopping that before issuing your
reboot / shutdown?
mythwelco 2057 os 15u unix 0xf19d46c0 0t0
13737 /tmp/orbit-os/linc-809-0-504602c3abbd0
mythwelco 2057 os 16u unix 0xf172b3c0 0t0
13739
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Could you provide the logs that contain the exact error
message, and perhaps an ls -lsa listing of /tmp right before a reboot?
We don't have any reason to think this is Mythbuntu specific, but
perhaps the logs would
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:
Upstreamed
** Changed in: mythbuntu
Importance: Undecided = Medium
** Changed in: mythbuntu
Status: New = Triaged
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/727251
Title:
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/mythbuntu/+bug/727251/+attachment/1878979/+files/CoreDump.gz
** Attachment removed: .var.log.mythtv.mythfrontend.log.gz
** Tags added: mirobridge
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/574744
Title:
Mythbuntu Control Centre Error Popup in Mirobrige on Secondary Backend
Status in Mythbuntu, Ubuntu
** Tags added: mirobridge
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/558912
Title:
MCC error on startup
Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
Confirmed
Bug
** Tags removed: need-i386-retrace
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/mythbuntu/+bug/722420/+attachment/1863431/+files/CoreDump.gz
** Visibility changed to: Public
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is
** Bug watch added: code.mythtv.org/trac/ #9607
http://code.mythtv.org/trac/ticket/9607
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/9607
Importance: Unknown
Status: Unknown
** Changed in: mythbuntu
Importance: Undecided = Medium
** Changed in: mythbuntu
** Changed in: mythbuntu
Importance: Undecided = Medium
** Changed in: mythbuntu
Status: New = Triaged
** Bug watch added: code.mythtv.org/trac/ #7714
http://code.mythtv.org/trac/ticket/7714
** Changed in: mythtv
Remote watch: code.mythtv.org/trac/ #9580 = code.mythtv.org/trac/
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
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/mythtv/+bug/693985/+attachment/1774958/+files/CoreDump.gz
** Visibility changed to: Public
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/mythbuntu/+bug/718166/+attachment/1847289/+files/CoreDump.gz
** Bug watch added: code.mythtv.org/trac/ #9580
http://code.mythtv.org/trac/ticket/9580
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/9580
** Bug watch added: code.mythtv.org/trac/ #9581
http://code.mythtv.org/trac/ticket/9581
** Also affects: mythtv via
http://code.mythtv.org/trac/ticket/9581
Importance: Unknown
Status: Unknown
** Tags removed: lucid need-i386-retrace
** Visibility changed to: Public
--
You
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. It looks like part of your myth system is not upgrading because
of some dependencies. You might try seeing what types of actions sudo
apt-get dist-upgrade or Synaptic wants to perform - one of those two
might resolve
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 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 Mythbuntu
Bug Team, which is subscribed to mythtv in 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
Public bug reported:
When I launch mythtv-setup from System - Admin, or from MCC, it can not
probe my PVR-USB2 card. I have to launch from the command line with
sudo mythtv-setup in order for it to be able to probe.
** Affects: mythbuntu
Importance: Undecided
Status: New
--
You
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 Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
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 Mythbuntu
Bug Team, which is
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 Mythbuntu
Bug Team, which is subscribed to mythtv in ubuntu.
https://bugs.launchpad.net/bugs/664559
Title:
VDPAU Error in mythfrontend.log although using radeon
Status in
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 =
Howdy, and thank you for helping to improve Mythbuntu and mythtv by
opening this ticket.
I would suggest capturing a log of the scan by performing the following
commands. After doing so, you can either submit the log here and I'll
try to find time to forward it upstream, or you are welcome to
** Visibility changed to: Public
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/689300
Title:
mythfrontend.real crashed with SIGSEGV in _int_malloc()
Status in Mythbuntu, Ubuntu
Low, since you could just not use bookmarks.
** Bug watch added: mythtv.org bug tracker #9366
http://svn.mythtv.org/trac/ticket/9366
** Also affects: mythtv via
http://svn.mythtv.org/trac/ticket/9366
Importance: Unknown
Status: Unknown
** Changed in: mythbuntu
Importance:
1 - 100 of 327 matches
Mail list logo
