> It can also be simply not installed.
> That was the case for the Neon/Netrunner reports.
Yes, Bhushan covered that part - not starting or crashing. I just
specified the cases where kamd is 'expected' to crash.
>> One of the things that we could try is for kactivities to return
>> 'Unknown' as
On Sat, Jul 23, 2016 at 9:07 PM, Ivan Čukić 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
On Sat, Jul 23, 2016 at 06:50:45PM +0200, Marco Martin wrote:
>
> I was surprised plasma-mobile was without kamd, and yes, the fact that
> before it appeared to be "working", it was ctually wrong
>
I will adjust mobile packaging to install kactivitymanagerd as well, and
perhaps plasma-workspace
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.
Other than that, I haven't had any crashes reported for quite a long time now.
Are there any
On Sat, Jul 23, 2016 at 6:50 PM, Marco Martin wrote:
>> This commit seems to break plasmashell loading in various cases, I at
>> least have one report from #kde-neon that plasmashell is not starting
>> and I've locally also reproduced that if kactivitymanagerd is not
>>
On Fri, Jul 22, 2016 at 5:12 PM, Bhushan Shah wrote:
>> http://commits.kde.org/plasma-workspace/f7ef6ee87b8957bebc976b6fc9e0df279cea05f1
>>
>
> This commit seems to break plasmashell loading in various cases, I at
> least have one report from #kde-neon that plasmashell is not
Hello Marco and co.
On Wed, Jul 20, 2016 at 11:59:37AM +, Marco Martin wrote:
> Git commit f7ef6ee87b8957bebc976b6fc9e0df279cea05f1 by Marco Martin.
> Committed on 20/07/2016 at 11:57.
> Pushed by mart into branch 'Plasma/5.7'.
>
> don't try to load layout before kamd starts
>
> if the