Screen lock not responding

[Piotr Gbyliczek]

Hi, 

I'm having an issue with KDE5 in F23 that if I lock screen and leave system 
for longer period of time, I can't unlock the system. It happened twice over 
night and once over a day where I was in meeting, but seen it working fine 
after 1 hour of lunch break. 

Any ideas or links to what this may be and how to fix/workaround ? 

I can't really afford any time searching for it on the list or in google this 
week, I have few projects going close to deadlines, but if it was already 
covered here, please say so and let me be. Link or search string would be 
appreciated if that is the case. 


-- 
Piotr Gbyliczek
Solutions Engineer (LPIC 3, Novell CLA, AWS SAA certified)
Node4 LTD
Tel:  [phone]

[Luigi Toscano]

On Thursday 03 of March 2016 10:02:48 Piotr Gbyliczek wrote:
>  Hi,
>  
>  I'm having an issue with KDE5 in F23 that if I lock screen and leave system
>  for longer period of time, I can't unlock the system. It happened twice over
>  night and once over a day where I was in meeting, but seen it working fine
>  after 1 hour of lunch break.
>  
>  Any ideas or links to what this may be and how to fix/workaround ? 
I've seen it very recently. I don't know the cause, if it's the same issue I 
found that sending a SIGHUP signal to the kscreenlocker process makes it 
responsive again.

There are few changes related to screen lock in Plasma 5.5.5 but I don't see 
this issue. Now, Plasma 5.6 will be out in few days, so it may be worth to 
wait for it and if it is still an issue, file a bug upstream.

Ciao
-- 
Luigi

[Piotr Gbyliczek]

On Thursday 03 March 2016 12:18:18 you wrote:
>  On Thursday 03 of March 2016 10:02:48 Piotr Gbyliczek wrote:
>  > Hi,
>  > 
>  > I'm having an issue with KDE5 in F23 that if I lock screen and leave
>  > system
>  > for longer period of time, I can't unlock the system. It happened twice
>  > over night and once over a day where I was in meeting, but seen it
>  > working fine after 1 hour of lunch break.
>  > 
>  > Any ideas or links to what this may be and how to fix/workaround ?
>  
>  I've seen it very recently. I don't know the cause, if it's the same issue I
>  found that sending a SIGHUP signal to the kscreenlocker process makes it
>  responsive again. 
Good to know, I'll try it next time it does that. I've tried killing it, but 
not with SIGHUP I think.

>  There are few changes related to screen lock in Plasma 5.5.5 but I
> don't see
>  this issue. Now, Plasma 5.6 will be out in few days, so it may be worth to
>  wait for it and if it is still an issue, file a bug upstream. 
I'm not on testing repos, only stable ones, as this is my work machine. So not 
sure how quickly this will get there... Anyway, will keep eye on this and try 
to fill bug report if I'll be able to collect anything.

-- 
Piotr Gbyliczek
Solutions Engineer (LPIC 3, Novell CLA, AWS SAA certified)
Node4 LTD
Tel:  [phone]

[Neal Becker]

Piotr Gbyliczek wrote:

>  On Thursday 03 March 2016 12:18:18 you wrote:
> > On Thursday 03 of March 2016 10:02:48 Piotr Gbyliczek wrote:
> > > Hi,
> > > 
> > > I'm having an issue with KDE5 in F23 that if I lock screen and leave
> > > system
> > > for longer period of time, I can't unlock the system. It happened twice
> > > over night and once over a day where I was in meeting, but seen it
> > > working fine after 1 hour of lunch break.
> > > 
> > > Any ideas or links to what this may be and how to fix/workaround ?
> > 
> > I've seen it very recently. I don't know the cause, if it's the same
> > issue I found that sending a SIGHUP signal to the kscreenlocker process
> > makes it responsive again.
>  
>  Good to know, I'll try it next time it does that. I've tried killing it,
>  but not with SIGHUP I think.
>  
> > There are few changes related to screen lock in Plasma 5.5.5 but I don't
> > see this issue. Now, Plasma 5.6 will be out in few days, so it may be
> > worth to wait for it and if it is still an issue, file a bug upstream.
>  
>  I'm not on testing repos, only stable ones, as this is my work machine. So
>  not sure how quickly this will get there... Anyway, will keep eye on this
>  and try to fill bug report if I'll be able to collect anything.
>   
The problem I've had is I can't put focus in the pw field to enter any 
chars, is that what you mean?

[Piotr Gbyliczek]

On Thursday 03 March 2016 07:42:09 Neal Becker wrote:
>  The problem I've had is I can't put focus in the pw field to
> enter any
>  chars, is that what you mean? 
The only thing that worked was mouse cursor movement, but screen was frozen, 
as in clicking on anything had no reaction. So, in theory it included 
inability to focus in text field and no input from keyboard, but that's only 
part of the problem, I'm sure. 

Regards,
Piotr

[Rex Dieter]

Piotr Gbyliczek wrote:

>  Hi,
>  
>  I'm having an issue with KDE5 in F23 that if I lock screen and leave
>  system for longer period of time, I can't unlock the system. It happened
>  twice over night and once over a day where I was in meeting, but seen it
>  working fine after 1 hour of lunch break.
>  
>  Any ideas or links to what this may be and how to fix/workaround ?
>  
>  I can't really afford any time searching for it on the list or in google
>  this week, I have few projects going close to deadlines, but if it was
>  already covered here, please say so and let me be. Link or search string
>  would be appreciated if that is the case. 
Issue tracked here,

https://bugzilla.redhat.com/show_bug.cgi?id=1313929
See comment 3 for a possible workaround.

I suspect this may be fallout from the recent xorg-x11-drv-intel update that 
(re)enabled dri3 by default,
https://bodhi.fedoraproject.org/updates/FEDORA-2016-606ca05253

The symptoms described now are the same before a prior update was released 
to use dri2 instead,
https://bodhi.fedoraproject.org/updates/FEDORA-2015-8616
and see also related,
"xorg-x11-drv-intel: upstream recommends Disable DRI3"
https://bugzilla.redhat.com/show_bug.cgi?id=1223477

-- Rex

[Piotr Gbyliczek]

On Thursday 03 March 2016 07:45:42 Rex Dieter wrote:
>  Issue tracked here,
>  
>  https://bugzilla.redhat.com/show_bug.cgi?id=1313929
>  See comment 3 for a possible workaround.
>  
>  I suspect this may be fallout from the recent xorg-x11-drv-intel update that
>  (re)enabled dri3 by default,
>  https://bodhi.fedoraproject.org/updates/FEDORA-2016-606ca05253
>  
>  The symptoms described now are the same before a prior update was released
>  to use dri2 instead,
>  https://bodhi.fedoraproject.org/updates/FEDORA-2015-8616
>  and see also related,
>  "xorg-x11-drv-intel: upstream recommends Disable DRI3"
>  https://bugzilla.redhat.com/show_bug.cgi?id=1223477 

Same version of the intel driver, so seems most likely the right candidate.  
I'll keep it on for now if the workarounds with killing processes will work, 
and try to contribute to the bug tracker if I can.

Regards,
Piotr