Re: krunner and systemtray broken in testing
Le 08/27/18 à 22:05, Erwan David a écrit :
> Le 08/27/18 à 21:51, Luigi Toscano a écrit :
>> yaros ha scritto:
>>> Dnia poniedziałek, 27 sierpnia 2018 21:25:21 CEST Erwan David pisze:
>>>> Since latest upgrade, krunner does not find anything outside the latest
>>>> documents (and cannot execute command lines), sametime system tray
>>>> cannot start anymore (and this on 2 different machines)
>>>>
>>>> Do someone have a hint on what happens ?
>>>>
>>>> (or is there a workaround) ?
>>>>
>>>>
>>>>
>>> Look at the topic "[Debian/buster] Problems after Upgrade 4:5.13.1-1
>>> to 4:5.13.4-1"
>>> And https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907262
>>>
>>>
>> Namely this email:
>> https://lists.debian.org/debian-kde/2018/08/msg00030.html
>>
> Thanks. So what would be the safest way to get only the needed packages
> from unstable and not keep getting them from unstable in the future ?
>
> My tests with soucre policies in the past lead to catastrophs because
> once a package was installed from unstable it was marked in some way and
> always came from unstable after that.
>
>
ANd another question : how to know the list of packages to upgrade ?
There are many of them for kde, with several naming schemes (plasma*,
kde*, kf* at least).
Reply to: