I installed xbmc and things seemed to be working fine, until I exited the program and started it again later. Every time I start it, it crashes with a segmentation fault. Just screwing around, I deleted the ~/.xbmc folder and it started up fine, but every subsequent attempt resulted in a crash. To narrow it down further, I found that renaming ~/.xbmc/userdata/profiles.xml to something else allowed me to restart and have it work. Again, every subsequent attempt after that was a segmentation fault.
The console output and crashlog are located here:
http://paste.ubuntu.com/1477759/
The contents of profiles.xml is here:
http://paste.ubuntu.com/1477775/
Athlon II X4 630
4GB RAM
Ubuntu 12.04
XMBC version 12.0-RC2 (2:12.0~git20121220.0939-rc2-0precise)
Is this a known issue?
I haven't created any other profiles. My profiles.xml has only one profile, for Master user, but I'll try the xbmc-nightly just to see if that works.
I still get a segmentation fault using xbmc-nightly.
Here is the crashlog:
http://paste.ubuntu.com/1479419/
The thread that has the segmentation fault looks like it died in the AudioEngine or libasound code.
My installed version of libasound2 is 1.0.25-1ubuntu10.1
try this plz:
search and delete any asound configs: /etc/asound.conf ~/.asoundrc
The only things that exist are:
/var/lib/alsa/asound.state
/usr/share/xbmc/system/asound.conf
There is nothing in /etc and there is no .asoundrc file in my home folder. I tried getting rid of /usr/share/xbmc/system/asound.conf and it still resulted in a segmentation fault. The only difference in the crashlog is that there is no stack trace this time. The log file contents are the same as before.
out of ideas then. could you enable debugging via advancedsettings.xml? maybe we get a hint whats going on then.
The only difference when I set loglevel to 3 in advancedsettings.xml is that <feff> appears at the beginning of the log file. The previous crashlogs say that a core file was generated, but I don't see one at the specified path. That would certainly help.
Maybe I'll try changing the settings in profiles.xml, one at a time, to see if a certain one will make it stop doing a segmentation fault.
Changing any values in profiles.xml didn't do anything. I also tried disabling the MythTV add-on. That didn't help either.
I did create a test profile, just to see what that was about. Then it got interesting. When I restart xbmc via the command line, it no longer crashes. All I did was create a test profile, with nothing special about it. Starting xbmc via the shortcut (GNOME shell Applications) still does cause it to crash. I haven't found out where that shortcut is actually located, but the surprising part is that xbmc did not crash (via command line) after I created a test profile.