Comment 22 for bug 341898
Revision history for this message
| Mario Limonciello (superm1) wrote Re: Mythtv frontend does not display any fonts | #22 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
OK, so some basic sleuthing led me a few data points that will be useful in helping to debug this.
I took a use case of running mythtv-setup on a fglrx/jaunty install no problem. I then spun up a6 in virtualbox( using vesa ), and tried to run that same functional mythtv-setup X forwarded on the virtualbox X instance. Problem occurs. So here's what you can take from that:
1) This *does NOT* happen on fglrx or nvidia closed source modules.
2) This *does* happen on on vesa
We've at least got a use case for reproducing. Live disks do it reliably when using vesa.
I went a little further and started spewing printf's all over mythtv code to figure out when the first BadMatch shows up. Around line ~612 of mythmainwindow.cpp, there is a show() call. As soon as this call is executed the first BadMatch comes up. It's not clear if the other X errors are caused by show() calls as well. show() is inherited from the parent class of MythMainWindow, QWidget. That means that this bug actually lies somewhere in QT and it's interface to X. This wouldn't be too much of a surprise considering it hasn't changed at all since Intrepid, and there quite possibly has been X changes in Jaunty.