[plasma-workspace/Plasma/5.7] shell: don't try to load layout before kamd starts

[David Edmundson]

On Sat, Jul 23, 2016 at 9:07 PM, Ivan Čukić <ivan.cukic at kde.org> wrote:

> The only reasons for kamd to crash are inability to create WAL sqlite
> database (it will return an assert with a detailed message), and to
> crash on *exit* due to the QSql bug related to driver deinit.
>
> It can also be simply not installed.
That was the case for the Neon/Netrunner reports.

And whilst that is a downstream bug, plasma shell code does try to make it
optional. if we want to make it mandatory we should make the code fully do
that.


> Other than that, I haven't had any crashes reported for quite a long time
> now.
>
> Are there any backtraces or more info related to this issue?
>
> One of the things that we could try is for kactivities to return
> 'Unknown' as the state until it figures out whether there is kamd
> running or not. And then set it as Running or NotRunning.
>

+100



> But Plasma will still have to decide what to do in both cases.
>
> Cheers,
> Ivan
>
> p.s. I've approved D2275 - the old script was indeed very wrong.
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160725/a81ec8fc/attachment.html>