Re: Cannot unlock screen from the lock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jean Jacques wrote:
Will try it but seems just happens under Gnome-Shell.

That's a bit of information which clearly make a difference. Can't help, went to XFCE back in fc16, there was no user demand for GNOME3, the greatest enthusiasm encountered was at the "I can live with it" level, users figured out XFCE with essentially no help, now that MATE is looking pretty solid, we have that around as well.

2013/2/7 Richard Vickery <richard.vickeryrv@xxxxxxxxx
<mailto:richard.vickeryrv@xxxxxxxxx>>

    I think I figured the screen-lock out quite by accident: perhaps the
    solution that you are looking for is "space-bar then the Enter key"

    hope this helps,

    Richard

Thank you, I added it to my "tricks I hope I never need" folder, useful if the problem shows up.


    On Wed, Feb 6, 2013 at 3:22 AM, Bryn M. Reeves <bmr@xxxxxxxxxx
    <mailto:bmr@xxxxxxxxxx>> wrote:

        On 02/06/2013 11:04 AM, Jean Jacques wrote:


            Has any one encountered the problem that the screen cannot back from
            lock? The new lock screen does not unlock after the password has been
            entered.



        I've seen similar behaviour in a few situations: when the load on the
        box is extremely high it may take minutes (or tens of minutes if
        severely stressed) for the authentication to complete. I've seen this
        with runaway browsers and other processes chewing memory and CPU time.
        Typically in this case the password dialog is also slow to appear and
        the cursor may be laggy and unresponsive.

        The other one that comes to mind is a problem with authentication itself
        - if using network auth then a problem with the network or backend
        service may cause unlock delays. This should be less of a problem with
        local authentication.

        Finally, you might have a deadlock or task blocked on IO - for e.g. a
        kernel or driver bug or some storage device. I've seen this with file
        system bugs for e.g. when some IO never completes.

        Depending on where things are stuck you may be able to switch to a
        virtual terminal, log in, and debug from there.

        Regards,
        Bryn.


--
Bill Davidsen <davidsen@xxxxxxx>
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux