[mythtv-users] blank screen after mythbuntu upgrade to 13.10 and myth upgrade to 27.0

[John]

On 24/12/13 14:40, Michael T. Dean wrote:
> On 12/24/2013 04:15 AM, John Reid wrote:
>> On 24/12/13 03:48, Michael T. Dean wrote:
>>> On 12/23/2013 05:45 AM, John Reid wrote:
>>>> I upgraded my mythbuntu box from 12.04 to 13.10 and also moved from
>>>> myth 0.25 to 0.27. Unfortunately now when I boot I get a blank screen
>>>> instead of mythwelcome.
>>>> The mythwelcome, mythfrontend and mythbackend processes are all
>>>> running in the background, I just can't see them. When I boot in
>>>> recovery mode and then resume mythwelcome and mythfrontend do appear
>>>> so I'm guessing there's something wrong with the video drivers or X.
>>>> I can't find any significant problems in the system logs (dmesg,
>>>> kern.log, syslog, Xorg.0.log). mythwelcome.log has some errors in it
>>>> such as:
>>>>
>>>> CoreContext mythuiwebbrowser.cpp:962 (Init) MythUIWebBrowser: failed
>>>> to find our parent screen
>>>> MythSocketThread(-1) mythsocket.cpp:661 (ConnectToHostReal)
>>>> MythSocket(305eb30:-1): Failed to connect to (127.0.0.1:6543)
>>>> Connection refused
>>>> CoreContext mythcorecontext.cpp:488 (ConnectCommandSocket) Connection
>>>> to master server timed out.#012#011#011#011Either the server is down
>>>> or the master server settings#012#011#011#011in mythtv-settings does
>>>> not contain the proper IP address
>>>>
>>> Well, you need to start there.  If the frontend can't connect to the
>>> backend, it won't work.
>>>
>>> Check your "this server" and "master server" "IP address" settings in
>>> mythtv-setup.
>>>
>> I'm not sure I do need to start there. I think this is just a timing
>> issue where the frontend comes up before the backend is ready. The
>> frontend does connect, just not straight away.
>
> That simply means that your configuration is wrong and tells the
> frontend that the backend is in the wrong place, then when the
> frontend can't find the backend, it falls back to a UPnP discovery
> mode and finds it where it actually is.  Still, fix that first because
> we /know/ that it's broken and should be fixed (whether mythfrontend
> is able to figure out that the config files are lying or not, you
> don't want it to be misconfigured).
Thanks I'll fix this but it doesn't sound like it will help with the
main problem.
>
>>   I think first I need to
>> get the display to work and I've just thought I never checked the
>> ~/.xsession-errors log so I'm going to look there now.
>
> I'd guess your video card/drivers are lying and saying that OpenGL
> works when it doesn't.  At that point, you need to set the:
>
> Paint engine
> This selects what MythTV uses to draw. Choosing 'Auto' is recommended,
> unless running on systems with broken OpenGL implementations (broken
> hardware or drivers or windowing systems) where only Qt works.
>
> setting to Qt.  Do that once with:
>
> mythfrontend -O ThemePainter=Qt
>
> And go immediately into Appearance settings and set it properly, after
> which you don't need any -O overrides, anymore.
The paint engine was set to auto. I tried Qt, that made no difference.
>
> (Or get a better card or drivers that actually works.  :)
This is the mystery. Everything worked just fine on mythbuntu 12.04 with
Mythtv 0.25 but on 13.10 with 0.27 I get a blank screen. AFAICT there
are no error messages in any of the logs (dmesg, kern.log, syslog,
Xorg.0.log) so I'm at a loss as to what went wrong and how to fix it. I
do have this warning

Top strut value for application window 0x1800004 confined to 0

in my .xsession-errors which doesn't sound good.

I don't have a graphics card, I'm using a H55 intel board with
integrated graphics.

At least mythfrontend works fine in 13.10 recovery mode so I will try to
find out what recovery mode does differently.

John.

>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users