Berkelium error rendering a region

Bug #1204048 reported by Maurizio Migliore on 2013-07-23
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BrowserNode
Undecided
Unassigned

Bug Description

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!

This is a bug in Berkelium/libbrowsernode, not in Xibo.

Changed in xibo:
status: New → Invalid
Changed in browsernode:
status: New → Confirmed
no longer affects: xibo
Eng Chong Meng (engcm) wrote :

Facing the same problem running python clinet on Ubuntu 12.10 with source compiled berkelium and libavg. In my case only the linked webpages, dataset, embed html are having problem; others like the media playback, RSS Ticker or slide show are OK.

Usually the problem does not happen when you first power up the system and lauch XiboClient. However when all regions in a layout expired, the XiboClient.py refreshes the whole display ( (even there is no layout change), and reloads the contents. This is where the problem start to happen. Restart XiboClient does not help.

If you restart the machine and launch XiboClient again, everything back to normal; but the whole cycle repeated.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers