https://bugs.kde.org/show_bug.cgi?id=364017
Bug ID: 364017
Summary: recording schedule with qdbus get disabled tv-records
Product: kaffeine
Version: 2.0.1
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mche...@osg.samsung.com
Reporter: tux...@web.de
As I see you improved tv recording.
Kaffeine's sqlite.db has get two fields more in TABLE RecordingSchedule now
(Priority and Disabled)
I'm using a TV-Browser ruby script to schedule recordings.
(http://wiki.tvbrowser.org/index.php/CapturePlugin_-_Kaffeine
Ruby-Script kaffeine-tvbrowser-qdebus.rb)
This script uses qdebus to write in kaffeine-sqlite.db.
ret = system(%Q<bash -c "qdbus org.kde.kaffeine /Television ScheduleProgram
'#{sTitel}' '#{sKanal}' #{sZeit} #{sDuration} 0">)
This all went well in last kaffeine version. But now (vers. 2.0.1) it happens
that not all but most schedulings were set to "disabled" and will not do the
recordings.
I tried to modify the script to give the Priority and Disabled fields a "100"
and "0" which is necessary to set the record to "enabled" but with qdbus it is
not allowed to set more than these five fields above.
It would not be so hard to use an other method in the TV-browser script to do
that, but I thought I should tell you this behaviour, because your
implementation should work with qdbus too.
Android KDE-Connect App is using qdbus and In future a nativ plasma-mobil App
will use qdbus too to work as a remote control.
I thought it could be a solution to set "100" in Priority and "0" in Disabled
fields as default in sqlite.db. But I'm not an expert on programming at all.
Greatings
TuxNix
Reproducible: Sometimes
--
You are receiving this mail because:
You are watching all bug changes.
