similar to: tty login vs Gnome screen lock

Which Keyboard-Layout do you use ? Maybe that's the trick... Well, i use Germay Keyboard Layout, but when the Screen lock is coming up The "z" and "y" is swapped (qwertz vs. querty). Try logging in Using us-keyboard-Layout. Just my 2 cents... Regards Marc Rebischke ----- Urspr?ngliche Nachricht ----- Von: Scott Ehrlich <scott at MIT.EDU> Gesendet: Dienstag, 15.

For an out-of-box Centos install that utilizes PAM for xscreensaver within both gnome and kde, what factors would lead to xscreensaver not being able to properly unlock the user? I reviewed the logs and nothing helped. I performed ldd on xscreensaver and an ls -l on each dependency proved they were all there. The system uses local /etc/passwd and /etc/shadow files for authentication - no

I've built some CentOS 5.5 64-bit systems straight off the DVD, full installs, and the Gnome screen lock (manually invoked or automatically via the gnome-screensaver) does not allow the user to unlock the screen. The only fix appears to be ctrl-alt-F<1 - 5> then have the user log into the tty session, type pkill -f gnome-screensaver, log out, then ctrl-alt-f7 to return to X. These

I hope someone can help me because I have spent a week on this and still I can't make it to work. I have a CentOS 5.5 server and I am trying to set it up so that upon login the gnome default keyring is unlocked. I don't have a desktop as users will login using ssh only. I have search the forum and google it, and I did find some help. All the articles though said to change /etc/pam.d/gdm

Hello, I need to reconfigure Gnome in CentOS for avoiding that a normal user could lock screen using task bar option and/or "Super L" key (Windows Key + L). How could I configure Gnome? I need to do that in several computers, so I can't do "login" in X environment of each computer, but I need to reconfigure executing from command line (multiple SSH connections).

Hello, after update my sshd to openssh-5.8_p2 (Linux Gentoo) I stated, that all ssh login (that open terminal session) causes writing of 2 records to a wtmp log. For example: user1 pts/4 gw.testdom.net Mon Jun 20 13:33 still logged in user1 ssh gw.testdom.net Mon Jun 20 13:33 - 13:38 (00:05) The first one is a standard record which appears only if a terminal

Hi all, I have two servers both identical in hardware and I have just done a clean install of CentOS 5.2 x86_64 on both. Sometimes (more often than not) when I log in at the physical console (e.g. tty1, tty2, etc.) I will be logged in and it stops responding even if the shell is not doing anything. When this happens I can still switch to another VT with alt+f2 and login as normal. I don't

[mod: This is the second time in a week that someone asks this question: is it a new attack? It sure looks to me like "userland" has completely locked up, but that the kernel is still working. As an isolated case, my diagnosis is: You probably have a bad block in your /bin/login program or something like that. When two people report this in a week, it's starting to become unlikely

Hi, Environment: I am using CentOS 5.3 operating system. I upgraded xorg of centos to 7.3. I am using intel 945 GM board. My xorg server version is 1.4.2 and inetl driver version 2.4.3. gnome-screensaver version is 2.16.1-8.el5. Problem: I connected another system of same hardware using VGA output. Now I can see clone of my system on secondary display. I enabled screensaver with 1 minute period

A user wants to time a command/program/application and ensure the full contents of that command's data management has been flushed from RAM/cache and saved to disk. Is there a way to ensure the cache/RAM is flushed to disk, or is the flushing a function of the kernel or the application? This happens to be on a 64-bit Intel system with 64-bit CentOS 5, fully patched. But even if the

https://bugs.freedesktop.org/show_bug.cgi?id=101206 Bug ID: 101206 Summary: intermittent lock up after login to GNOME under wayland Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Block drivers like nbd and rbd unlock struct request_queue->queue_lock in their request_fn. I'd like to do the same in virtio_blk. After happily posting the patch, Michael Tsirkin pointed out an issue that I can't explain. This may affect existing block drivers that unlock the queue_lock too. What happens when the block device is removed (hot unplug or kernel module unloaded) while

Block drivers like nbd and rbd unlock struct request_queue->queue_lock in their request_fn. I'd like to do the same in virtio_blk. After happily posting the patch, Michael Tsirkin pointed out an issue that I can't explain. This may affect existing block drivers that unlock the queue_lock too. What happens when the block device is removed (hot unplug or kernel module unloaded) while

https://bugs.freedesktop.org/show_bug.cgi?id=100433 Bug ID: 100433 Summary: Kernel Oops on attempting to return from locked screen on gnome-session Product: Mesa Version: 17.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

On 2018/12/11 ??9:34, Michael S. Tsirkin wrote: > On Mon, Dec 10, 2018 at 05:44:52PM +0800, Jason Wang wrote: >> When we try to do rx busy polling in tx path in commit 441abde4cd84 >> ("net: vhost: add rx busy polling in tx path"), we lock rx vq mutex >> after tx vq mutex is held. This may lead deadlock so we try to lock vq >> one by one in commit 78139c94dc8c

If I set up a room of Win XP Pro w/SP2 systems, hardened via local policy and gpedit.msc, and add them to a samba domain running from an unpatched, out-of-box install of RHEL 5.0, how will the local XP policies differ from any changes I make to pdbedit on the Samba side? Which takes priority/preference? Thanks. Scott

Hi all wine users and developers, I have a touch question which I have been searching answers for quite a long time to configure wine but still have not solved yet. Wine is the only Windows program simulator running in Linux which I use, however one thing annoying me is that currently the cursor is always blinking in the GUI. For example, the editplus running in wine. Something it really drives

About a year ago I outlined a scheme for arranging chowning of the tty end of ptys without needing root privileges. Since then, I haven''t had time to actually implement it. I was thinking about the problem again today, and, having learned a bit about sessions and controlling ttys and stuff, was able to come up with a simpler mechanism. First, observe that the POSIX session mechanism, if

I am running Windows 10 vms on a Linux host with libvirt 4.0.0 and qemu 2.10.2 I can shutdown and reboot the Windows 10 guests if the no user is logged in the vm, or if the user is logged in and active/seeing the desktop. But after a while, when the lock screen kicks in (but the user is still logged in technically), the shutdown and reboot commands don't have any effect any more. Is

http://bugzilla.mindrot.org/show_bug.cgi?id=272 Summary: Ctrl-C exits - Can not open TTY Product: Portable OpenSSH Version: -current Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: