Bug 182289 - autolaunch Kaffeine for recordings
Summary: autolaunch Kaffeine for recordings
Status: REOPENED
Alias: None
Product: kaffeine
Classification: Applications
Component: general (show other bugs)
Version: 2.0.15
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-29 12:11 UTC by Fabian Baumert
Modified: 2021-02-21 19:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Baumert 2009-01-29 12:11:19 UTC
Version:            (using KDE 4.1.3)
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.27.7-9-default
Installed from:    SuSE RPMs

If you programm a DVB-T record-time into kaffeine and the programm isn't running during the timeframe programmed, the programmed time-frame isn't deleated on restart. When you close kaffeine, the programm still reports the fact that there are programmed recordings and asks if I really want to close the programm even if all the events are in the past.

It would be nice to have a deamon, checking system time and launching Kaffeine automaticly for a programmed recording.
Comment 1 Christoph Pfister 2010-08-11 21:22:26 UTC
the first part is surely solved in Kaffeine 1.0, the second part isn't that easy
Comment 2 Mauro Carvalho Chehab 2016-06-06 00:27:14 UTC
This bug is too old, for a version < 1.3. Closing it, as the latest version is 2.0.1, and lots of things changed since version 1.2.x, including the usage of VLC as video display backend, support for DVB-T2 and ISDB-T via libVLC, etc.

You may check on the upstream version and see if the bug was solved. The README file contains instructions about how to compile it. You can find it at our git repository: 

https://quickgit.kde.org/?p=kaffeine.git 

If you find similar issues with version 2.0.1, please re-open.
Comment 3 Shane Whittet 2021-02-21 19:52:18 UTC
This is still an issue with 2.0.15.