https://bugs.kde.org/show_bug.cgi?id=426963
Iyán Méndez Veiga changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=426963
Martin Tlustos changed:
What|Removed |Added
CC||martin.tlus...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=426963
Albert changed:
What|Removed |Added
CC||anonis...@yahoo.com
--- Comment #9 from Albert ---
https://bugs.kde.org/show_bug.cgi?id=426963
--- Comment #8 from S. Christian Collins ---
I was able to stop the crashes by deleting the ~/.local/kactivitymanagerd
folder. Then I just had to recreate my favorites in the application launcher.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=426963
S. Christian Collins changed:
What|Removed |Added
CC||s_chriscoll...@hotmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=426963
--- Comment #6 from Ivan Čukić ---
Thanks.
Seems that database disk corruption can be exposed randomly during work.
KAMD performs some tests on startup and restores the last database known to
work. But it does not cover these errors.
Will see how to
https://bugs.kde.org/show_bug.cgi?id=426963
tildear...@protonmail.com changed:
What|Removed |Added
CC||tildear...@protonmail.com
---
https://bugs.kde.org/show_bug.cgi?id=426963
--- Comment #4 from Iyán Méndez Veiga ---
(In reply to Ivan Čukić from comment #3)
> Can you start kactivitymanagerd from shell and post the output here?
And how can I do that? I only see kactivities-cli in /usr/bin, not
kactivitymanagerd
--
You are
https://bugs.kde.org/show_bug.cgi?id=426963
--- Comment #3 from Ivan Čukić ---
Can you start kactivitymanagerd from shell and post the output here?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426963
--- Comment #2 from Iyán Méndez Veiga ---
(In reply to David Edmundson from comment #1)
> Reading the code non debug builds should fail gracefully, so this is
> relatively low priority.
What do you mean by "fail gracefully"? I got the same crash
https://bugs.kde.org/show_bug.cgi?id=426963
--- Comment #1 from David Edmundson ---
>From the trace presumably
Q_ASSERT_X(success, "Uils::exec", qPrintable(QStringLiteral("Query
failed:") + query.lastError().text()));
Reading the code non debug builds should fail gracefully, so
https://bugs.kde.org/show_bug.cgi?id=426963
David Edmundson changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
12 matches
Mail list logo
