Xibo Pyclient doesn't always show all regions at launch and goes black over time

Asked by Mark S

Hi all and thanks for reading. I have a Dell Precision T3400 running Ubuntu 10.04.4 LTS (32-bit). The server v1.4.2 is running on this machine as well as the client, which is also v1.4.2. I have enabled the proprietary nVidia graphics drivers. I have one flash region, two RSS tickers, one webpage region, and a PNG slideshow overtop of a background image. Upon launch of the client, I get the following errors, which I've read here shouldn't be of any concern:

Switching to new logger
[25806:25814:31035005044:ERROR:process_singleton_linux.cc(264)] Failed to create /opt/xibo/pyclient/client/python/.berkelium/SingletonLock: File exists
[25806:25898:31047324251:ERROR:zygote_main_linux.cc(547)] Your system is broken: dlsym doesn't work! This has been reported to be caused by Nvidia's libGL. You should expect time related functions to misbehave. http://code.google.com/p/chromium/issues/detail?id=16800

But then, I always get the following, usually several right away and then more identical error messages appear over time:

(berkelium:25899): Gdk-WARNING **: XID collision, trouble ahead

Sometimes when launching, not all of my regions show up. Doesn't seem to be any rhyme or reason as to which ones don't show up. Sometimes it's the flash region, sometimes the two RSS feed tickers, sometimes the webpage. If I quit the client and come back in a couple times eventually they come up. When they don't, I get the following console error, one set of these for each region that doesn't show:

Error rendering Md9dc2e65b033498f468217f54de292a7-9-13. Re-rendering
Error rendering Md9dc2e65b033498f468217f54de292a7-9-13. Re-rendering
Error rendering Md9dc2e65b033498f468217f54de292a7-9-13. Skipping

When I launch it and everything looks fine, after a half hour or so, the client screen goes all black and the messages in the console go straight from the XID collision warnings to messages like this which appear in groups every ten seconds:

[13-04-29 17:05:55.791] WARNING: getElementByID("L4-4") failed.

If I press "i" in the console, there's five green check marks and the stats one is grey. It says Now Playing 4 Schedule 4, just like it does when it's working correctly. The hard drive is 89% free, both CPU cores stay below 20%, RAM is only 25% used and the swap is untouched.

Any ideas?

Thank you much!

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Alex Harrington
Solved:
Last query:
Last reply:
Revision history for this message
Alex Harrington (alexharrington) said :
#1

All the errors you list are normal. The regions not showing up are a bug in
Berkelium which manifests itself on some hardware more than others. We've
done our best to work around it but for now there is no further development
within the Berkelium project on the current library.

Once that's fixed the problem will go away.

Alex

Revision history for this message
Mark S (vo1one) said :
#2

Hi Alex, thanks for the response. Luckily I do have some other hardware at my disposal so perhaps I'll try putting this all on another computer and see how it flies. In the meantime, I don't mind starting up the client a few times until it decides to run correctly, but where it blacks out after a half hour and stays that way will be quite problematic. Do you know of a way I can prevent it from doing that or would it be best to just have it automatically reload the client every half hour or am I really just best off putting this on another computer?

Revision history for this message
Best Alex Harrington (alexharrington) said :
#3

It only goes black because of this bug.

It's waiting for regions that haven't rendered to expire.

Keep in mind it's still officially "alpha" because of these problems

Alex

Revision history for this message
Mark S (vo1one) said :
#4

Thanks Alex Harrington, that solved my question.

Revision history for this message
Maurizio Migliore (maurizio-migliore) said :
#5

A few questions:
how to avoid this problem?
There were no reports on the resolution of the bug from the team berkelium?
There are special cases that trigger the error?
What are the hardware that trigger the error and what are the most stable?

Thanks in advance!
Maurizio