New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid incorrect disabling PVR addons (Alternate) #4761
Avoid incorrect disabling PVR addons (Alternate) #4761
Conversation
AddonDB is not a reliable source for testing existence of an addon, use AddonManager instead and tag clients as "known" in PVRDB.
Heh...WTF is github up to now... |
Ah, wrong branch. Sorry for the noise. ie. Fixed now. |
did you test this with a clean installation (removed ~/.xbmc before running)? |
@opdenkamp Nope, top two should address. I'll do some squashing before push. |
jenkins build this please |
@opdenkamp Did you give this one the OK on IRC? I can't remember... :/ |
if you tested those cases i mentioned, and tried installing a new add-on via a zip which gets disabled, then +1 |
Avoid incorrect disabling PVR addons (Alternate)
Has also add your correction to my ADSP Pull request #4402 which use the same way to load the add-ons, thank a lot t-nelson. |
@t-nelson this breaks "reset pvr database". reverting last commit fixes it. |
"Breaks" how? I'm pretty sure I've used the reset thing since this went in and the database seemed pretty empty. |
"breaks" like pvr plugin disabled, pvr database wiped, pvr plugin NOT (re)enabled. |
OK. I'll look into it on Monday. |
@opdenkamp I guess we need to clear m_clientMap from CPVRClients. Is there anything else we should/shouldn't consider wiping from memory on db reset? |
the add-on shouldn't be automatically re-enabled when you clear the database. if it did that before, then that was a bug. it should only clear the pvr tables, not do anything with the add-on db |
k then, let me explain it again, in depth.. my use case: add some (iptv) channels to vdr backend. before this pr, 2 simple steps to reset and enjoy live tv:
after this pr, 4 not-so-simple steps, including an annoying "hey I am not runing" message, or "what where did TV go?":
next:
or:
this is a change in behaviour. the one before this pr is what I am familiar with, and almost everyone I know that use xbmc + pvr.
so what do you mean here, excuse my ignorance but I dont understand:
if 1. then see above the change-in-behaviour note, because that's what most users (at least those I know personaly, including me) are familiar with |
this reverts upstream commit b6bec7a (part of xbmc/pull/4761): > From b6bec7a Mon Sep 17 00:00:00 2001 > From: Trent Nelson <trent.nelson@pivosgroup.com> > Date: Wed, 21 May 2014 17:16:54 +0800 > Subject: [PATCH] [PVR] Make sure client addons are disabled first time we see > them. xbmc/pull/4761 fixed a bug where newly added pvr clients were automaticaly enabled and could not be disabled first time an user tries to disable em. unfortunately, it introduces a regression, now "reset pvr database" is useless and leaves the user with no pvr clients enabled at all. however, the "oh-i-can-not-disable-pvr-addons" bug I can not reproduce anymore, but this commit may re-introduce it for some users.
Alternate to #4757.