KDE Screen Unlock Issue

[cirehawk]

I've been having an issue for a while now and am wondering if anyone else has seen this.  I always lock my screen so when when I return I have to enter a password to unlock it.  I'm using a generic screensaver as well.  There are random times when I unlock the computer where the unlock dialog box remains on the screen after it's unlocked.  The only way I have been able to get rid of the dialog box is by logging out and logging back in.  Has anyone else had this happen?  By the way, I'm using the nVidia drivers.

[shimonl]

YES!!
I had this problem, it was terrible. Started dragging windows around to be able to see them
where they were not blocked by that dialog glued onto the front of my screen...
Especially bad when I was working on something which would be lost at logout.

1. I also would lock my screen
2. I had a screensaver chosen from 'configure your desktop'/hardware/display/slideshow.
3. no nvidia, I have a standard builtin intel controller.
4. as you say, nothing short of logging out seemed to help. adding new desktops just got
    the same ugly patch on the new ones.

This happened along with various other problems,
and I ended up dumping that install of PCLOS, and
moving to FullMonty on another partition.

At the time I also remember asking here if there was some way to reinitialize the display to
fix this problem, but I don't recall getting any suggestions.

So, I feel for you, but I am sorry I can't help.

[pags]

Have you tried xkill to see if it can terminate the wayward window?

[shimonl]

The problem is, it isn't a window at all!
It sort of gets glued on to the screen OVER all the windows,
the way the 'desktop' is UNDER all windows.
It's just... *there*.

(At least that was how it happened to me, I don't know about the OP)

[pags]

The problem is, it isn't a window at all!
It sort of gets glued on to the screen OVER all the windows,
the way the 'desktop' is UNDER all windows.
It's just... *there*.

(At least that was how it happened to me, I don't know about the OP)

Still, could be related to a hung process...X may still have code running to display it (especially as there are two reports on different video hardware...seems to reduce the chance of a driver issue).
Test with xkill, if it re-occurs...I don't think you have anything to lose...

XKILL(1)                                   General Commands Manual                                  XKILL(1)

NAME
       xkill - kill a client by its X resource

SYNOPSIS
       xkill [-display displayname] [-id resource] [-button number] [-frame] [-all]

DESCRIPTION
       Xkill  is  a  utility for forcing the X server to close connections to clients.  This program is very
       dangerous, but is useful for aborting programs that have displayed  undesired  windows  on  a  user's
       screen.  If no resource identifier is given with -id, xkill will display a special cursor as a prompt
       for the user to select a window to be killed.  If a pointer button is pressed over a non-root window,
       the server will close its connection to the client that created the window.

OPTIONS
       -display displayname
               This option specifies the name of the X server to contact.

       -id resource
               This  option  specifies the X identifier for the resource whose creator is to be aborted.  If
               no resource is specified, xkill will display a special cursor with which you should select  a
               window to be kill.

       -button number
               This  option specifies the number of pointer button that should be used in selecting a window
               to kill.  If the word "any" is specified, any button on the pointer may be used.  By default,
               the first button in the pointer map (which is usually the leftmost button) is used.

       -all    This option indicates that all clients with top-level windows on the screen should be killed.
               Xkill will ask you to select the root window with each of the currently  defined  buttons  to
               give you several chances to abort.  Use of this option is highly discouraged.

       -frame  This option indicates that xkill should ignore the standard conventions for finding top-level
               client windows (which are typically nested  inside  a  window  manager  window),  and  simply
               believe that you want to kill direct children of the root.

CAVEATS
       This  command  does not provide any warranty that the application whose connection to the X server is
       closed will abort nicely, or even abort at all. All this command does is to close the  connection  to
       the  X  server.  Many  existing applications do indeed abort when their connection to the X server is
       closed, but some can choose to continue.

XDEFAULTS
       Button  Specifies a specific pointer button number or the word "any" to use when selecting windows.

SEE ALSO
       X(7), xwininfo(1), XKillClient and XGetPointerMapping in the Xlib Programmers Manual,  KillClient  in

[cirehawk]

Thanks for the inputs.  I'll try xkill later to see if it helps.