[lcapriotti]

It seems that newer debs are needed.
Pls be patient, the fix will be incorporated in next packages.

[sensei73]

It seems that newer debs are needed.
Pls be patient, the fix will be incorporated in next packages.

Thank you so much for following us, and helping us!

[tr45h]

First post here (hi all) :-)

It seems that I have the same problem when doing dpkg-reconfigure xbmc-live:

: 120: #: unexpected operator

Looking forward to new packages...

[biggles]

Me too! For me it seems like X isn't starting with the new xbmc-live. As sson as I log in to the HTPC and manually startx, XBMC starts automatically...

When I try to reconfigure I get the same :: 120: #: unexpected operator

[grassmunk]

It seems that newer debs are needed.
Pls be patient, the fix will be incorporated in next packages.

Thats great news. But while we're waiting for the new package what can the rest of us do as a band-aid?

[lcapriotti]

not really, but I hope to have an updated package early next week.

[gsgleason]

remove xbmc-live package and only have xbmc. It takes very little to set up a user to auto login and start xbmc. afaik, that only reason for the xbmc-live package is to do this and have the user be able to shutdown, etc. After upgrading ubuntu to 9.10 and installing the new xbmc package, I ran into issues as well. My solution was to remove the xbmc user that had been created, and set up my normal super user to log in automatically and start xbmc.

[BOFH]

Using the latest xbmc-live.conf from svn I was able to eliminate the "[: 120: #: unexpected operator" issue and get the xbmc-live upstart service to start again:

Code:

wget http://trac.xbmc.org/export/25111/trunk/tools/XBMCLive/xbmc-live.conf

Unfortunately, xbmc still won't fire up the GUI due to an assert (from .xsession-errors):

Code:

Xsession: X session started for xbmc at Sun Nov 29 10:03:37 UTC 2009
xbmc.bin: ../xbmc/MathUtils.h:33: int MathUtils::round_int(double): Assertion `x > static_cast<double>((-2147483647 - 1) / 2) - 1.0' failed.
Aborted

Thus, it really seems the PPA upgrade from Live alpha2 to beta1 introduces more problems than it solves...

For me, getting the alpha2 xbmc.bin out of the squashfs archive on the Live CD works for now (unfortunately the alpha2 DEBs were removed from PPA), hopefully the new beta1 DEBs will fix the assertion, that seems to have been encountered before:
http://forum.xbmc.org/showpost.php?p=439...tcount=640

[lcapriotti]

would you pls update again and report if the new package fixes the issue?

[jbernardo]

The script works now - but xbmc itself doesn't. It just shows a blank screen (or window). I've tried both on my POV ION, and on a X86_64 and the results are the same.

[tredman]

The script works now - but xbmc itself doesn't. It just shows a blank screen (or window). I've tried both on my POV ION, and on a X86_64 and the results are the same.

I have the same problem , only I can see a mouse cuersor on the blank window.

Doing sudo dpkg-reconfigure xbmc-live through ssh gives the output:

* Configuring system and starting XBMC... * Mounting local disks...
[ OK ]
Can't open display

=======================| DirectFB 1.0.1 |=======================
© 2001-2007 The DirectFB Organization (directfb.org)
© 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2008-11-12 15:27)
* Configuring system and starting XBMC... (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
--> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system' core!
--> Initialization error!
ERROR: Unable to create application. Exiting
CRITSEC[0x8b03964]: Trying to enter destroyed section.
CRITSEC[0x8b03964]: Trying to leave destroyed section.
* Mounting local disks...
[ OK ]
Can't open display
xbmc@xbmc:~$
=======================| DirectFB 1.0.1 |=======================
© 2001-2007 The DirectFB Organization (directfb.org)
© 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2008-11-12 15:27)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
--> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system' core!
--> Initialization error!
ERROR: Unable to create application. Exiting
CRITSEC[0x8b03964]: Trying to enter destroyed section.
CRITSEC[0x8b03964]: Trying to leave destroyed section.

which would seem to indicate the problem is with the display?

[jbernardo]

Strange, I don't get those fbdev errors when I do "sudo dpkg-reconfigure xbmc-live".

Code:

~$ sudo dpkg-reconfigure xbmc-live
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xbmc-live stop

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) utility, e.g. stop xbmc-live
xbmc-live stop/waiting
update-rc.d: warning: /etc/init.d/xbmc-live missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xbmc-live start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start xbmc-live
xbmc-live start/running, process 24891

[tredman]

Strange, I don't get those fbdev errors when I do "sudo dpkg-reconfigure xbmc-live".

Code:

~$ sudo dpkg-reconfigure xbmc-live
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xbmc-live stop

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) utility, e.g. stop xbmc-live
xbmc-live stop/waiting
update-rc.d: warning: /etc/init.d/xbmc-live missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xbmc-live start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start xbmc-live
xbmc-live start/running, process 24891

confused then

[tredman]

further to above, dug out my xbmc.log and it stops when loading at the points below:

12:49:16 T:3026466704 M:1999949824 INFO: msg: PICTURE::LoadImage: Unable to open image: special://xbmc/media/icon.png Error: (2)

12:49:16 T:3026466704 M:1999949824 ERROR: Texture manager unable to load file: special://xbmc/media/icon.png

don't mean much to me, anyone else?

[jankowskid]

further to above, dug out my xbmc.log and it stops when loading at the points below:

12:49:16 T:3026466704 M:1999949824 INFO: msg: PICTURE::LoadImage: Unable to open image: special://xbmc/media/icon.png Error: (2)

12:49:16 T:3026466704 M:1999949824 ERROR: Texture manager unable to load file: special://xbmc/media/icon.png

don't mean much to me, anyone else?

I am running Ubuntu 9.10 and I had to copy everything from /usr/share/xbmc/ to /usr/lib/xbmc/. It seems they changed the locations of the special://xbmc folder. I looked at the very top of my xbmc.log to find where it was looking

Code:

17:17:40 T:3062896528 M:447655936  NOTICE: Starting XBMC, Platform: GNU/Linux.  Built on Dec  1 2009 (SVN:25154)
17:17:40 T:3062896528 M:447655936  NOTICE: special://xbmc/ is mapped to: /usr/lib/xbmc