Bug 364017 - recording schedule with qdbus get disabled tv-records
Summary: recording schedule with qdbus get disabled tv-records
Status: RESOLVED FIXED
Alias: None
Product: kaffeine
Classification: Applications
Component: general (show other bugs)
Version: 2.0.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-06 11:11 UTC by tuxnix
Modified: 2016-09-15 09:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
set recording.disabled to false on dbus ScheduleProgram (608 bytes, patch)
2016-07-22 14:50 UTC, Michael
Details
set recording.disabled to false in dvbEpgModell::scheduleProgram (642 bytes, patch)
2016-07-23 09:56 UTC, Michael
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tuxnix 2016-06-06 11:11:35 UTC
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
Comment 1 Michael 2016-07-22 14:49:33 UTC
I have the same problem and found that a tiny patch will help. On reading the incoming dbus command recording.disabled is not set neither to true nor to false. So just set it like this.
Comment 2 Michael 2016-07-22 14:50:54 UTC
Created attachment 100250 [details]
set recording.disabled to false on dbus ScheduleProgram
Comment 3 Michael 2016-07-23 09:53:58 UTC
Similar problem appears when scheduling a program through the EPG. You have to "confirm" the scheduling by going into the Edit-dialog for the recording.
Comment 4 Michael 2016-07-23 09:56:05 UTC
Created attachment 100257 [details]
set recording.disabled to false in dvbEpgModell::scheduleProgram
Comment 5 Mauro Carvalho Chehab 2016-09-15 09:51:04 UTC
Thanks for the patches! Applied to Kaffeine.