© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I can confirm this error is only happening on the SSH console login. When run directly from the console AFTER logging in, conflicts are shown properly. If I log out of the SSH session and back in again, only current Scheduled recordings are shown and the Conflicts section has the above error every time.