Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. I am closing this ticket for a combination of reasons:
1. This ticket is quite old and the mythtv developers upstream have stopped
focusing on 0.21 based reports
2. This issue would need to be reproduced on 0.22 with
Howdy, and thank you for helping to improve Mythbuntu and MythTV by
opening this ticket. Thanks to you, this bug has been found and will be
resolved in a Mythbuntu build in the near future! Any build /
distribution after 21949 will contain the fix.
Thanks again!
** Changed in: mythtv
Howdy, and thank you for helping to improve Mythbuntu and MythTV by
opening this ticket. Thanks to you, this bug has been found and will be
resolved in a Mythbuntu build in the near future! Any build /
distribution after 21949 will contain the fix.
Thanks again!
** Changed in: mythtv (Ubuntu)
Sorry, I was doing a bunch of things at once and didn't get a chance at
the time to see if that existed when the error popped up. Since it
popped up immedately after the upgrade reboot, it is possible the file
hadn't been created yet... looks like it got created eventually:
Ticket was opened at
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket.
Can you think of any reason the /home/mythtv directory wouldn't exist,
or couldn't be created? Is NFS, mount points, or partitions involved in
/home or /home/mythtv?
Also, was this a new install of mythtv, or an
I know I'm commenting on a closed bug here, but comment #2 worries me:
I'm not sure that, this far into the intrepid support cycle, it's justified
to make this intrusive of a
change via SRU for a one-time upgrade bug that most users will have already
dealt with.
Since 8.04 / Hardy is an
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. The mythtv developers upstream have stopped focusing on 0.21
based reports in preparation for a 0.22 release later this year. If you
are so inclined, you can see if this problem is reproducable with 0.22 -
if it is,
Closing. Solution is outlined in Comment #5, which summarizes what
upstream said regarding the last four digits.
** Changed in: mythplugins (Ubuntu)
Status: New = Invalid
--
[8.10] mythzmserver will not display live feed
https://bugs.launchpad.net/bugs/276942
You received this bug
*** This bug is a duplicate of bug 428473 ***
https://bugs.launchpad.net/bugs/428473
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32053499/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/32053500/ProcMaps.txt
** Attachment
*** This bug is a duplicate of bug 428473 ***
https://bugs.launchpad.net/bugs/428473
Mario, anything you want to know or see before I blow this install away
and start over?
--
jamu.py crashed with MythError in __init__()
https://bugs.launchpad.net/bugs/432897
You received this bug
** Bug watch added: mythtv.org bug tracker #7098
http://svn.mythtv.org/trac/ticket/7098
** Also affects: mythtv via
http://svn.mythtv.org/trac/ticket/7098
Importance: Unknown
Status: Unknown
--
mythfrontend.real crashed with SIGSEGV in MythGenericTree::getRouteByString()
** Bug watch added: mythtv.org bug tracker #7097
http://svn.mythtv.org/trac/ticket/7097
** Also affects: mythtv via
http://svn.mythtv.org/trac/ticket/7097
Importance: Unknown
Status: Unknown
** Changed in: mythtv (Ubuntu)
Status: New = Confirmed
--
mythfrontend.real
This has been fixed in the upcoming 9.10 release of Mythbuntu which has
version 0.22 of MythTV.
** Changed in: mythplugins (Ubuntu)
Status: New = Fix Committed
--
flash does not work in mythbrowser
https://bugs.launchpad.net/bugs/365361
You received this bug notification because you are
Command 'mythtv' still crashes like reported in first post, maybe it
is not intended to run directly?
That is correct. It is an unfortunately named test application. mythtv-test
would be an infinitely better name.
Even still, upstream has corrected the crashes of this app in
** Changed in: mythbuntu
Status: Confirmed = Fix Committed
--
[karmic] [MCC] Plugins tab is incorrectly selected on startup
https://bugs.launchpad.net/bugs/428691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: mythbuntu
Status: Confirmed = Fix Committed
--
[karmic] Tabs in MCC do not appear selected when clicked with the mouse
https://bugs.launchpad.net/bugs/428689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: mythbuntu
Status: Triaged = Fix Committed
--
[karmic] MythControls appears as a plugin in MCC but has been removed from
repository
https://bugs.launchpad.net/bugs/428683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
mythfilldatabase crashed with SIGSEGV in
This looks to be the same error as Bug #370146, but since this is the
first occurance I've seen with 0.22, maybe we should maybe keep this
separate and open for now.
** Changed in: mythtv (Ubuntu)
Status: New = Confirmed
--
mythfilldatabase crashed with SIGSEGV in
This same error has been reproduced in with MythTv 0.22 (see bug
#428959).
** Changed in: mythbuntu
Status: Incomplete = Confirmed
** Changed in: mythtv (Ubuntu)
Status: Incomplete = Confirmed
--
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
See Bug #429069 for report of this from a MythTV 0.22 install on Karmic
/ 9.10.
** Changed in: mythtv (Ubuntu)
Status: Incomplete = Confirmed
--
mythfilldatabase crashed with SIGSEGV in QMutex::lock()
https://bugs.launchpad.net/bugs/210246
You received this bug notification because you
*** This bug is a duplicate of bug 210246 ***
https://bugs.launchpad.net/bugs/210246
** This bug has been marked a duplicate of bug 210246
mythfilldatabase crashed with SIGSEGV in QMutex::lock()
--
mythfrontend.real crashed with SIGSEGV in QMutex::lock()
*** This bug is a duplicate of bug 210246 ***
https://bugs.launchpad.net/bugs/210246
Howdy, and thank you very much for helping to make Mythbuntu better by
reporting this issue with MythTV 0.22 which is to be included with
Mythbuntu 9.10 . We are still researching how to debug it further.
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. The mythtv developers upstream have stopped focusing on 0.21
based reports in preparation for a 0.22 release later this year. Can
you please try to see if this bug is reproducible on 0.22? If it is, we
can try to
*** This bug is a duplicate of bug 428238 ***
https://bugs.launchpad.net/bugs/428238
** This bug has been marked a duplicate of bug 428238
(SIGSEGV in MythDB::ClearSettingsCache) mythfilldatabase assert failure: ***
glibc detected *** /usr/bin/mythfilldatabase: corrupted double-linked
Howdy, and thank you for helping to improve Mythbuntu by reporting this issue.
This problem has been seen by a few other users, and is still under
investigation.
Looks like the assert was likely caused by the same thing as the
SIGSEGV in MythDB::ClearSettingsCache reports:
#14 0x003e27c9 in
One suggestion I found via google:
Chances are very good that it is a pointer problem. valgrind is particularly
good at tracking down pointer problems, so I suggest you take a look at that
--
(SIGSEGV in MythDB::ClearSettingsCache) mythfilldatabase assert failure: ***
glibc detected ***
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. The mythtv developers upstream have stopped focusing on 0.21
based reports in preparation for a 0.22 release later this year. Can
you please try to see if this bug is reproducible on 0.22? If it is, we
can try to
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. The mythtv developers upstream have stopped focusing on 0.21
based reports in preparation for a 0.22 release later this year. Can
you please try to see if this bug is reproducible on 0.22? If it is, we
can try to
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. Since many fixes have been added to the socket code in the
upcoming release (0.22), it is likely this has been resolved. We have
builds of mythtv 0.22 available on a PPA to test if you are so inclined
to check. Please
Howdy! This ticket is quite old and the mythtv developers upstream have
stopped focusing on 0.21 based reports in preparation for a 0.22 release
later this year. Can you please try to see if this bug is reproducible
on 0.22? If it is, we can try to forward this bug upstream to get the
right eyes
Howdy! This ticket is quite old and the mythtv developers upstream have
stopped focusing on 0.21 based reports in preparation for a 0.22 release
later this year. Can you please try to see if this bug is reproducible
on 0.22? If it is, we can try to forward this bug upstream to get the
right eyes
Howdy! This ticket is quite old and the mythtv developers upstream have
stopped focusing on 0.21 based reports in preparation for a 0.22 release
later this year. Can you please try to see if this bug is reproducible
on 0.22? If it is, we can try to forward this bug upstream to get the
right eyes
Howdy! This ticket is quite old and the mythtv developers upstream have
stopped focusing on 0.21 based reports in preparation for a 0.22 release
later this year. Can you please try to see if this bug is reproducible
on 0.22? If it is, we can try to forward this bug upstream to get the
right eyes
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
myth backend crashed
https://bugs.launchpad.net/bugs/360286
You
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 360286
myth backend crashed
** This bug is no longer a duplicate of bug 360286
myth backend crashed
** This bug has been marked a duplicate of bug 370146
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 360286
myth backend crashed
** This bug is no longer a duplicate of bug 360286
myth backend crashed
** This bug has been marked a duplicate of bug 370146
I haven't looked for an option to disable this, but if it isn't there,
it would fall under wishlist.
** Summary changed:
- [8.04] Mythtv retunes when beginning recording on channel
+ Wishlist: Mythtv retunes even when recording same channel
** Changed in: mythtv (Ubuntu)
Status: New =
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. Do you still see this crash? If so, have you run a memory test?
Thank you!
** Changed in: mythtv (Ubuntu)
Status: New = Incomplete
--
mythtv backend crash : double free or corruption (fasttop)
Howdy, and thank you for helping to improve Mythbuntu. The mythtv
developers upstream have stopped focusing on 0.21 based reports in
preparation for a 0.22 release later this year. Is this issue
reproducible on 0.22? If it is, we can try to forward this bug upstream
with a stacktrace/backtrace
*** This bug is a duplicate of bug 210246 ***
https://bugs.launchpad.net/bugs/210246
** This bug has been marked a duplicate of bug 210246
mythfilldatabase crashed with SIGSEGV in QMutex::lock()
--
mythfilldatabase crashed with SIGSEGV in QMutex::lock()
I believe this issue has been addressed in the 8 months since this bug
report was issued.
Since upstream is focused on 0.22, any future bug reports would need to
be against that version. We have builds of mythtv 0.22 available on a
PPA to test. Please follow the directions at
*** This bug is a duplicate of bug 210246 ***
https://bugs.launchpad.net/bugs/210246
** This bug has been marked a duplicate of bug 210246
mythfilldatabase crashed with SIGSEGV in QMutex::lock()
--
mythfilldatabase crashed with SIGSEGV in QMutex::lock()
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
mythfilldatabase crashed with SIGSEGV in
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
mythfilldatabase crashed with SIGILL in
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
mythfilldatabase crashed with SIGSEGV in
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
Multiple strange mythtv problems, mythfilldatabase crashed with SIGSEGV
Howdy, and thank you for helping to improve Mythbuntu! I don't think
upstream can use this stack trace - the symbols are missing (no fault of
yours). Has this crash reoccured in the past two weeks since you first
reported it?
Mario, do the latest trunk builds have debugging symbol info?
**
** Bug watch added: mythtv.org bug tracker #7030
http://svn.mythtv.org/trac/ticket/7030
** Also affects: mythtv via
http://svn.mythtv.org/trac/ticket/7030
Importance: Unknown
Status: Unknown
--
mythfilldatabase crashed with SIGSEGV in
Howdy, and thank you for helping to improve Mythbuntu by reporting this issue.
I am closing this ticket for a combination of reasons:
1. It is missing symbol information needed to help debug the issue
2. There are no other reports of this issue
3. This ticket is quite old and the mythtv
Howdy, and thank you for helping to improve Mythbuntu by reporting this issue.
I am closing this ticket for a combination of reasons:
1. It appears that a partial cause of this crash was mythphone, and it is no
longer supported
2. There are no other reports of this issue
3. This ticket is
Howdy, and thank you for helping to improve Mythbuntu by reporting this issue.
I am closing this ticket for a combination of reasons:
1. The user interface is being totally re-written for 0.22, so it is likely
this is fixed
2. Mythmusic itself is being re-written for 0.23
3. There are no
*** This bug is a duplicate of bug 416100 ***
https://bugs.launchpad.net/bugs/416100
** This bug has been marked a duplicate of bug 416100
mythtv crashed with SIGSEGV in TV::DoEditSchedule()
--
mythtv crashed with SIGSEGV in TV::DoEditSchedule()
https://bugs.launchpad.net/bugs/415149
You
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
mythfilldatabase crashed with SIGSEGV in
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
mythfilldatabase crashed with SIGSEGV in
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
mythfilldatabase crashed with SIGSEGV in
*** This bug is a duplicate of bug 370146 ***
https://bugs.launchpad.net/bugs/370146
** This bug has been marked a duplicate of bug 370146
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
--
mythfilldatabase crashed with SIGILL in
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. The mythtv developers upstream have stopped focusing on 0.21
based reports in preparation for a 0.22 release later this year. If
this bug is reproducible on the latest version of 0.21 from the PPA
/weekly-fixes, could
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. I am closing this ticket for a combination of reasons:
1. It is missing symbol information needed to help debug the issue (not your
fault)
2. The decoders have been refreshed in the upcoming version (0.22)
3. There
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. Since the mythtv has moved to QT4, these portions of code have
been completely revamped for the next release (0.22) and it is likely
this has been resolved. We have builds of mythtv 0.22 available on a PPA
to test if
*** This bug is a duplicate of bug 279500 ***
https://bugs.launchpad.net/bugs/279500
** This bug has been marked a duplicate of bug 279500
mythbackend crashed with SIGSEGV in QValueListQString::detachInternal()
--
mythbackend crashed with SIGSEGV in QValueListQString::detachInternal()
These error messages from the DpkgTerminalLog look worrisome:
1.
/usr/bin/mandb: can't write to /var/cache/man/17379: No space left on device
2.
Creating new cluster (configuration: /etc/postgresql/8.4/main, data:
/var/lib/postgresql/8.4/main)...
initdb: nelze vytvoÅ$(1C-(Bt adresáÅ$(1
Howdy Pavel, Thank you very much for helping to improve Mythbuntu by
reporting this issue. Are you still having trouble, or did you resolve
this somehow (and if so, how?).
--
package mythtv-backend 0.22.0~trunk21556-0ubuntu1 failed to install/upgrade:
podproces instalovaný post-installation
As I suspected, upstream said the current backtrace isn't usable.
--
mythfilldatabase crashed with SIGSEGV in
NetInterfaceTrafficStats::NetInterfaceTrafficStats()
https://bugs.launchpad.net/bugs/421314
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: mythtv.org bug tracker #7034
http://svn.mythtv.org/trac/ticket/7034
** Also affects: mythtv via
http://svn.mythtv.org/trac/ticket/7034
Importance: Unknown
Status: Unknown
--
mythbackend crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/371782
You
Closing at request of ticket reporter.
** Changed in: mythtv (Ubuntu)
Status: New = Invalid
--
mythfrontend.real crashed on startup with SIGSEGV in QGLWidget::resizeEvent()
https://bugs.launchpad.net/bugs/361001
You received this bug notification because you are a member of Ubuntu
Bugs,
Howdy, and thank you for helping to improve Mythbuntu by reporting this
issue. The mythtv developers upstream have stopped focusing on 0.21
based reports in preparation for a 0.22 release later this year. Can
you please try to see if this bug is reproducible on 0.22? If it is, we
can try to
*** This bug is a duplicate of bug 360345 ***
https://bugs.launchpad.net/bugs/360345
** This bug has been marked a duplicate of bug 360345
mythfrontend.real crashed with SIGSEGV in
mythvideo_videomanager::ManualSearchUIDHandler::OnExit()
--
mythfrontend.real crashed with SIGSEGV in
Howdy, and thank you for helping to improve lcdproc and Ubuntu. I am
marking this ticket as confirmed since this ticket seems to contain all
the necessary information. Thank you for attaching an easy and low risk
solution.
** Changed in: lcdproc (Ubuntu)
Status: New = Confirmed
--
Howdy, and thank you for helping to improve Mythbuntu! I'm going to
take a few stabs in the dark here:
1. LCDd may not be running. Perhaps try sudo service LCDd restart
2. Could you try exiting mythfrontend and then kill mythlcdserver. Then
restart mythlcdserver and see if the system time
*** This bug is a duplicate of bug 415922 ***
https://bugs.launchpad.net/bugs/415922
Thank you, Pavel!
--
mythfrontend.real crashed with SIGFPE in QMutexPool::get()
https://bugs.launchpad.net/bugs/420932
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Pavel Mlčoch reported in Bug #420932 that removing the mythstream plugin
was solving this issue for him.
** Changed in: mythtv (Ubuntu)
Status: New = Confirmed
--
mythfrontend.real crashed with SIGFPE in QMutexPool::get()
https://bugs.launchpad.net/bugs/415922
You received this bug
Howdy Brian. Did you ever resolve this? If so, how? If not, you
might try to verify aspects of your hardware, including checking your
CPU temperature during load, and running a memory test.
** Changed in: mythtv (Ubuntu)
Status: New = Incomplete
--
frontend dies with illegal
Public bug reported:
Binary package hint: mythstream
If we pulled this in soon, it might stop the crash reports...
http://home.kabelfoon.nl/~moongies/streamtuned.html
** Affects: mythbuntu
Importance: Undecided
Status: New
** Affects: mythstream (Ubuntu)
Importance:
Mythstream is being dropped from Mythbuntu since there is only limited
time and it is not an official plugin.
** Changed in: mythbuntu
Status: New = Won't Fix
** Changed in: mythstream (Ubuntu)
Status: New = Invalid
--
streamer has no video player options, defaults don't work
There are other fixes and patches (also from the minimyth maintainer) described
on the mythtv mailing list.
You are welcome to investigate and integrate these yourself, but they won't be
distributed officially via Mythbuntu.
Closing (would close as WONTFIX, but that isn't an option in the
Howdy Jan, any chance you could check out a 9.10 alpha and see if it is
still as messed up? Thanks!
--
ofdb.py crashed with ImportError in module()
https://bugs.launchpad.net/bugs/378384
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mythtv (Ubuntu)
Status: New = Confirmed
--
[jaunty] mythfrontend 0.22 from ppa trunk fails to start
https://bugs.launchpad.net/bugs/424716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
*** This bug is a duplicate of bug 415922 ***
https://bugs.launchpad.net/bugs/415922
Howdy, and thank you for helping to improve Mythbuntu.
Someone else has run into this problem as well and appears to have been
able to resolve it by removing one or more of the packages, but
unfortunately we
*** This bug is a duplicate of bug 415922 ***
https://bugs.launchpad.net/bugs/415922
Howdy, and thank you for helping to improve Mythbuntu.
Someone else has run into this problem as well and appears to have been
able to resolve it by removing one or more of the packages, but
unfortunately we
*** This bug is a duplicate of bug 415922 ***
https://bugs.launchpad.net/bugs/415922
Howdy, and thank you for helping to improve Mythbuntu.
Someone else has run into this problem as well and appears to have been
able to resolve it by removing one or more of the packages, but
unfortunately we
Two more reports of this, so I'm re-opening, barely.
Everyone with this problem, please report back the output of the
following command executed from a terminal (shell) window:
cat /proc/cpuinfo
** Changed in: mythtv (Ubuntu)
Status: Invalid = Incomplete
--
package mythtv-backend
Two people edited same bug at same time. Please open a new bug with new
logs attached. Thank you!
** Changed in: mythtv (Ubuntu)
Status: Incomplete = Invalid
--
package mythtv-backend 0.21.0+fixes18722-0ubuntu1 failed to install/upgrade:
subprocess post-installation script returned
Howdy Martin. Minor clarification on option #1: I was suggesting that
when duplicates are discovered, the private ones are left private and
are marked as duplicates of the public bugs. There would be no exposure
to sensitive information and QA people could do their job! I'll leave
it up to you
After compiling together information and posting to the mythtv-users
list, I have received no responses - so I'm afraid that the only course
forward is for one of you to either upgrade to alpha 0.22, or do a
parallel install (anyone have a spare drive or partition?) to see if the
problem is still
Howdy, and thank you for helping to improve Mythtv and Mythbuntu. The
upstream mythtv bug that you mention (5744) contains a comment which
seems to imply that the fix does not work properly for 0.22. If you
believe that to not be the case, you might consider re-opening that
ticket (and also
Sorry, hopefully someone else can chime in and help here regarding the
status of themes, and/or how to work around this. Multiple people are
running 0.22, and it shouldn't matter that most are probably on 9.10.
Questions I have about this:
Should the theme really be pulled from a directory with
** Changed in: mythbuntu
Importance: Undecided = High
** Changed in: mythbuntu
Status: New = Confirmed
** Changed in: mythbuntu-common (Ubuntu)
Status: New = Confirmed
--
Can't enable automatic login in MCC
https://bugs.launchpad.net/bugs/422238
You received this bug
** Changed in: mythbuntu
Status: New = Incomplete
--
USB remote stops working
https://bugs.launchpad.net/bugs/421276
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Here is the lircd.conf that I developed. It uses naming that is
compatible with the mce remotes since it basically is one.
** Attachment added: lircd.conf.gyration (uses mce remote naming)
http://launchpadlibrarian.net/31102972/lircd.conf.gyration
--
Gyration Media Center Universal Remote
** Attachment added: .lircrc/mythtv file (uses same names as mce .lircrc)
http://launchpadlibrarian.net/31103061/mythtv.lircrc
** Changed in: mythbuntu
Status: Incomplete = Confirmed
--
Gyration Media Center Universal Remote Control needs an entry in the remote
section
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
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.
--
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:
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
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.
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
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
801 - 900 of 1080 matches
Mail list logo
