Bug 18721

Summary:	Latest Kaffeine completely messes up 'Recording Schedule'
Product:	Mageia	Reporter:	DariuszSki <linuxstuff>
Component:	RPM Packages	Assignee:	David GEIGER <geiger.david68210>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kaffeine-1.3.1-1.mga5	CVE:
Status comment:

Description DariuszSki 2016-06-17 10:35:06 CEST

Description of problem:

Currently using Kaffeine 1.2.2 because of the following problem, I don't know if it's a bug or my setup problem.

The latest recently released version (1.3.1) allows the TV channels to switch MUCH faster, that's great. But when you upgrade, any TV shows in the "recording schedule" option appear blanked, however, looking at the Kaffeine SQLLite database shows any shows already programmed are still there, but as much as I've managed to test, won't record with version 1.3.1.

If you programme a new show in the latest version of Kaffeine, it doesn't enter into the database, and if Kaffeine is restarted, the show you just entered into "record schedule" vanishes.

Having enabled backports, I was able to delete the latest Kaffeine version and re-install version 1.2.2, where everything works again, but without the speed improvements of the latest version.


Version-Release number of selected component (if applicable):
Kaffeine 1.3.1-1.mga5

Upgrade from version 1.2.2 to 1.3.1

Steps to Reproduce:
1. Install / use latest Kaffeine version.

Marja Van Waes 2016-06-18 12:26:40 CEST

CC: (none) => marja11
Assignee: bugsquad => geiger.david68210

Comment 1 David GEIGER 2016-06-18 14:36:16 CEST

Hi,

Can you report this bug upstream, please?

https://bugs.kde.org/

Perhaps a similar bug has already been opened???

Comment 2 Marja Van Waes 2018-04-24 19:39:09 CEST

No reply, no link to an upstream bug report :-/

Closing as OLD, because Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

Resolution: (none) => OLD
Status: NEW => RESOLVED