[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Nate Graham changed: What|Removed |Added Priority|HI |NOR -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Eric Edlund changed: What|Removed |Added Priority|NOR |HI CC||ericedlund2...@gmail.com Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Nate Graham changed: What|Removed |Added CC||0xe2.0x9a.0...@gmail.com --- Comment #11 from Nate Graham --- *** Bug 376814 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Nate Graham changed: What|Removed |Added CC||de...@krutt.org --- Comment #10 from Nate Graham --- *** Bug 396340 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 locked.sha...@openmailbox.org changed: What|Removed |Added CC||locked.shadow@openmailbox.o ||rg -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Ivan Čukić changed: What|Removed |Added CC||wba...@tmo.at --- Comment #9 from Ivan Čukić --- *** Bug 389640 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 --- Comment #8 from Ivan Čukić --- The first step done - KAStats will not do any qFatals and Q_ASSERTS while reading from the database. As requested, it will fail silently (will do a qWarning) and report empty data sets. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Christoph Feck changed: What|Removed |Added CC||tokmajigeo...@gmail.com --- Comment #7 from Christoph Feck --- *** Bug 390516 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 --- Comment #6 from Ivan Čukić --- @Luca Activity info can not be lost. At least I don't see how it can. What can happen is KAMD refusing to start making Plasma think there is only one activity - 00--000-0 (pretend this is a null uuid :) ). But all should be fine when KAMD is restarted with a functioning database. Unless something strange is going on. @Marco That Okteta use-case is not supported, sorry. :P Yes, an approach like that would be fine - backup linked resources from time to time, and maybe the score caches, omitting the resource events as they are not that important. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #5 from Marco Martin --- i managed to reproduce the error (actually by writing random nonsense in the database file with okteta :p) tough i couldn't reproduce the loss of activities in plasma. what i think it could be done is:(which is i think similar to what firefox does) * when this error occurs, not asserting but try to move the database file in a database.corrupt file * open it again and repopulate (since activity names and ids are saved in a config file all of this should be fine) * every now and then backup the content of some tables (even just a text file with the inserts) at least the ResourceLink table * when this emergency recreation happens, import that text file to have favorites back -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #4 from Luca Beltrame --- When corruption happens, this can lead to losing activity information completely (activity contents are reset to default state), so this effectively causes data loss. I'm not sure if it's due to kamd itself or its interaction with Plasma, though. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 389441] kactivitymanagerd does not handle DB corruption properly
https://bugs.kde.org/show_bug.cgi?id=389441 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Summary|kactivitymanagerd keeps |kactivitymanagerd does not |crashing on a loop |handle DB corruption ||properly --- Comment #3 from Ivan Čukić --- Yes relying on upstream to work properly was not a good idea. I'll probably have to go the Firefox way - export the database from time to time, and in the case of a DB problem, recreate it. -- You are receiving this mail because: You are watching all bug changes.
