Forum

That's strange. I just tested and it worked fine for me.

That "echo" breaks it as we _first_ save the exit code (0=quit, 66=reboot, ...) and only _after_ that we call "sudo stop xbmc" and that echo gets executed, overwriting it with a normal "quit" exit code (0).

Is a reboot required before "trying" it?

Something "simple" has been "added" as "shutdown -r/h now" works perfectly. I've seen this issue before but only for a few upgrades.

(9th Jul, 2014 02:09 AM)IriDium Wrote: [ -> ]Is a reboot required before "trying" it?

Something "simple" has been "added" as "shutdown -r/h now" works perfectly. I've seen this issue before but only for a few upgrades.

Yes, that "echo" line was added only recently (a week ago). I've pushed a fix on GitHub - should be in next update, as it's working fine for me.

Here's the diff: https://github.com/xbianonpi/xbian-package-xbmc-scripts/commit/fe6b665fc0fdc71f9969458850ec6f2f7248a153

To test:
* stop XBMC: sudo stop xbmc;
* apply the patch above to /etc/init/xbmc.conf (manual copy/paste is fine);
* this shouldn't be needed, but let's make sure Upstart knows about your modification: sudo initctl reload-configuration;
* start XBMC again: sudo start xbmc;
* try to reboot from the GUI.

Thanks menakite,
it works fine for me too!

(9th Jul, 2014 04:52 AM)PicatriX Wrote: [ -> ]Thanks menakite,
it works fine for me too!

Yep - that did the trick. Works as expected.

A couple of questions:
1:
I used the RC2.0 image on the homepage, this one still contains XBMC 13 beta1. Can the image please be replaced by the one posted by mk01?

(4th Jul, 2014 11:06 AM)mk01 Wrote: [ -> ]@yami
http://ivka57.dyndns-ip.com/images/xbian-image-rpi-20140704.img.xz

url does not work anymore..

2:
Also, after installing the image from the homepage, when updating or when I install a package like Transmission, I always see the message "less than 30% space available for metadata, will only keep 1 snapshot.."
how come? I never had this before. I checked free space, see attached screenshot.

3:
When I reboot XBian, I always see in XBMC "Xbian 1.0 beta 2 mounted", quickly followed by "XBian 1.0 beta 2 unmounted". Why does this happen? Again, I installed the RC image on the homepage.

4:
PLEASE always add a datestamp in the name of an image.. or add version/datestamp on the download page. Referring to "RC image on the homepage" is a bit vague ofcourse.

I'm trying a dist-upgrade but I'm getting warnings about mandatory package deletions.
My current version should be 1RC2 Gotham
Am I upt to date?
Have I to wait before doing dist-upgrade?
xbian-apt-show-versions:
http://pastebin.com/4T7bUBQK

Hi,

seems I have problem with photo slideshow on XBian 1.0 RC 2 - after some it crashes XBMC.
I'm using Synology NAS to share photos. I've tried sharing photos with different protocols (NSF, SMB, WebDav), turning off zoom in and out effect - the problem remains.
On Xbian 1.0 RC 1 it works ok.
Has anyone same issue ?

regards

@zilexa

1) There is a lot of work in progress, both by Debian and thus Xbian to incorporate the new changes.
URL works for me - can you retry.
2) I believe the 30% less space is associated with xbmc-backup which is showing as 25% free.
3) This is an automount message required for the daily/weekly snapshot function. (discussed elsewhere)
4) Iagree it is a bit vague - especially as a date stamp is put on the Cubox-i images

Hi guys, big linux noob here.

I have updated to Gotham and now I cannot connect to my rutorrent anymore "502 Bad Gateway", rtorrent is runing in background so are nginx and php.

There was also a php lib update I did together with Gotham and a bunch of other updates, I am kind of lost at this point, I tried to reinstall rtorrent using the script I have used previously but nothing changes...

Can you help me out ? I am happy to give you more info but I wouldn't what is relevant at this point...

(11th Jul, 2014 06:11 PM)Fabio72 Wrote: [ -> ]I'm trying a dist-upgrade but I'm getting warnings about mandatory package deletions.
My current version should be 1RC2 Gotham
Am I upt to date?
Have I to wait before doing dist-upgrade?
xbian-apt-show-versions:
http://pastebin.com/4T7bUBQK

Code:

root@xbian:~#  cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi
deb http://xbian.brantje.com stable main

Code:

root@xbian:~# apt-get dist-upgrade
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Eseguito
I seguenti pacchetti saranno RIMOSSI:
  upstart xbian-package-config-xbmc xbian-package-lirc xbian-package-upstart-xbmc-bridge xbian-package-xbmc
  xbian-package-xbmc-gotham-nightly xbian-package-xbmc-scripts xbian-update
I seguenti pacchetti NUOVI saranno installati:
  sysvinit
ATTENZIONE: i seguenti pacchetti essenziali stanno per essere rimossi.
Questo non dovrebbe essere fatto a meno che non si sappia esattamente cosa si sta facendo.
  xbian-update xbian-package-lirc (a causa di xbian-update) upstart (a causa di xbian-update) xbian-package-upstart-xbmc-bridge
  (a causa di xbian-update) xbian-package-xbmc (a causa di xbian-update) xbian-package-xbmc-scripts (a causa di xbian-update)
0 aggiornati, 1 installati, 8 da rimuovere e 0 non aggiornati.
È necessario scaricare 129 kB di archivi.
Dopo quest'operazione, verranno liberati 102 MB di spazio su disco.
Si sta per compiere un'azione potenzialmente pericolosa.
Per continuare scrivere la frase "Sì, esegui come da richiesta."
?]

I'm experiencing the same thing too. This is what an apt-get upgrade shows:

And if you want to see the whole message in english, here it is:

@Fabio72 and @ slovdahl
Have you tried the upgrade via ssh xbian-config? It is a little bit more "intelligent" in what is required.

I will try asap

(11th Jul, 2014 06:11 PM)Fabio72 Wrote: [ -> ]I'm trying a dist-upgrade but I'm getting warnings about mandatory package deletions.
My current version should be 1RC2 Gotham
Am I upt to date?
Have I to wait before doing dist-upgrade?

@Fabio

without trying to force my truth there (but it is the truth in that case ), what is the concern/problem which makes you trying dist-upgrade?

purpose of dist-upgrade is for live distribution upgrades (for instance process of going from wheezy to jessie without reimaging). and because of that dist-upgrade is not honouring standard rules as defined for SAFE apt-get operations (for instance "upgrade").

dist-upgrade is allowed to remove even by USER installed packages and if it considers others as priority - but with one specific purpose => allow distro generation change what can mean completely different deb package structure.

with this ability it is often misused to avoid typing two commands instead of one. for security reasons APT will not UPGRADE package if its dependencies changed. imagine you running auto updates and you installed program putting "hello world" on your screen day before. second day someone change that package and put a trojan horse as dependency. the third day you are a victim of crime (because APT auto installed the trojan horse as was requested with the new version of "hello world" package. would be bad, wasn't it?

now back to XBian. as we were developing from A5 -> RC2 user and our expectations changed over time. also, upgrading from Frodo to Gotham means other support programs - this time because XBMC developers decided that way. for APT that means that someone is trying to hijack your installation. that's why it will list those packages as "on hold"

there are two ways how to install such packages. one is misuse of dist-upgrade. but dist-upgrade will HONOR original Debian packages over any other installed. In Xbian's case it means removing UPSTART thus making you system to remove all other XBian packages because we rely on it. Don't go this way. (just for info this particular conflict is open as bug at Debian for over 1.5y and by many many users). Also we tried to put this into EACH bigger upgrade howto (B1, B2 and so on). There I just try to say that don't worry it is not your install wrong, it is by design (unfortunately).

second option to install the packages (if you prefer command line) is just simply telling APT to install them. That means

where pkgX is name of package which APT lists as on hold during operations.

And because we always wish for seamless and easy user experience we designed the upgrade module of xbian-config (within XBMC or SSH) to directly list those packages for you to check it for upgrade and confirmation with OK. Nothing less or more is asked.

At the end of long story: I'm not encouraging you to forget about dist-upgrade. I'm trying to be sure you understand the risks involved there. This is also reason why some of the XBian packages are flagged as MANDATORY. If they would not, your Installation would be useless few minutes after you hit Enter on dist-upgrade.

For more info check "man apt-get" (only if interested, otherwise is quite boring ).
If you follow this best-practices and still will hit strange things, don't hesitate to open ISSUE report at github to get it solved ASAP.

mk

---

(14th Jul, 2014 09:58 AM)ilgello Wrote: [ -> ]Hi guys, big linux noob here.

I have updated to Gotham and now I cannot connect to my rutorrent anymore "502 Bad Gateway", rtorrent is runing in background so are nginx and php.

There was also a php lib update I did together with Gotham and a bunch of other updates, I am kind of lost at this point, I tried to reinstall rtorrent using the script I have used previously but nothing changes...

Can you help me out ? I am happy to give you more info but I wouldn't what is relevant at this point...

I'm just shooting blind but I have strange feeling it could be with new XBMC allocating different TCP port for ES component and by accident that is the one used before by some of the downloader programs .

Try to check list of ISSUES reported at github.

(19th Jul, 2014 08:05 PM)mk01 Wrote: [ -> ]

(11th Jul, 2014 06:11 PM)Fabio72 Wrote: [ -> ]I'm trying a dist-upgrade but I'm getting warnings about mandatory package deletions.
My current version should be 1RC2 Gotham
Am I upt to date?
Have I to wait before doing dist-upgrade?

@Fabio

without trying to force my truth there (but it is the truth in that case ), what is the concern/problem which makes you trying dist-upgrade?

purpose of dist-upgrade is for live distribution upgrades (for instance process of going from wheezy to jessie without reimaging). and because of that dist-upgrade is not honouring standard rules as defined for SAFE apt-get operations (for instance "upgrade").

dist-upgrade is allowed to remove even by USER installed packages and if it considers others as priority - but with one specific purpose => allow distro generation change what can mean completely different deb package structure.

with this ability it is often misused to avoid typing two commands instead of one. for security reasons APT will not UPGRADE package if its dependencies changed. imagine you running auto updates and you installed program putting "hello world" on your screen day before. second day someone change that package and put a trojan horse as dependency. the third day you are a victim of crime (because APT auto installed the trojan horse as was requested with the new version of "hello world" package. would be bad, wasn't it?

now back to XBian. as we were developing from A5 -> RC2 user and our expectations changed over time. also, upgrading from Frodo to Gotham means other support programs - this time because XBMC developers decided that way. for APT that means that someone is trying to hijack your installation. that's why it will list those packages as "on hold"

there are two ways how to install such packages. one is misuse of dist-upgrade. but dist-upgrade will HONOR original Debian packages over any other installed. In Xbian's case it means removing UPSTART thus making you system to remove all other XBian packages because we rely on it. Don't go this way. (just for info this particular conflict is open as bug at Debian for over 1.5y and by many many users). Also we tried to put this into EACH bigger upgrade howto (B1, B2 and so on). There I just try to say that don't worry it is not your install wrong, it is by design (unfortunately).

second option to install the packages (if you prefer command line) is just simply telling APT to install them. That means

Code:

apt-get install pkg1 pkg2 pkg3 pkg4

where pkgX is name of package which APT lists as on hold during operations.

And because we always wish for seamless and easy user experience we designed the upgrade module of xbian-config (within XBMC or SSH) to directly list those packages for you to check it for upgrade and confirmation with OK. Nothing less or more is asked.

At the end of long story: I'm not encouraging you to forget about dist-upgrade. I'm trying to be sure you understand the risks involved there. This is also reason why some of the XBian packages are flagged as MANDATORY. If they would not, your Installation would be useless few minutes after you hit Enter on dist-upgrade.

For more info check "man apt-get" (only if interested, otherwise is quite boring ).
If you follow this best-practices and still will hit strange things, don't hesitate to open ISSUE report at github to get it solved ASAP.

mk

---

(14th Jul, 2014 09:58 AM)ilgello Wrote: [ -> ]Hi guys, big linux noob here.

I have updated to Gotham and now I cannot connect to my rutorrent anymore "502 Bad Gateway", rtorrent is runing in background so are nginx and php.

There was also a php lib update I did together with Gotham and a bunch of other updates, I am kind of lost at this point, I tried to reinstall rtorrent using the script I have used previously but nothing changes...

Can you help me out ? I am happy to give you more info but I wouldn't what is relevant at this point...

I'm just shooting blind but I have strange feeling it could be with new XBMC allocating different TCP port for ES component and by accident that is the one used before by some of the downloader programs .

Try to check list of ISSUES reported at github.

Thanks for your reply, I think it's not an XBMC related issue, I have reverted the updates using BTFRS and I am now upgrading every package one by one so I can isolate the issue.