search for: screenlock

http://bugzilla.mindrot.org/show_bug.cgi?id=496 ------- Additional Comments From hauser at acm.org 2003-03-31 16:56 ------- Created an attachment (id=266) --> (http://bugzilla.mindrot.org/attachment.cgi?id=266&action=view) Readme.txt for the japanese win-ssh-agent.exe/win-ssh-askpass.exe proofread by Nayuta ------- You are receiving this mail because: ------- You are the assignee

...n to remote in, and the display is never unplugged from the system as some of the RedHat bugzilla reports show. I did try a yum update but the problem persists, so I suspect the issue has not been fixed, or if it has, has not been released via the yum default locations. The screensaver and manual screenlock options must be enabled, so disabling them is not an option. I've also developed a cron job to restart gnome-screensaver every few minutes. I've got other systems, built back when CentOS 5.0 was out, that do not experience this problem. I've built newer systems with CentOS 5.4 and 5....

I have a desktop installation with Centos 6. A lot works fine, but suspend to ram or disk does not work from the KDE menu. If I choose suspend to RAM, the screen goes dark (black-light on) but nothing further happens. I can give my password to remove the screenlock and continue. But the machine stays on. Obviously the suspend has failed. If I use pm-suspend (as root) all works fine. I've looked in /var/log/messages but there is no hint there. The question is thus, how can I debug this? Could it be a permission issue? Do I need to add myself to a specific...

...tty quickly, and won't use netgroups at all. netgroup: files automount: files aliases: files services: files sendmailvars: files printers: user files auth_attr: files prof_attr: files project: files /etc/pam.conf (snipped for the dtlogin section only): # CDE login and screenlock dtlogin auth sufficient pam_winbind.so debug use_first_pass use_authtok dtlogin auth requisite pam_authtok_get.so.1 debug dtlogin auth required pam_dhkeys.so.1 debug #dtlogin auth optional...

I have an ssh only login to a G5 on which I am hoping to run some analyses. The situation is complicated by the fact that the computer's owner is away for the summer (and thus also only has shell login). R is installed and there is a symlink to /usr/local/bin/R but when I try to launch it I get: [jhowison at euro]$ R kCGErrorRangeCheck : Window Server communications from outside of

https://bugs.freedesktop.org/show_bug.cgi?id=69029 Priority: medium Bug ID: 69029 Assignee: nouveau at lists.freedesktop.org Summary: GT218 (NVA8): GPU lockup since kernel 3.11 upgrade QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fred at

...I was running fine for a long time with no problems. Today with openSUSE 12.3 (KDE 4.10.3, Xorg 1.13.2, upgraded on Jun. 10), my machine hung completely. I believe the nouveau driver is at fault rather than KDE or X, so chose this list. I think it might have been triggered by the "Clock" ScreenLocker (screen saver). It happened twice so far. I'm not on the list, so please CC me. Here is a snippet from syslog where some strange stuff begins (while I am not using the computer): 2013-06-14T03:59:34.103035+02:00 linux-zxd7 kernel: [303714.267370] nouveau E[ PFIFO][0000:04:00.0] DMA_PUSH...

https://bugs.freedesktop.org/show_bug.cgi?id=99922 Bug ID: 99922 Summary: [NVE4] [regression, bisected] 4.10 (atomic): X shows black screen with cursor after monitors turn off Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Keywords: bisected