2015-02-28, 20:05
Sorry for my late reply.
Yes, I have activate the automatet start up and the follow feature. I have tested it and the problem apears when I switch from one profile to next profile (Kodi Logoff). When I use only one profile the bug does not apear.
For test purposes I use one Kodi installation with two profiles. The Kodi db is on a Synology NAS with MariaDB. The two users use the same Kodi db with one sql user.
For WatchedList I create two separate databases. I configured WatchedList to use under every Kodi profile a different database. But they use the same sql user.
WatchedList ignore the diffrent databases and updated every time the wateched state with the data from the other profile.
I'll try it with different SQL usern.
Yes, I have activate the automatet start up and the follow feature. I have tested it and the problem apears when I switch from one profile to next profile (Kodi Logoff). When I use only one profile the bug does not apear.
For test purposes I use one Kodi installation with two profiles. The Kodi db is on a Synology NAS with MariaDB. The two users use the same Kodi db with one sql user.
For WatchedList I create two separate databases. I configured WatchedList to use under every Kodi profile a different database. But they use the same sql user.
WatchedList ignore the diffrent databases and updated every time the wateched state with the data from the other profile.
I'll try it with different SQL usern.
