Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#29436 - recording rules issues after upgrade to 0.25
Attached to Project:
Community Packages
Opened by Willem van Asperen (wasperen) - Friday, 13 April 2012, 19:53 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 14 April 2012, 09:25 GMT
Opened by Willem van Asperen (wasperen) - Friday, 13 April 2012, 19:53 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 14 April 2012, 09:25 GMT
|
DetailsDescription:
Just upgraded to 0.25 (on Arch Linux using the latest package 0.25-1). Now my frontend does not show the Recording Rules. Also no Upcoming Recordings. In the System Status, it shows 79 standard rules and 12 search rules are defined. But 0 matching showings... When trying to schedule a random recording, it does not show up in the Upcoming Recordings. When I try to change one of my search rules I get the following in the console: {{{ REPLACE INTO customexample (rulename,fromclause,whereclause,search) VALUES(?,?,?,?); Bindings were: :FROMC=NULL, :RULE="de wereld draait door", :SEARCH=true, :WHEREC="program.title LIKE 'de wereld draait door%' AND WEEKDAY(program.starttime) < 5 AND HOUR(program.starttime) >= 19 AND HOUR(program.starttime) < 23 " Driver error was [2/1048]: QMYSQL3: Unable to execute statement Database error was: Column 'fromclause' cannot be null }}} Additional info: package 0.25-1 |
This task depends upon
Closed by Jelle van der Waa (jelly)
Saturday, 14 April 2012, 09:25 GMT
Reason for closing: Not a bug
Additional comments about closing: issue was in settings for local backend and master backend. not sure whether prev. version accepted 127.0.0.0 and the hostname respectivly or these where changed during the upgrade...
Saturday, 14 April 2012, 09:25 GMT
Reason for closing: Not a bug
Additional comments about closing: issue was in settings for local backend and master backend. not sure whether prev. version accepted 127.0.0.0 and the hostname respectivly or these where changed during the upgrade...