Forum
[SOLVED] XBian config do not start - Printable Version

+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Configuration (/forum-17.html)
+--- Thread: [SOLVED] XBian config do not start (/thread-2811.html)



XBian config do not start - D-Kalck - 5th Mar, 2015 10:09 AM

Software
XBian version: 1.0
XBMC/Kodi version: 14.2-BETA2
Overclock settings: default

Hardware
Device type and model (e.g. Raspberry Pi Model A/B 256/512 MB, CuBox-i i4Pro, ...): Raspberry Pi 2 Model B
Power supply rating:
SD card size and make/type: 8Gb
Network (Ethernet or wireless): Ethernet
Connected devices (TV, USB, network storage, ...):

Log files
Link to logfile(s): http://pastebin.com/CzwFdDja

Problem description:
I did a fresh install of Xbian and when I launch Xbian Config from within Kodi (around line 1194 in the log file), it loads until around 25% and close.

How to reproduce:
Launch Xbian Config

EDIT: fixed with latest build of xbian-package-config-shell


RE: XBian config do not start - f1vefour - 6th Mar, 2015 02:27 AM

Did you update yet?


RE: XBian config do not start - D-Kalck - 6th Mar, 2015 07:05 AM

Update which component ?
After many fails, I upgraded xbian with xbian-config from ssh, but it didn't fix the problem.


RE: XBian config do not start - f1vefour - 6th Mar, 2015 07:14 AM

sudo apt-get update
sudo apt-get upgrade


RE: XBian config do not start - madmikelol - 6th Mar, 2015 09:24 AM

(6th Mar, 2015 07:14 AM)f1vefour Wrote:  sudo apt-get update
sudo apt-get upgrade

Experiencing the same problem - fresh installation today, the XBian-config loads to 25% then just disappears, nothing happening. Am I correct to assume that within this XBian-config I'll be able to enable R/W on the ext. HDD that's plugged into the Pi? I can access it fine through my Macbook, but I can't add files to it through Finder. Sorry for posting here if it's the wrong forum!

Edit: Forgot to add that I did update and upgrade before trying, no changes.


RE: XBian config do not start - f1vefour - 6th Mar, 2015 11:07 AM

I filed a bug report for you on github: https://github.com/xbianonpi/xbian-package-config-xbmc/issues/29


RE: XBian config do not start - D-Kalck - 6th Mar, 2015 11:14 AM

(6th Mar, 2015 07:14 AM)f1vefour Wrote:  sudo apt-get update
sudo apt-get upgrade
I'm ugrading to the latest linux-image-bcm2836, I will see if it fix my problem.


RE: XBian config do not start - f1vefour - 6th Mar, 2015 01:22 PM

I wasn't referring to the kernel, there was an update to xbian-config I was hoping would fix the issue.


RE: XBian config do not start - D-Kalck - 6th Mar, 2015 05:04 PM

(6th Mar, 2015 01:22 PM)f1vefour Wrote:  I wasn't referring to the kernel, there was an update to xbian-config I was hoping would fix the issue.
I have the 20150220 version, I will try to manually update to 20150306.

EDIT : I updated to 20150306, but I have the same problem.


RE: XBian config do not start - madmikelol - 6th Mar, 2015 05:47 PM

(6th Mar, 2015 11:07 AM)f1vefour Wrote:  I filed a bug report for you on github: https://github.com/xbianonpi/xbian-package-config-xbmc/issues/29

In that bug report it says "solved 90%" does that mean that it'll get fixed in the next update or something?


RE: XBian config do not start - yishay - 15th Mar, 2015 11:40 PM

(6th Mar, 2015 05:47 PM)madmikelol Wrote:  
(6th Mar, 2015 11:07 AM)f1vefour Wrote:  I filed a bug report for you on github: https://github.com/xbianonpi/xbian-package-config-xbmc/issues/29

In that bug report it says "solved 90%" does that mean that it'll get fixed in the next update or something?

Update & upgrade didn't succeed.

(15th Mar, 2015 11:40 PM)yishay Wrote:  
(6th Mar, 2015 05:47 PM)madmikelol Wrote:  
(6th Mar, 2015 11:07 AM)f1vefour Wrote:  I filed a bug report for you on github: https://github.com/xbianonpi/xbian-package-config-xbmc/issues/29

In that bug report it says "solved 90%" does that mean that it'll get fixed in the next update or something?

Update & upgrade didn't succeed.



RE: XBian config do not start - f1vefour - 22nd Mar, 2015 09:29 AM

He said 90% sure it would be solved in the next update and the @D-Kalck confirmed it was fixed.

If you post on the github issue with @belese in the body of your post perhaps he will assist you in diagnosis of your particular problem.