Forum

just to explain:

without fresh firmware Gotham Beta3 is unable to play ...

I just wanted to known if there was some issues installing last updates, since I had troubles with python. I didn't want to be the first tester

there were none since python (Raspbian)

for stable XBian just Gotham and firmware. you can run the update.

(25th Mar, 2014 05:07 PM)Fabio72 Wrote: [ -> ]I just wanted to known if there was some issues installing last updates, since I had troubles with python. I didn't want to be the first tester

I'm running it without any problems.

I just updated but I'm waiting to reboot cause I'm not at home.
Digging around I found that the initramfs line in config.text is commented out. Is it normal?

@Fabio72



you are quite brave ! )

I have two little kids, twins. At home I don't have time to do nothing. Really nothing. I just can make some little test from work.
If xbian stop working and my kids cannot watch tv it's a tragedy as I cannot have time to fix it. And my satellite receiver is broken and I have no time to fix it, so we can only see cartoon in steaming.
But I'm an IT worker and I love to test, experiment, update...
These are difficult days...

xbian-package-config-xbmc 1.1.7-1 gave me a bunch of trouble.
First reboot didn't recognize /dev/sda1
Second reboot booted to prompt (XBMC didn't start)
"sudo start xbmc" gave me a working XBMC.

Update was fine.
Still not working xbian config GUI version: close at 25%
I'll check logfile asap
EDIT
Xbian package config did not get updated first run
Tomorrow I will check it again

(26th Mar, 2014 05:24 AM)Fabio72 Wrote: [ -> ]EDIT
Xbian package config did not get updated first run
Tomorrow I will check it again

ok, i prefer this
if it crash, even with new version, please activate debug in xbmc and post log.
~

Quote:xbian-package-config-xbmc 1.1.7-1 gave me a bunch of trouble.
First reboot didn't recognize /dev/sda1
Second reboot booted to prompt (XBMC didn't start)

i don't see how it could be related to xbian-config.
/dev/sda1 is done earlier than xbmc start.
second point, maybe, but probably not, as all modif i've done are run only when you start xbian-config in xbmc.

(26th Mar, 2014 06:22 PM)belese Wrote: [ -> ]

Quote:xbian-package-config-xbmc 1.1.7-1 gave me a bunch of trouble.
First reboot didn't recognize /dev/sda1
Second reboot booted to prompt (XBMC didn't start)

i don't see how it could be related to xbian-config.
/dev/sda1 is done earlier than xbmc start.
second point, maybe, but probably not, as all modif i've done are run only when you start xbian-config in xbmc.

Yeah, just later figured out that I MAY have been rebooting before the complete install was done
That's what happens when you SSH in from multiple devices.... my bad

(21st Mar, 2014 03:57 AM)raudpats Wrote: [ -> ]

(19th Mar, 2014 04:03 AM)crs Wrote: [ -> ]Error = trying to overwrite '/usr/lib/python2.7/lib-dynload/_hashlib.so', which is also in package python2.7 2.7.3-6

Did anybody succeeded to solve this problem? I'm hitting this as well...

Same error here.
Seems to be a problem with python dependencies (_hashlib.so and _ssl.so modules). You can find more information here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702005

A forced install fixed it for me:
apt-get -o Dpkg::Options::="--force-all" upgrade

I finally updated xbian package config and rebooted
Not working yet. I also tried to delete cache.db and run updates update db
still stop at 25%
http://pastebin.com/te9HCKww
EDIT
I re-run xbian-config packages updatedb and xbian-config updates updatedb and now finally started

Just did all the stable updates to the latest RC1 and it worked. Very handy that for the common error's the wiki is update with [Q] and [A].

(27th Mar, 2014 08:28 PM)HenkPl Wrote: [ -> ]

(21st Mar, 2014 03:57 AM)raudpats Wrote: [ -> ]

(19th Mar, 2014 04:03 AM)crs Wrote: [ -> ]Error = trying to overwrite '/usr/lib/python2.7/lib-dynload/_hashlib.so', which is also in package python2.7 2.7.3-6

Did anybody succeeded to solve this problem? I'm hitting this as well...

Same error here.
Seems to be a problem with python dependencies (_hashlib.so and _ssl.so modules). You can find more information here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702005

A forced install fixed it for me:
apt-get -o Dpkg::Options::="--force-all" upgrade

Have the same problem here... what options do i have to use in DPKG ?

this i what i've done and it worked for me :
hope this helps anyone

Added spoiler