https://bugs.kde.org/show_bug.cgi?id=485719
--- Comment #6 from Josh W <winchesterjosh...@gmail.com> --- Yes, I too am using spacebar 24.05 which as you mentioned, per https://invent.kde.org/plasma-mobile/spacebar/-/merge_requests/159 it should be fixed. The original user for that issue mentioned that it fixed the issue for them, and they had also mentioned the specific error they suspected it to be was: futuresql: SQL error: "no such table: Messages Unable to execute statement" I thought these issues might be related, because of these lines in my journalctl output: May 30 19:21:42 pcubed spacebar-daemon[4249]: current (old) database revision 8 May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: Marking migration "2023-05-07-102621_init" as done. May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: SQL error: "UNIQUE constraint failed: __qt_schema_migrations.version Unable to fetch row" May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: Migrations finished I am quite sure the issue is related to futuresql and how spacebar uses it. -- You are receiving this mail because: You are watching all bug changes.
