search

code-google-com / mythbox

Automatically exported from code.google.com/p/mythbox
GNU General Public License v2.0
0 stars 1 forks source link

Error onInit #153

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. install xbmc from rpmfusion repo
2. add mythbox addon
3. start it

What is the expected output? What do you see instead?
dialogue box saying there is an error and nothing is populated

What version of the product are you using? On what operating system?
Fedora 14 x86_64
Xbmc 10.0
MythBox 1.0.2

Please provide any additional information below.
Mythbackend is separate from mysql db.  plugin seems to get backend details 
from mysql db fine but there is an error onInit - see attached.

Original issue reported on code.google.com by ukpb...@gmail.com on 27 Jan 2011 at 8:40

Attachments:

GoogleCodeExporter commented 9 years ago 
This issue occurs on both the default Confluence skin and Night.

Original comment by ukpb...@gmail.com on 27 Jan 2011 at 8:42

GoogleCodeExporter commented 9 years ago 
Turn on debug (Mythbox > Settings > Advanced) and re-post your log.

Original comment by semir.pa...@gmail.com on 27 Jan 2011 at 7:56

GoogleCodeExporter commented 9 years ago 
I selected debug in xbmc and mythbox.  the output is taken from selecting 
mythbox in the Video-Addons menu to after clicking the 'OK' on the error onInit 
dialogue box, selecting 'Watch Recordings' ok'ing the error and escaping back 
to the main mythbox screen.

I had previously installed 1.0.{0,1} but to ensure cleanliness I uninstalled 
the plugin from xbmc and even deleted all traces from ~/.xbmc/.  After 
reinstalling the same issues occurred.

Original comment by ukpb...@gmail.com on 27 Jan 2011 at 9:34

Attachments:

GoogleCodeExporter commented 9 years ago 
Looks related to your use of the external python 2.7 instead of python2.4 that 
is bundled with xbmc. Not sure I can do much about that because the first 
stacktrace seems to indicate a problem getting the name of the thread.

/usr/lib64/python2.7/threading.py:806: RuntimeWarning: tp_compare didn't return 
-1 or -2 for exception return _active[_get_ident()]

Found one other reference to this error - bug fixed in Python 2.5 

http://bugs.python.org/issue1733757

Can you try editing your mythbox_log.ini and remove the reference to the thread 
name in the log formatter and try again?

Old: format=%(levelname)s | %(name)s | %(module)s.py | %(threadName)s | Line 
%(lineno)d | %(message)s

New: format=%(message)s

Original comment by semir.pa...@gmail.com on 28 Jan 2011 at 4:27

GoogleCodeExporter commented 9 years ago 
I used the same setup as last time.

The rules for packaging in the RPMFusion repository forbid using different 
versions of software that are included in the distribution (or something like 
that).  Bundling sounds like a bad thing to me too if it's already in the OS.

For more information:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=xbmc

Original comment by ukpb...@gmail.com on 28 Jan 2011 at 11:02

Attachments:

GoogleCodeExporter commented 9 years ago 
There are two lines that need replacing in mythbox_log.ini.  The log output 
indicates that only one of then was updated.

Original comment by semir.pa...@gmail.com on 1 Feb 2011 at 3:09

GoogleCodeExporter commented 9 years ago

Original comment by ukpb...@gmail.com on 1 Feb 2011 at 7:00

Attachments:

GoogleCodeExporter commented 9 years ago 
Well, don't know what to tell you. For some reason, python 2.7 on your distro 
doesn't quite agree with some threading internals used in the script. Are any 
other scripts that use threads working?

Original comment by semir.pa...@gmail.com on 11 Feb 2011 at 5:58

GoogleCodeExporter commented 9 years ago 
I may be an RHCE but nfi.  everything else in XBMC seems to work properly and 
as intended.  I tested on the weekend a completely different i686 system, while 
still fedora 14, and the results are the same.

side note:
xbmc really should be using the latest stable release of python..

Original comment by ukpb...@gmail.com on 14 Feb 2011 at 6:25

GoogleCodeExporter commented 9 years ago 
I have same setup as above:  Fedora 14 x86_64, xbmc 10.1, mythtv 0.24.1.  xbmc 
and mythtv were loaded from the RPMFusion repositories.

Turning on debugging for both xbmc and mythbox shows that xbmc is bundled with 
Python2.7:

20:22:41 T:139903400159456 M:3281690624    INFO: initializing python engine.
20:22:41 T:139903400159456 M:3281690624   DEBUG: Loading: 
/usr/lib64/xbmc/system/python/python27-x86_64-linux.so

Original comment by dwgoldf...@gmail.com on 19 Jun 2011 at 8:41

Attachments:

GoogleCodeExporter commented 9 years ago 
Same issue here, Fedora 14 32-bit, xbmc-10.1-1.fc14.i686 from the rpmfusion 
repo. Anything I can do? Will upgrading Fedora change anything?

Original comment by a...@adamhaeder.com on 6 Dec 2011 at 3:36

GoogleCodeExporter commented 9 years ago 
I see from the pre-release notes for XBMC Eden that they are migrating from the 
internally bundled python to external.  hopefully this should fix the 
incompatibility issue we are seeing here.

Original comment by ukpb...@gmail.com on 6 Dec 2011 at 10:51

GoogleCodeExporter commented 9 years ago 
I have same issue being oninit error with ipaddress on appletv 2 with xmbc eden 
beta and latest version of mythbox connected to my media server with suse 11.3 
with mythtv .24 installed i can use frontend of mythtv from any pc fine but not 
from appletv 2
 So whats with ipaddress error?

Original comment by vwbug200...@gmail.com on 20 Jan 2012 at 7:15