Re: F20 gnome inactivity causes mouse/kbd unresponsiveness, must restart gnome-shell

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

 




hello pekka,

On 02/12/2014 08:59 AM, Pekka Savola wrote:
Hello,

I've two systems running F20 + updates-testing, a T400 laptop and a
desktop PC. PC was upgraded with yum from F18, laptop was a fresh
install. Both experience the same problems, at least for roughly two
weeks now, maybe longer (not sure when this started, maybe even from
the install in Dec/Jan). The problems are much more severe on the
laptop, though (laptop is on docking station and on power all the
time).

2 physically different computers showing same problem.

using "updates-testing".

After inactivity timeout, you need to swipe the screen or use keyboard
to reactivate it (I've disabled screen locking). The problem that
often occurs is that mouse movement works, but clicking doesn't do
anything. Similarly keyboard is unresponsibe. The clock has been
frozen to the inactivity time.

"problem that often occurs"

are there other problems?

does this problem not always happen?

clock freezing means that a routine has locked up or is possibly
holding off screen refresh.

The workaround is to use CTRL-ALT-F2, log on there and do 'killall
-HUP gnome-shell'. Then you can resume the session (after entering the
password etc.). Sometimes restarting doesn't work.

"use CTRL-ALT-F2", then keyboard is not _completely_ unresponsive.

I've been unable to find similar reports on F20 but maybe I don't know
what to look for. On F18 I found something remotely familiar (but this
occurs pre-locking and there are no errors):
https://bugzilla.redhat.com/show_bug.cgi?id=872118

I see no strange messages in messages, Xorg.0.log or gdm logs.
Any ideas? Where to start digging?

"swag" time.

is there anything special that you have on both systems that
relates to keyboard and/or mouse?

ie, being that i see you are from "fi" land, i wonder if by chance
you are using 'multi language' on your systems.

if so, can/have you create another user as "en" only to see if
problem occurs?

have you tired/considered setting up one of the systems without
using "updates-testing"?

i would suggest that if you are wanting to use "updates-testing",
at least have a partition with non testing, and if you have room,
do such on t400. or just not run "testing" on t400.


--

peace out.

in a world with out fences, who needs gates.

tc.hago.

g
.

--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
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