Posts: 3
Joined: Dec 2012
Reputation:
0
2013-12-04, 19:14
(This post was last modified: 2013-12-04, 19:18 by XzavieR.)
Well, seems it's not just me then. Good to know. I'm getting the same errors mentioned here, lots of popups (one for each of my plugins) on every XBMC start. Also the PVR plugins aren't working anymore and all of them autodisable (this started at the same time as the aforementioned popups started appearing, in the same build, so I'm guessing there's a connection). When I try to activate one of them, it just dies immediately. Since the PVR plugins even in the unstable ppa are considerably older than the xbmc build, I guess the error is really the same as with most other plugins right now (reference to older xbmc.python)?
Posts: 62
Joined: Feb 2010
Reputation:
0
yup, me too. Just posted on this issue before finding this thread. I'm on a 12/2 build, going to try updating.
Posts: 77
Joined: Nov 2012
Reputation:
3
2013-12-12, 23:37
(This post was last modified: 2013-12-12, 23:39 by BartOtten.)
I noticed so I did not say a word about 'that' repository. It's a general rule that Frodo repositories should not be used in Gotham. I think it would be possible to prevent such errors to happen using a dependency on oe of the submodules of XBMC (gui, python etc). Which one do you think would fit best for that purpose?