2014-01-20, 03:26
I had an original installation of XBMCbuntu with an older Ubuntu install (I think it was 11.01?) which I'd upgraded to Frodo 12.2. After a few attempts to upgrade the OS, I got tired of running into issues so I backed up my user directory (including .xbmc) and the installed media, downloaded a fresh XBMCbuntu install .iso, (specifically xbmcbuntu-12.2.Intel-AMD.iso) burned it, and installed as a clean installation (wiping what was in place). The system will boot, and I can get into the XBMCbuntu GUI, but XBMC itself crashes almost immediately on start. I say "almost" because it will briefly display the background, then go back to the XBMCbuntu splash screen and eventually leave me at the lightdm login prompt. This box is dedicated to running XBMC, so I figured the simplest way to get this working was just to use the live CD to install, which is why I've done it this way.
Reproducing this is (unfortunately) very straightforward: From lightdm if I select XBMC, the Frodo splash screen displays briefly, followed by a brief display of what I assume is supposed to be the background for Confluence, with a return to lightdm. If I start the "XBMCbuntu" desktop, and run xbmc from an xterm, I get the following:
I have not (yet) restored anything from the backup.
Here's the info that I think I'm supposed to provide, please let me know what else I might have missed, and thanks in advance:
xbmc.log - I see a number of errors in there but I am not sure what to do about those
uname -a
Linux media 3.5.0-45-generic #68-Ubuntu SMP Mon Dec 2 22:02:00 UTC 2013 i686 i686 i686 GNU/Linux
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.10 - XBMCbuntu
Release: 12.10
Codename: quantal
dmesg output
lspci output
gdb output (not sure if I did this right):
Reproducing this is (unfortunately) very straightforward: From lightdm if I select XBMC, the Frodo splash screen displays briefly, followed by a brief display of what I assume is supposed to be the background for Confluence, with a return to lightdm. If I start the "XBMCbuntu" desktop, and run xbmc from an xterm, I get the following:
Code:
WARNING: gnome-keyring:: couldn't connect to: /home/david/.cache/keyring-yqitPI/pkcs11: No such file or directory
/usr/lib/xbmc/xbmc-xrandr: Failed to get size of gamma for output default
/usr/lib/xbmc/xbmc-xrandr: Failed to get size of gamma for output default
LLVM ERROR: Program used external function '' which could not be resolved!
pure virtual method called
terminate called without an active exception
Aborted (core dumped)
I have not (yet) restored anything from the backup.
Here's the info that I think I'm supposed to provide, please let me know what else I might have missed, and thanks in advance:
xbmc.log - I see a number of errors in there but I am not sure what to do about those
uname -a
Linux media 3.5.0-45-generic #68-Ubuntu SMP Mon Dec 2 22:02:00 UTC 2013 i686 i686 i686 GNU/Linux
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.10 - XBMCbuntu
Release: 12.10
Codename: quantal
dmesg output
lspci output
gdb output (not sure if I did this right):
Code:
gdb /usr/lib/xbmc/xbmc.bin core
GNU gdb (GDB) 7.5-ubuntu
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/lib/xbmc/xbmc.bin...(no debugging symbols found)...done.
warning: core file may not match specified executable file.
[New LWP 2819]
Core was generated by `python /usr/share/xbmc/FEH.py'.
Program terminated with signal 11, Segmentation fault.
#0 0xb68d932e in ?? ()
(gdb) thread apply all bt
Thread 1 (LWP 2819):
#0 0xb68d932e in ?? ()
#1 0x09aff800 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)