Hi,
It seems like recent apps has stopped populating itself in AppDash starting with 5.6 update. I also noticed my recent apps history was wiped out on update. User history should never be deleted without a users permission.
Sudhir Khanger wrote:
Hi,
It seems like recent apps has stopped populating itself in AppDash starting with 5.6 update. I also noticed my recent apps history was wiped out on update. User history should never be deleted without a users permission.
I think what you're seeing is part of: http://bugs.kde.org/361952
Our plasma-desktop-5.6.3-2 packages (and newer) include an experimental patch (referenced in the aforementioned bug) to use the newer kactivities framework. It may not be 100% correct yet.
-- Rex
---- On Tue, 17 May 2016 19:03:33 +0530 Rex Dieter <rdieter@math.unl.edu>wrote ----
Sudhir Khanger wrote:
> Hi,
>
> It seems like recent apps has stopped populating itself in AppDash
> starting with 5.6 update. I also noticed my recent apps history was wiped
> out on update. User history should never be deleted without a users
> permission.
>
I think what you're seeing is part of:
Our plasma-desktop-5.6.3-2 packages (and newer) include an experimental
patch (referenced in the aforementioned bug) to use the newer kactivities
framework. It may not be 100% correct yet.
-- Rex
Any specific reasons we are using an experimental package in stable release product. The upstream dev hasn't replied to the bug report in 3 months. It's stalled for unforeseeable future.
Regards, Sudhir Khanger, sudhirkhanger.com.
Sudhir Khanger wrote:
I think what you're seeing is part of: http://bugs.kde.org/361952 Our plasma-desktop-5.6.3-2 packages (and newer) include an experimental patch (referenced in the aforementioned bug) to use the newer kactivities framework. It may not be 100% correct yet.
Any specific reasons we are using an experimental package in stable release product. The upstream dev hasn't replied to the bug report in 3 months. It's stalled for unforeseeable future.
I included that patch for 2 reasons: * it fixes the regression * it looks like the "right way" to fix it too
I'm disappointed/surprised the upstream maintainer has yet to comment though, good or bad.
-- Rex