Howdy and thank you for helping to improve Mythbuntu by opening this
ticket. Could you please generate a more extensive log with extra
debugging turned on so that we can submit it to the developers? To do
this, you would probably need to use the following commands in a
terminal window:
sudo /etc
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. I have forwarded trace upstream. Hopefully it will contain
enough information for them to act upon it. If not, this ticket will be
closed and we'll just have to fall back on our continued hope for
correct symbol suppor
Howdy again, unfortunately your log looks truncated. Not sure what
happened, but there is (comparatively speaking) nearly empty.
--
LNB configuration window does not appear under diseqc settings
https://bugs.launchpad.net/bugs/449023
You received this bug notification because you are a member of
Howdy again,
I'm trying to better understand the problem you had and what, if
anything, can be done to make sure others don't run into it. Developers
may or may not have time to resolve the issues, but I'd like to better
understand them. Unfortunately, I don't have the hardware you are
talking a
Howdy again,
Upstream is interested, but unfortunately they need info produced from a
tool like valgrind or something similar to really find out what the
cause is. If you can find the time to do that, the whole community that
would benefit would be grateful.
If you don't have the time or ability
Upstream might need some help on this... it is marked as info needed.
** Bug watch added: GNOME Bug Tracker #591959
https://bugzilla.gnome.org/show_bug.cgi?id=591959
** Also affects: brasero via
https://bugzilla.gnome.org/show_bug.cgi?id=591959
Importance: Unknown
Status: Unknown
** Changed in: mythbuntu
Status: New => Fix Committed
** Changed in: mythbuntu
Milestone: None => karmic-rc
--
lirc shouldn't be such a hard dependency
https://bugs.launchpad.net/bugs/133634
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Visibility changed to: Public
--
mythfilldatabase crashed with SIGSEGV in MythDB::ClearSettingsCache()
https://bugs.launchpad.net/bugs/446818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
*** This bug is a duplicate of bug 442707 ***
https://bugs.launchpad.net/bugs/442707
Closing since this is yet another incomplete back trace. Future PPA-
based builds will hopefully have better trace info!
** Changed in: mythtv (Ubuntu)
Status: New => Invalid
--
mythfilldatabase cra
*** This bug is a duplicate of bug 442707 ***
https://bugs.launchpad.net/bugs/442707
** This bug has been marked a duplicate of bug 442707
mythfilldatabase crashed with SIGSEGV in MythDB::ClearSettingsCache()
--
mythfilldatabase crashed with SIGSEGV in MythDB::ClearSettingsCache()
https:/
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 will hopefully
have better trace info. Please don't let the closing of this ticket
deter you from op
Howdy again! I've changed this report back to private at the moment
since it has a core file in it. Core files are memory dumps, so it is
possible that it contains sensitive data (passwords and other personal
information, for example). Launchpad has an automatic tool (retrace) to
extract the pro
*** This bug is a duplicate of bug 441904 ***
https://bugs.launchpad.net/bugs/441904
** Attachment added: "Casper.gz"
http://launchpadlibrarian.net/33766301/Casper.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33766302/Dependencies.txt
** Attachment added: "
Bug #452725 is a duplicate of this one. That one recreated this bug
with the latest Ubiquity (2.0) and Kernel by using the 15 Oct 2009 daily
.iso image burned to USB. Machine installed fine with beta disk a few
weeks ago.
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Ch
I happened upon this as well on my spare machine trying to install the
latest (15 Oct 2009) daily .iso
** Changed in: usplash (Ubuntu Karmic)
Status: New => Confirmed
--
--pulse-logo doesn't actually pulse the logo
https://bugs.launchpad.net/bugs/448988
You received this bug notification
Howdy, and thank you for helping to improve Ubuntu by filing this
report. I'm marking it confirmed since it appears to contain the
necessary information for maintainers to get started on it. I am also
marking it Low importance since, while annoying, it does not appear to
cause any problems other
Public bug reported:
Binary package hint: ubiquity
If any URLs are clicked during the install slide-show, Firefox is
eventually launched displaying the URL(s). When the slide-show is over,
ubiquity pops back to the top (so firefox is no longer visable at all)
and prompts the user for more info.
Yes, ubiquity was running full screen. I selected "install" from the CD, not
Live mode.
Also, if it is not obvious from the above media line, this was a daily CD .iso
from 2009-10-15, where I believe the ubiquity version is 2.0
--
If Firefox is launched during slide show, it stays hidden when
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 metadata grabber has been totally re-done for the upcoming 0.22 release,
so it is likely this is fixed
2. mythtv developers upstream have stopped focusing
I'm very sorry - the builds were broken when you updated, so you got an
old build. The builds should be fixed now, so if you could update and
recapture a stack trace, it would be most appreciated!
** Changed in: mythtv (Ubuntu)
Status: New => Confirmed
--
mythfilldatabase crashed with S
Original complaint was addressed here:
---
ubiquity (1.99.22) karmic; urgency=low
[ Michael Terry ]
* kde: Let back/forward/quit buttons activate when highlighted and the
user presses Enter. Part of bug #46600
--
cannot select `continue' with keyboard in kde
https://bugs.la
Howdy, and thank you for helping to improve Mythbuntu by filing this
report. Could you clarify a few things that should help the maintainers
narrow down possible causes?
1. What version of mythfrontend are you running on the Karmic system? (command
is "apt-cache policy mythtv-frontend")
2. What
Since you opened this ticket because of a sound problem, I assume that
we can leave it open for now.
But be advised that all systems that are talking to each other must be
at the same version level ... in this case, you have a mix of 0.22 and
0.21, so even if the sound issue can be resolved, you s
ullix: I certainly understand your desire to not upgrade a perfectly running
server.
When 0.22 is finally released, I do not know if it will be made available
Intrepid-backports, but in fact PPAs are available currently which allow you to
upgrade to trunk (pre-0.22) on Intrepid, or install 0.21
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
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 notif
*** 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 ad
*** 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 notificati
** 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()
https://
** 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 cras
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)
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 1
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 upgrad
** Changed in: mythtv-status (Ubuntu)
Importance: Undecided => Low
** Changed in: mythtv-status (Ubuntu)
Status: New => Confirmed
--
Fails to find Disk information on .22
https://bugs.launchpad.net/bugs/455542
You received this bug notification because you are a member of Ubuntu
Bugs,
Marking as resolved/released since Ubuntu 9.10 (Karmic) is shipping with
lcdproc 0.5.3, which has previously been reported as a solution to this
ticket.
** Changed in: lcdproc (Ubuntu)
Status: Confirmed => Fix Released
--
lcdproc needs patch for the imon lcd
https://bugs.launchpad.net/bug
Does not look like lcdproc 0.5.3 includes a driver for this.
** Changed in: lcdproc (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: lcdproc (Ubuntu)
Status: New => Confirmed
--
lcdproc: Futaba dm-140gink VFD device needs driver
https://bugs.launchpad.net/bugs/302919
You rece
I probably should have marked this triaged previously.
** Changed in: lcdproc (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: lcdproc (Ubuntu)
Status: Confirmed => Triaged
--
During suspend LCD should be turned off
https://bugs.launchpad.net/bugs/365474
You received this bug
** Changed in: mythbuntu
Status: Confirmed => Fix Committed
** Changed in: mythbuntu
Milestone: None => karmic-rc
--
Mixer values are not getting stored across reboot cycles
https://bugs.launchpad.net/bugs/454265
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: mythtv (Ubuntu)
Importance: Undecided => Medium
** Changed in: mythtv (Ubuntu)
Status: New => Confirmed
--
mythfrontend.real crashed with SIGSEGV in MythGenericTree::getRouteByString()
https://bugs.launchpad.net/bugs/456049
You received this bug notification because you
*** This bug is a duplicate of bug 455542 ***
https://bugs.launchpad.net/bugs/455542
** This bug has been marked a duplicate of bug 455542
Fails to find Disk information on .22
--
mythtv-status script incorrectly attempts to report on storage using protocol
version 32 and 39
https://bugs
*** This bug is a duplicate of bug 455542 ***
https://bugs.launchpad.net/bugs/455542
** This bug has been marked a duplicate of bug 455542
Fails to find Disk information on .22
--
cronjob for mythtv-status send me error mails
https://bugs.launchpad.net/bugs/425945
You received this bug no
The following message has gone unanswered on the upstream ticket for 14
months. Appears they are waiting on Ubuntu for a response:
<<
In my opinion the libmyth-perl package in Ubuntu is misnamed. According
to the Debian Perl Policy [0], it should be named libmythtv-perl.
I've had a bit of a lo
Setting to medium since it is a trade-off between being easy to work
around and fix, but annoying to new users:
Work-around: go into setup -> setup -> info center -> web settings and
change the value of the browser to anything, and change the text zoom to
anything. Select OK to exit the screen.
I must have missed hitting the "OK" button when I tried to do it the
previous time, or else I hit rather than , but regardless,
it was correctly pointed out to me that you don't have to change the
values to anything - just go into that screen, then tab over to "OK" and
then hit . This will popula
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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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
Closing since there has not been a response from to the maintainer. If
you do not believe this is still a problem with 9.04 or 9.10, please do
not hesitate to re-open this ticket.
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Won't Fix
--
dpatch patch-file permissions incorrect
ht
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 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 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 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
Not aware of this happening in a long, long time. If it is reproducable
on 9.04 or 9.10, please do not hesitate to re-open this ticket.
Thanks!
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Invalid
--
mythwelcome spawns infinite number of times on startup
https://bugs.launchpad.n
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 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 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
We are closing this ticket since there has not been a response to
previous questions regarding this issue. If you are able to reproduce
this with a 0.22 system, please do not hesitate to re-open this ticket.
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Invalid
--
Mythbuntu Progra
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 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 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 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 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
Closing since there has been no response to previous questions regarding
this issue. If you still believe this to be a problem, please feel free
to re-open if some answers can be provided. Thank you!
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Invalid
--
package mythtv-backend
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 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 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
Sorry that reinstalling is the only idea we are down to!
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Won't Fix
--
package mythtv-common 0.21.0+fixes19961-0ubuntu8 failed to install/upgrade:
subprocess post-installation script returned error exit status 30
https://bugs.launchpad.
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 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
Closing since this is not reproducible. If you can reproduce it on with
0.22, please do not hesitate to open a new ticket!
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Won't Fix
--
mythtv livetv freezes on program boundary
https://bugs.launchpad.net/bugs/235902
You received this
Howdy Pavel, have you worked out a solution to this issue?
Thanks!
--
frontend dont works with LCDproc
https://bugs.launchpad.net/bugs/427023
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
** Changed in: myththemes (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: myththemes (Ubuntu)
Status: New => Fix Released
** Changed in: myththemes (Ubuntu)
Milestone: None => ubuntu-9.10
** Changed in: mythbuntu
Status: Fix Committed => Fix Released
** Changed in
** Changed in: mythbuntu
Status: Fix Committed => Fix Released
--
transcode unencrypted DVD fails
https://bugs.launchpad.net/bugs/429089
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
** Changed in: mythbuntu
Status: Fix Committed => Fix Released
--
lirc shouldn't be such a hard dependency
https://bugs.launchpad.net/bugs/133634
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Thomas, when you say you can't get any other response out of the
computer - are you hitting certain sequences that you expect would do
something (i.e., hitting keyboard short-cuts that should produce some
action [maybe execute "sudo reboot"])? If that were to work, other
commands could be executed
Thomas, when you say you can't get any other response out of the
computer - are you hitting certain sequences that you expect would do
something (i.e., hitting keyboard short-cuts that should produce some
action [maybe execute "sudo reboot"])? If that were to work, other
commands could be executed
Closing this one since 0.21 development tree is closed and this same
error has been reproduced in with MythTv 0.22 (see bug #428959).
** Changed in: mythtv (Ubuntu)
Status: Confirmed => Won't Fix
--
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
https://bugs.la
Actually, I meant Bug #428238
** Changed in: mythbuntu
Importance: Undecided => Medium
** Changed in: mythbuntu
Status: Confirmed => Won't Fix
--
mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache()
https://bugs.launchpad.net/bugs/370146
You received this bug not
I am setting this to Critical because this appears to be a major
regression in (3.98.2+debian-0ubuntu1) that is about to be shipped in
9.10 as compared to (3.98-0.0) that was shipped in 9.04 and 8.10. If
someone feels that is not really criticial, please feel free to change
it (or let me know and
Pulseaudio is often at the root of sound related problems, especially
since MythTV doesn't support it well yet.
To those of you having the killed sound, what window manager are you using?
Asked another way, did you install the myth packages as add-on's to an install
that wasn't originally Mythb
> I have the default install of ubuntu karmic, i.e. the Gnome desktop.
> mythtv-frontend was added from repositories after default install was
> completed
Thank you for reporting back. Anyone else having this problem using
GNOME?
The following thread contains links to decent Pulseaudio discussio
Since Mythbuntu ships with xfce, this affects anyone that does a default
Mythbuntu install and tries to use Firefox. Not the most common
Mythbuntu use-case, but plenty of people do it. Confirmed on 9.10 Beta.
--
"Open containing folder" is only working if nautilus is present
https://bugs.launch
Since it is known that upstream doesn't do pulse audio well, moving to the
Mythbuntu bucket.
It would still be nice if someone could confirm that disabling pulse audio
fixes the problem.
** Also affects: mythbuntu
Importance: Undecided
Status: New
** Changed in: mythbuntu
Importanc
Since it is known that upstream doesn't do pulse audio well, moving to the
Mythbuntu bucket.
It would still be nice if someone could confirm that disabling pulse audio
fixes the problem.
** Changed in: mythtv (Ubuntu)
Status: Confirmed => Invalid
--
[ubuntu karmic] mythtv frontend inact
r22174 or later should hopefully be included in the nightly build, and
will be pushed to Karmic as soon as possible.
** Changed in: mythtv (Ubuntu)
Status: New => Fix Committed
** Changed in: mythplugins (Ubuntu)
Status: New => Fix Committed
** Changed in: mythbuntu
Status:
701 - 800 of 1068 matches
Mail list logo
