Blank screen on OpenElec and Raspberry Pi

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Install OpenElec for Raspberry Pi - 
OpenELEC-RPi.arm-devel-20120807030154-r11766
2.Install MythBox add-on from addons menu (have also tried latest from 
https://github.com/mitchcapper/mythbox)
3. Select Video, Add-ons, MythBox

What is the expected output? What do you see instead?
I expect to see something. I get a blank screen. The keyboard is ineffective. 
The only resort I've found is killall -9 xbmc.bin

What version of the product are you using? On what operating system?
As above

Please provide any additional information below.
I've added some logging into bootstrap.py to find out how far it's getting and 
it's getting as far as HomeWindow.__init__, which means it probably thinks the 
HomeWindow is displayed OK, I just can't see it. Interestingly, if I break the 
logging config file, I see a dialog box telling me what's wrong, with a mythbox 
logo behind it. I presume this is the splash screen. If I OK the dialog, the 
splash screen remains, but the keyboard does nothing and I have to kill xbmc 
again.

It is entirely possible the UI is working but that I just can't see it, however 
having never seen the UI and not knowing the key combinations, I can't tell. 
Certainly pressing 'Esc' lots of times does nothing.

FYI, I don't have a settings.xml file. I thought that it would prompt me to 
create one.

Sorry, the log files aren't much help (the MythBox: n lines I added are just it 
ticking off each function call in bootstrapper.run).

Original issue reported on code.google.com by j...@thejpster.org.uk on 25 Aug 2012 at 9:35

Attachments:

• xbmc.log
• mythbox.log

[GoogleCodeExporter]

I was having the same issue with the latest version of RASPBMC, but I found an 
interesting "workaround." I turned on debugging mode so I could collect 
accurate logs and everything worked fine. Shutting off debugging mode once 
again caused the black screen to return. With debugging on I was able to 
configure and play media from my myth backend.

Hopefully this helps narrow the problem down. There's something different about 
the debug method that changes the behavior.

Original comment by krnew...@gmail.com on 2 Sep 2012 at 9:34

[GoogleCodeExporter]

I noticed no ~/.xbmc/userdata/addon_data/script.mythbox/settings.xml was 
created. Could this be the issue? An empty one at least gives you an error (no 
data found etc).

Is there any example of the settings.xml?

Original comment by matthy...@gmail.com on 4 Sep 2012 at 5:47

[GoogleCodeExporter]

I concur that enabling debug allows MythBox to work. The cpu/memory overlay is 
annoying, but it's better than nothing.

Original comment by j...@thejpster.org.uk on 4 Sep 2012 at 8:35

[GoogleCodeExporter]

How exactly can I enable the mentioned debug workaround? Which file+setting to 
change? I tried some editing in mythbox_log.ini but no results. I'm trying this 
on a raspberry-pi running openelec's xbmc + mythbox. Thanks for the info!

Original comment by atka...@gmail.com on 10 Sep 2012 at 8:54

[GoogleCodeExporter]

I think it has something to do with the splash screen.

Original comment by Robertso...@gmail.com on 12 Sep 2012 at 4:03

[GoogleCodeExporter]

Same here. Latest RASPBMC on Raspberry Pi. I am looking forward for a fix or a 
less annoying workaround…

Original comment by jajcus on 18 Sep 2012 at 2:47

[GoogleCodeExporter]

Commenting out the "splash.show" line in default.py fixes the issue without 
needing debug mode.

Original comment by calvin.m...@gmail.com on 3 Oct 2012 at 12:28

[GoogleCodeExporter]

Thanks. Commenting out the splash screen got me one step further. But now 
whenever I select a recording to watch, I get amessagebox: Error: onClick 
<xbmcgui.listitem object at 0x41651a0>

Anybody have the same issue (or better, a solution)?

Original comment by edoo...@gmail.com on 5 Oct 2012 at 1:59

[GoogleCodeExporter]

I am seeing this as well with xbian 1.0 alpha 4.

Confirming that commenting out the splash screen in default.py in 
/home/xbian/.xbmc/addons/script.mythbox/default.py allows mythbox to start 
successfully.

Unfortunately I am running a 0.25 backend backport on Debian with proto 72 so 
mythbox won't connect anyway.

Original comment by sfdonne...@gmail.com on 27 Jan 2013 at 1:39