Re: plasma5 screen management going wrong

On Thu, Jul 12, 2018 at 7:06 PM, Bug Reporter wrote: > On Thu, Jul 12, 2018 at 6:03 PM, Bug Reporter wrote: >> see below >> >> On Thu, Jul 12, 2018 at 2:20 AM, Duncan <1i5t5.dun...@cox.net> wrote: >>> Bug Reporter posted on Wed, 11 Jul 2018 21:05:22 -0400 as excerpted: >>> see below

Re: plasma5 screen management going wrong

On Thu, Jul 12, 2018 at 6:03 PM, Bug Reporter wrote: > see below > > On Thu, Jul 12, 2018 at 2:20 AM, Duncan <1i5t5.dun...@cox.net> wrote: >> Bug Reporter posted on Wed, 11 Jul 2018 21:05:22 -0400 as excerpted: >> >>> see below >>> >>> On Mon, Jul 2, 2018 at 2:25 AM, Duncan <1i5t5.dun...@cox.net>

Re: plasma5 screen management going wrong

see below On Thu, Jul 12, 2018 at 2:20 AM, Duncan <1i5t5.dun...@cox.net> wrote: > Bug Reporter posted on Wed, 11 Jul 2018 21:05:22 -0400 as excerpted: > >> see below >> >> On Mon, Jul 2, 2018 at 2:25 AM, Duncan <1i5t5.dun...@cox.net> wrote: >>> Bug Reporter posted on Sun, 01 Jul 2018 21:17:29

Re: plasma5 screen management going wrong

Bug Reporter posted on Wed, 11 Jul 2018 21:05:22 -0400 as excerpted: > see below > > On Mon, Jul 2, 2018 at 2:25 AM, Duncan <1i5t5.dun...@cox.net> wrote: >> Bug Reporter posted on Sun, 01 Jul 2018 21:17:29 -0400 as excerpted: > >> This is likely the kscreen component, or libkscreen ... >> I