98.8b: Conflicts no longer resolvable.

[_gl]

I have just upgraded to 98.8b (from my previous 97.13). Conflicts were working OK before the upgrade, now when I try to Resolve one, no conflicting shows are listed anymore, so I can't cancel them from there. This is true of every conflict, none are resolveable.

I've tried emptying and reloading the EPG but it hasn't helped...

[martint123]

I don't think it's an introduced bug in this version - I have plenty of conflicts and they all allow 'ignore' or 'cancel' from the resolve button.

p.s. I'd really like to see a pair of descriptions at this point and the ability to cancel either of the two conflicting shows on this screen (hint).

[_gl]

I don't think it's an introduced bug in this version - I have plenty of conflicts and they all allow 'ignore' or 'cancel' from the resolve button.

The update definitely broke it, it worked fine before and now all the conflicts are broken. What database are you using? I'm on SQLlite.

[martint123]

The update definitely broke it, it worked fine before and now all the conflicts are broken. What database are you using? I'm on SQLlite.

Sorry, I wasn't doubting you, just pointing out that it wasn't a problem for all.
Yup, I'm on SQLite as well from the previous version. Do you get the pink colours for the conflicts on the TV guide compared to the normal red ones or is it just the conflict/resolve bit that is failing?

[_gl]

Sorry, I wasn't doubting you, just pointing out that it wasn't a problem for all.

No worries, I was just saying that just because it doesn't affect everyone doesn't mean it's not a bug

Yup, I'm on SQLite as well from the previous version. Do you get the pink colours for the conflicts on the TV guide compared to the normal red ones or is it just the conflict/resolve bit that is failing?

It's just Resolve, the only option I get is to 'Make no changes, Leave conflict in place', the conflicting show isn't shown.

However, I went through each of my 25 odd conflicts, and found a couple that did show the conflicting show. Didn't notice any pattern though. Before the upgrade, all conflicts worked as normal.

[sub]

I spent some time today trying to reproduce this, but it seems to be working ok for me.

If you're not using the default blue skin, can you see if changing back to the blue skin resolves it?

[_gl]

I spent some time today trying to reproduce this, but it seems to be working ok for me.

If you're not using the default blue skin, can you see if changing back to the blue skin resolves it?

I've been using the default blue for a long time now, it was just easier than constantly updating 3rd party ones. I can try going back to my backed up previous version to triple-check - it should work with the current database right?

[_gl]

Update, today I checked them again, and now half are working again, the rest are all (or mostly) the same program/channel. So it seems this is actually caused by buggy listings (Radio Times UK XMLTV) that are starting to correct themselves. That it happened exactly the same time I'm upgrading is just bizarre .

Sub, do you want to check my listings to see what's happening?

[roy]

So it seems this is actually caused by buggy listings

I've seen this before (conflicts that aren't) and doing a complete EPG reload removed the conflicts.

[martint123]

I find it very difficult doing a complete EPG reload. With recurring/season recordings parts of the EPG become sticky and if the time of a particular program changes by 5 minutes (quite common in the UK) then you get a conflict that is difficult to get rid of - along with a badly painted TV listing. More than once I've had to copy over the empty database and re-create my season recordings.