XBMC wierdness

English Applications
#1

I installed XBMC out of the pacman repository after upgrading to 13.1. It seemed to run fine, but most settings don’t seem to save.

I believe that XBMC is trying to create a directory in /home/user called U: with a bunch of sub-directories and files underneath it. I DO get a U: directory. And it has a userdata subdir in it. And that in turn has an addon_data directory. So far so good. Unfortunately, I also get “U:\userdata\Database\Epg7.db”, “U:\userdata\Database\MyMusic32.db”, and a few other files in my $HOME. Note this isn’t a directory path-- see the image of the partial directory listing below.

Can anyone confirm this strangeness?

http://i.imgur.com/83702Os.jpg

#2

By default XBMC should save it’s configuration to ~/.xbmc/

I would suggest reinstalling XBMC. I installed 13.1 (clean install) and downloaded XBMC from Pacman without any problems.

#3

Still no change. I’ll try again when I upgrade another computer in the house to 13.1

#4

That’s strange, the distribution version shouldn’t matter. Try taking a look at /usr/bin/xbmc and check if the log files are being stored in ~/.xbmc/temp/xbmc.log. I’m not entirely sure where XBMC sets the default config/userdata folder.

I am experiencing some weirdness after a few updates that are not related to your particular issue. I’m getting segmentation fault when I try to run xbmc.

/usr/bin/xbmc: line 110: 19092 Segmentation fault      python /usr/share/xbmc/FEH.py $SAVED_ARGS

Commenting out the line calling FEH.py works. In particular, importing qt is causing the problem in the python file. I tried this in the python console,

>>> import qtdlopen("/usr/lib64/python2.7/site-packages/qt.so", 2);
dlopen("/usr/lib64/python2.7/site-packages/sip.so", 2);
import sip # dynamically loaded from /usr/lib64/python2.7/site-packages/sip.so
Segmentation fault

Just curious if anyone else is experiencing this issue with XBMC.

#5

I don’t see that issue. It starts and runs fine… but I can’t seem to save settings, and I get strange files created in whichever directory I start xbmc from .

~/.xbmc is created correctly. Here’s bits of my log in case anybody recognizes something.

Things seem to start ok. I don’t see any reason to be alarmed by the mixer not starting.

 14:26:15 T:140546105772224  NOTICE: -----------------------------------------------------------------------14:26:15 T:140546105772224  NOTICE: Starting XBMC (12.2 Git:32b1a5e), Platform: Linux (openSUSE 13.1 (Bottle) (x86_64), 3.11.6-4-desktop x86_64). Built on Dec  6 2013
14:26:15 T:140546105772224  NOTICE: special://xbmc/ is mapped to: /usr/share/xbmc
14:26:15 T:140546105772224  NOTICE: special://xbmcbin/ is mapped to: /usr/lib64/xbmc
14:26:15 T:140546105772224  NOTICE: special://masterprofile/ is mapped to: /home/apc/.xbmc/userdata
14:26:15 T:140546105772224  NOTICE: special://home/ is mapped to: /home/apc/.xbmc
14:26:15 T:140546105772224  NOTICE: special://temp/ is mapped to: /home/apc/.xbmc/temp
14:26:15 T:140546105772224  NOTICE: The executable running is: /usr/lib64/xbmc/xbmc.bin
14:26:15 T:140546105772224  NOTICE: Local hostname: linux-81l0
14:26:15 T:140546105772224  NOTICE: Log File is located: /home/apc/.xbmc/temp/xbmc.log
14:26:15 T:140546105772224  NOTICE: -----------------------------------------------------------------------
14:26:15 T:140546105772224   ERROR: CAESinkOSS::EnumerateDevicesEx - Failed to open mixer: /dev/mixer

Then a bit lower in the log, after the ALSA devices are discovered

 14:26:15 T:140546105772224  NOTICE: load settings...14:26:15 T:140546105772224  NOTICE: special://profile/ is mapped to: U:\userdata\
14:26:15 T:140546105772224  NOTICE: loading special://masterprofile/guisettings.xml
14:26:15 T:140546105772224  NOTICE: Getting hardware information now...
14:26:15 T:140546105772224  NOTICE: Loading player core factory settings from special://xbmc/system/playercorefactory.xml.
14:26:15 T:140546105772224  NOTICE: Loaded playercorefactory configuration
14:26:15 T:140546105772224  NOTICE: Loading player core factory settings from special://masterprofile/playercorefactory.xml.
14:26:15 T:140546105772224  NOTICE: special://masterprofile/playercorefactory.xml does not exist. Skipping.
14:26:15 T:140546105772224  NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml)
14:26:15 T:140546105772224  NOTICE: No settings file to load (special://masterprofile/advancedsettings.xml)
14:26:15 T:140546105772224  NOTICE: Default DVD Player: dvdplayer
14:26:15 T:140546105772224  NOTICE: Default Video Player: dvdplayer
14:26:15 T:140546105772224  NOTICE: Default Audio Player: paplayer
14:26:15 T:140546105772224  NOTICE: Disabled debug logging due to GUI setting. Level 0.
14:26:15 T:140546105772224  NOTICE: Log level changed to 0
14:26:15 T:140546105772224  NOTICE: Loading media sources from U:\userdata\sources.xml
14:26:15 T:140546105772224 WARNING: CreateDirectory, cant create dir <U:/userdata/addon_data\>. trying lower case.
14:26:15 T:140546105772224   ERROR: Create - Error creating U:/userdata/addon_data
14:26:15 T:140546105772224   ERROR: Create - Error creating special://profile/addon_data

You can see it referencing the U: drive as though this were windows and failing at creating files and directories.

#6

You’re not running XBMC in portable mode correct?

special://profile/ is being pointed to U:\ so if a profile exists at that location, remove it. Then, by default, special://profile/ should point to special://masterprofile/. If you have tried this already and it’s still saving subsequent profile changes to U:\ then try the below method.

Overwrite the special://profile/ through path substitution. You can read more about it Path substitution - XBMC and advancedsettings.xml - XBMC. Maybe this might work.

#7

THANK YOU!

I went through the xml configuration files in the .xmbc folder and saw where the U and P drives were being set. When I deleted those lines and re-ran XBMC the files were re-built correctly.

I’m still wondering how they got that way to begin with though. I’m reasonably sure I don’t have any wacky environment variables set. Pretty strange all in all.

#8

Glad you got it working. It is weird how it got set to the U: path. According to XBMC it looks like legacy paths.