Howdy, and thank you for going the extra mile to get a valid backtrace.
I went ahead and opened an upstream ticket, but you should be aware that
you, or your mirror, does not seem to be tracking the auto-build ppa
correctly - the mythtv revision for fixes is well about the 23000 number
now. It is
*** This bug is a duplicate of bug 358983 ***
https://bugs.launchpad.net/bugs/358983
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported, so
it is being marked as a duplicate. Please look at the other bug
Appears to be rare, but confirming since multiple people have seen this.
Haven't seen a report of this on 9.10 or 10.04... if someone could
confirm it still occurring there, it would be helpful.
Duplicate bug has a very similar stack trace.
** Changed in: cron (Ubuntu)
Status: New => Confi
** Visibility changed to: Public
--
cron crashed with SIGSEGV
https://bugs.launchpad.net/bugs/410203
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
*** This bug is a duplicate of bug 358983 ***
https://bugs.launchpad.net/bugs/358983
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported, so
it is being marked as a duplicate. Please look at the other bug
Howdy, and thank you for helping to improve Ubuntu by opening this
ticket. Unfortunately, through no fault of your own, the debugging
information which was automatically collected does not contain any
useful hints as to the cause of this crash.
Please do not hesitate to open tickets on this or oth
Meant to mark this as triaged the other day.
** Changed in: cron (Ubuntu)
Status: Confirmed => Triaged
--
cron crashed with SIGSEGV in _init()
https://bugs.launchpad.net/bugs/447080
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
Howdy, and thank you for helping to improve Ubuntu by opening this
ticket. I don't quickly see any other reports of a crash of this type -
could you please report back if it has reoccurred for you (and/or if you
know of a way to reproduce it)?
** Visibility changed to: Public
--
cron crashed wi
** Visibility changed to: Public
--
cron crashed with SIGSEGV in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/340417
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
** Visibility changed to: Public
** Tags added: mythtv-database
--
mythfrontend.real crashed with SIGSEGV in VideoListImp::buildDbList()
https://bugs.launchpad.net/bugs/456176
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Tags added: mythtv-database
** Tags removed: database
--
mythnews claims mythbrowser is not installed when it is
https://bugs.launchpad.net/bugs/446861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Visibility changed to: Public
--
jamu.py crashed with KeyError in _graphicsCleanup()
https://bugs.launchpad.net/bugs/507703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Yougo: if attaching the output of that to this ticket is easier than
pastebin, feel free to do so. Thanks!
** Changed in: mythplugins (Ubuntu)
Status: New => Incomplete
** Changed in: mythplugins (Ubuntu)
Importance: Undecided => Medium
--
jamu.py crashed with KeyError in _graphicsCl
I believe on Mythbuntu installs, it is located here:
/usr/share/mythtv/mythvideo/scripts/jamu.py
Note that there is a space between the .py and the -v or other
options. It looked from your previous paste that you were missing a
space.
--
jamu.py crashed with KeyError in _graphicsCleanup()
http
Ok, I finally dug up where this is, cause it has annoyed me slightly too.
You'll find that
/usr/share/applications/mythtv.desktop
points to:
/usr/share/mythtv/themes/MythCenter-wide/ui/mythtv_logo.png
I believe the problem with the logo is a combination of a lot of white
space surrounding the
Two things here: Mythbuntu database may need to be updated, and there
may be an upstream crashing bug because that field is empty (if that
hasn't been fixed already).
** Changed in: mythtv (Ubuntu)
Importance: Medium => Low
** Changed in: mythtv (Ubuntu)
Status: Incomplete => Confirmed
Changing the state back to assigned since cagney responded confirmed the
fix.
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
please backport pvrusb2 fix for FX2 16KB firmware
https://bugs.launchpad.net/bugs/44
You received this bug notification because you are a me
Until upstream has resolved this (or unless someone else develops a
patch and submits it upstream), I understand the work-arounds to be:
* Fall back to 0.21 (available in the 9.04 repos), do the channel scanning
there, then upgrade that database
-or-
* Enter channel info manually
-or-
* Use a ser
*** This bug is a duplicate of bug 478048 ***
https://bugs.launchpad.net/bugs/478048
frieso, this bug is a duplicate of
https://bugs.launchpad.net/bugs/478048 (which points to upstream bug
http://svn.mythtv.org/trac/ticket/6530)
** Bug watch added: mythtv.org bug tracker #6530
http://svn.m
*** This bug is a duplicate of bug 79 ***
https://bugs.launchpad.net/bugs/79
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported and
appears to be a duplicate, so it is being marked as such. Please
Raising importance, between this bug and Bug #448656 and no telling how
many others, this is affecting a number of users.
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Importance: Low => Medium
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug notification
*** This bug is a duplicate of bug 79 ***
https://bugs.launchpad.net/bugs/79
Howdy, and thank you for taking the time to report this bug and helping
to make Ubuntu better. This particular bug has already been reported and
appears to be a duplicate, so it is being marked as such. Please
** Visibility changed to: Public
--
grub crashed (floating point exception) when used at prompt from Ubunto Live
CD, in command find, repeatedly
https://bugs.launchpad.net/bugs/311700
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Screen capture of invisible icon
** Attachment added: "Invisible Icon"
http://launchpadlibrarian.net/38670149/invisible-icon.png
--
MythTV Frontend icon is Very hard to see.
https://bugs.launchpad.net/bugs/458686
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Howdy, and thank you for helping to improve Ubuntu by opening this
ticket. The errors from the log files are:
Setting up lirc (0.8.6-0ubuntu2) ...
* Loading LIRC modules
^Cdpkg: error processing lirc (--configure):
subprocess installed post-installation script killed by signal (Interrupt)
Setti
** Visibility changed to: Public
** Bug watch added: mythtv.org bug tracker #8106
http://svn.mythtv.org/trac/ticket/8106
** Also affects: mythtv via
http://svn.mythtv.org/trac/ticket/8106
Importance: Unknown
Status: Unknown
** Changed in: mythtv (Ubuntu)
Status: New => Tri
Howdy, and thank you for helping to improve Lirc by opening this ticket.
The above patch appears to only support >= 2.6.33 kernels. A patch
(coded somewhat differently, and includes support for older and newer
kernels) appears to already be in the upstream cvs tree:
http://lirc.cvs.sourceforge.ne
Thank you for helping to improve Lirc by opening this ticket. I am
marking this ticket as confirmed because it appears to have enough
information to help the developers understand the problem. It is
possible I am wrong and another more experienced triager or developer
may adjust the status of th
** Changed in: lirc (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: lirc (Ubuntu)
Milestone: None => ubuntu-10.04-beta-1
--
Check the TRANSMITTER logic for errors w/ lirc-mceusb
https://bugs.launchpad.net/bugs/517743
You received this bug notification because you are a member of
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Unfortunately, this backtrace attached is not useful to the
developers. Could both of you please open new tickets after following
the "basic backtrace" directions outlined here:
http://www.mythtv.org/wiki/Debugging#De
frankO: Mythbuntu simply repackages the themes that are available
from the upstream MythTV source, and this issue was never fixed there.
The next best that we can offer would be to follow the directions on
David Valentines comment #10 and fix it on your install. Upstream is
shorthanded, so they s
Howdy Andrew Cagney (and/or anyone else with an interest in this): just
wanting to call your attention to the request by a kernel developer
worked on this ticket. Is there any way that you could test this - at a
minimum, perhaps by temporarily installing his 10.04 kernel and then
reverting back?
*** This bug is a duplicate of bug 360378 ***
https://bugs.launchpad.net/bugs/360378
** This bug has been marked a duplicate of bug 360378
Gave up waiting for root device after upgrade then busybox console
--
karmic rc: root device sometimes not found
https://bugs.launchpad.net/bugs/46091
*** This bug is a duplicate of bug 360378 ***
https://bugs.launchpad.net/bugs/360378
** This bug has been marked a duplicate of bug 360378
Gave up waiting for root device after upgrade then busybox console
--
"Gave up waiting for root device" with the 2.6.27-11-generic kernel
https://bugs
Other reports: http://ubuntuforums.org/showthread.php?t=1319976 Some
work-arounds appear to be discussed there.
I also found this posted out in the wild:
<>
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
Gave up waiting for root device after upgrade then busybox console
ht
http://zfranciscus.wordpress.com/2009/11/01/ubuntu-karmic-upgrade-series-1-upgrading-jaunty-to-karmic-koala/
Also makes mention that loading by UUID and found that loading with actual
device name worked better:
<>
--
Gave up waiting for root device after upgrade then busybox console
https://bug
Bug #343919 may also be a cause of this
--
Gave up waiting for root device after upgrade then busybox console
https://bugs.launchpad.net/bugs/360378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
*** This bug is a duplicate of bug 500396 ***
https://bugs.launchpad.net/bugs/500396
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. Since there is another ticket which addresses this issue, I'm
marking this one as a duplicate of that. Thanks again!
** This bug
*** This bug is a duplicate of bug 500396 ***
https://bugs.launchpad.net/bugs/500396
Howdy, and thank you for helping to make Mythbuntu better. What version
of mythtv-status is installed on your system? I suspect that this
problem is likely addressed by
https://bugs.launchpad.net/ubuntu/+sou
*** This bug is a duplicate of bug 500396 ***
https://bugs.launchpad.net/bugs/500396
I was actually referring to that bug to point to the steps to work-
around the problem you are having. I believe the bug was actually
resolved per https://bugs.launchpad.net/ubuntu/+source/mythtv-
status/+bug
Howdy, and thank you for helping to improve Mythbuntu. mythtv-status fell
behind on the 9.10 release.
This is resolved for 10.04 with the re-sync to debian, described in
https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/455542
It is also available for 9.10 via the Mythbuntu -testin
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Triaged
--
[No emblems] can't set any kind of background for the side panel
https://bugs.launchpad.net/bugs/525231
You received this bug notification because you are a me
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket.
The error message in the dpkgterminal log states:
Setting up mythtv-database (0.22.0+fixes22594-0ubuntu1) ...
ERROR 1005 (HY000) at line 2839: Can't create table
'mythconverg.weatherdatalayout' (errno: 121)
dpkg: error
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. I am marking this ticket as confirmed because it appears to
have enough information to help the developers understand the problem.
It is possible I am wrong and another more experienced triager or
developer may adjust th
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
https://bug
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 pleas
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 notific
** 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
https:
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 o
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 0.21.
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 er
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 t
** Visibility changed to: Public
--
twinkle tried to handle an incoming phone call
https://bugs.launchpad.net/bugs/450361
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
** Visibility changed to: Public
--
twinkle assert failure: twinkle: events.cpp:435: void
t_event_ui::exec(t_userintf*): Assertion `false' failed.
https://bugs.launchpad.net/bugs/476563
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- [karmic alpha 4] grub re-writes boot sector on wrong drive on mythbuntu
install
+ [karmic] grub re-writes boot sector on wrong drive on fresh install
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Critical
--
[karmic] grub re-writes boot sector on wrong drive o
Since at.c explains that DISPLAY is not exported on purpose, and there
is a work-around in comment #5, marking this ticket as a feature
request.
** Changed in: at (Ubuntu)
Importance: Medium => Wishlist
--
Unexported $DISPLAY prevents `at' from executing GUI apps
https://bugs.launchpad.net/bu
** Changed in: at (Ubuntu)
Importance: Undecided => Medium
** Changed in: at (Ubuntu)
Status: Confirmed => Triaged
--
at command ignores savings time when given UTC time
https://bugs.launchpad.net/bugs/433545
You received this bug notification because you are a member of Ubuntu
Bugs, w
Hello grazanel, if you believe this information in this ticket to be
incomplete, could you please explain why?
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Confirmed
--
[karmic] grub re-writes boot sector on wrong drive on fresh install
https://bugs.launchpad.net/bugs/414996
You re
Howdy, we'd like to know if Karmic (Ubuntu 9.10) has resolved this issue for
you, but we have received a response. Could you report back any testing
results?
Thanks!
--
No simple way to enable 4+ channel sound
https://bugs.launchpad.net/bugs/234412
You received this bug notification because
** Changed in: f-spot (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: f-spot (Ubuntu)
Status: New => Confirmed
--
Allow editing photos from F-Spot Viewer
https://bugs.launchpad.net/bugs/484888
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Changed in: gwenview (Ubuntu)
Importance: Undecided => Medium
** Changed in: gwenview (Ubuntu)
Status: New => Confirmed
--
gwenview rotate causes jpg quality loss
https://bugs.launchpad.net/bugs/315437
You received this bug notification because you are a member of Ubuntu
Bugs, which
Howdy, and thanks for helping to improve Mythbuntu by not only opening
this ticket, but also proposing a solution. I am marking this ticket as
triaged since you have proposed a solution. The developer/themer will
evaluation that and make a decision what, if anything to do about this
issue.
** Al
** Attachment added: "URL-box-overflow.png"
http://launchpadlibrarian.net/36319399/URL-box-overflow.png
--
Url to long for status bar in mythbrowser
https://bugs.launchpad.net/bugs/477557
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "bookmark_URL_overflow.png"
http://launchpadlibrarian.net/36319434/bookmark_URL_overflow.png
--
Url to long for status bar in mythbrowser
https://bugs.launchpad.net/bugs/477557
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Box should probably extend at least to the ellipses. There is plenty
of screen width even on a non-widescreen monitor... could URL box be
larger (assuming MythUI allows for it)?
** Attachment added: "URL-box-overflow2.png"
http://launchpadlibrarian.net/36319517/URL-box-overflow2.png
--
Url
Howdy there! The dpkg.log seems to show:
Setting up mythexport (2.1.3-0ubuntu1) ...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)
dpkg: error processing mythexport (--configure):
Here are a few things to check:
* Is mysql running?
* Ha
Howdy, and thank you for helping to improve Ubuntu and Mythbuntu by opening
this ticket. Could you please investigate the work-arounds presented in
https://bugs.launchpad.net/mythbuntu/+bug/460579 and report back if that
changes your results at all?
** Changed in: mythtv (Ubuntu)
Importanc
9.10 ships with:
mythtv (0.22.0+fixes22594-0ubuntu1) karmic; urgency=low
** Changed in: mythtv (Ubuntu)
Status: Fix Committed => Fix Released
--
Bogus version in mythbackend.log
https://bugs.launchpad.net/bugs/455525
You received this bug notification because you are a member of Ubuntu
B
** Changed in: mythtv (Ubuntu)
Importance: Undecided => Medium
** Changed in: mythtv (Ubuntu)
Status: New => Triaged
** Changed in: mythtv (Ubuntu)
Milestone: None => lucid-alpha-1
--
mythconverg_restore.pl and mythconverg_backup.pl should be in mythtv-backend
https://bugs.launchp
The summary from the linked email thread is that there are two ways to
solve this for 10.04:
1. package and distribute an older version (8KB rather than 16 KB) of the
firmware
2. backport a .33 kernel patch to the Ubuntu .32 kernel
** Summary changed:
- please backport pvrusb2 fix for FX2 16KB
I'm sure users would appreciate back porting this as far as possible
(10.04 at least, but 9.10 certainly wouldn't be objected to :-)
** Changed in: mythbuntu
Importance: Undecided => Medium
** Changed in: mythbuntu
Status: New => Triaged
--
please backport pvrusb2 fix for FX2 16KB fir
I searched pretty extensively and can't find the meaning of 'kernel-
series-unknown'.
Sorry if this wasn't clear... this was a problem introduce in the
2.26.31 kernel and the fix is landing on the upstream 2.26.33 kernel.
Request is for to be fixed in 2.6.32, and if not too disruptive, 2.26.31
as
Howdy, and thank you for helping to improve Mythbuntu by opening this
ticket. This ticket is being marked as incomplete because the
developers/maintainers will likely need more information to be able to
properly debug this issue:
1. please describe your video capture device configuration and atta
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 forw
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 f
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 fo
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 fo
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 fo
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 fo
*** 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 received
*** 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 => Co
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)
https://bugs.
** 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 ma
** 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.
--
ubun
** 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 Ubun
*** 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 MythContext::ClearSettingsCache
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 MythDB::ClearSettingsCa
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()
https://
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()
https://bugs.launchpad.net/bugs/19
*** 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. 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. Can
you please try to see if this bug is reproducible on 0.22? If it is, we
can try to forw
*** 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 list
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 Myth
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 *** /us
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 forw
201 - 300 of 1068 matches
Mail list logo
