Summary: | kactivitymanagerd crashes if libQt5Sql5-sqlite is not installed | ||
---|---|---|---|
Product: | [Plasma] kactivitymanagerd | Reporter: | Wolfgang Bauer <wbauer1> |
Component: | general | Assignee: | Ivan Čukić <ivan.cukic> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | plasma-bugs |
Priority: | NOR | ||
Version: | 5.11.95 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
URL: | http://bugzilla.opensuse.org/show_bug.cgi?id=1078173 | ||
Latest Commit: | Version Fixed In: |
Description
Wolfgang Bauer
2018-01-30 11:23:50 UTC
I'm not convinced that a bad installation/setup can be handled more gracefully than showing the exact error in the output. The question I have is what driver is QSQLITE3 in opensuse's Qt packaging - I'm asking because it does not exist in the Qt's docs [1] - only QSQLITE2 and QSQLITE exist, where the QSQLITE driver handles sqlite 3 and above. [1] http://doc.qt.io/qt-5/sql-driver.html (In reply to Ivan Čukić from comment #1) > I'm not convinced that a bad installation/setup can be handled more > gracefully than showing the exact error in the output. The problem is that the system is more or less unusable though (because kactivitymanagerd keeps restarting and crashing endlessly, and systemd-coredump creates one coredump after the other), and the user won't see the output anyway of course. Similar things happen when the database gets corrupted btw, there were a few users having that problem recently, e.g.: https://forums.opensuse.org/showthread.php/530020-Help-working-process-quot-system-coredump-quot > The question I have is what driver is QSQLITE3 in opensuse's Qt packaging - > I'm asking because it does not exist in the Qt's docs [1] - only QSQLITE2 > and QSQLITE exist, where the QSQLITE driver handles sqlite 3 and above. That's the one from akonadi, which I happen to have installed. libQt5Sql5-sqlite OTOH contains the standard one from qtbase, with that installed it works (unless the database is corrupted or similar). Ok, that explains things. As for the assert, yes it needs to go away. I expected sqlite to be stable enough not to have these issues (thus asserting and qFataling on errors). I'll close this issue - the database corruption issue is tracked in the https://bugs.kde.org/show_bug.cgi?id=389441 *** This bug has been marked as a duplicate of bug 389441 *** |