I suspend to RAM and it shuts down after a few seconds, leaving the PC in a nice, low-power state.
Then, I hit a key and the system comes up without apparent problems.
The screen is locked and it asks for my password. I type my correct password and it’s not recognized.
I click “Switch Users”, select a different account, get the new lock screen, click “Switch Users”, select my account again, and my password is now recognized. I didn’t have to log in as the other user, just switch to that session.
Following another thread’s recommendation, I uninstalled pm-utils, with no effect.
This problem only started recently, perhaps after I installed the 70 or so updates since the last update, but the timeline isn’t exact.
Have you seen the lock screen get your password wrong after sleep? Are there packages that might be worth re-installing or reverting?
[Jan 2 03:38] PM: Syncing filesystems ... done.
+0.476500] PM: Preparing system for mem sleep
+0.121207] Freezing user space processes ... (elapsed 0.001 seconds) done.
+0.001840] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
+0.001214] PM: Entering mem sleep
+0.000032] Suspending console(s) (use no_console_suspend to debug)
+0.000294] sd 5:0:0:0: [sdb] Synchronizing SCSI cache
+0.000011] sd 4:0:0:0: [sda] Synchronizing SCSI cache
+0.002639] sd 4:0:0:0: [sda] Stopping disk
+0.000369] sd 5:0:0:0: [sdb] Stopping disk
+0.000218] nouveau DRM] suspending fbcon...
+0.000006] nouveau DRM] suspending display...
+0.000006] nouveau DRM] unpinning framebuffer(s)...
+0.000025] mpt2sas0: pdev=0xffff88032f030000, slot=0000:04:00.0, entering operating state [D3]
+0.000005] mpt2sas0: sending diag reset !!
+0.000003] nouveau DRM] evicting buffers...
+1.130350] mpt2sas0: diag reset: SUCCESS
+0.078642] nouveau DRM] waiting for kernel channels to go idle...
+0.000006] nouveau DRM] suspending client object trees...
+0.001109] nouveau DRM] suspending kernel object tree...
+2.910093] PM: suspend of devices complete after 4121.454 msecs
+0.000231] PM: late suspend of devices complete after 0.228 msecs
+0.000505] pcieport 0000:00:1c.2: System wakeup enabled by ACPI
+0.011055] pcieport 0000:00:1c.1: System wakeup enabled by ACPI
+0.011124] ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
+0.010882] uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI
+0.000051] uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI
+0.000048] uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI
+0.000124] ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI
+0.010781] uhci_hcd 0000:00:1a.2: System wakeup enabled by ACPI
+0.000049] uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI
+0.000048] uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI
+0.000200] PM: noirq suspend of devices complete after 44.841 msecs
+0.000336] ACPI: Preparing to enter system sleep state S3
+0.000602] PM: Saving platform NVS memory
+0.000323] Disabling non-boot CPUs ...
+0.001913] smpboot: CPU 1 is now offline
+0.001773] smpboot: CPU 2 is now offline
+0.001873] smpboot: CPU 3 is now offline
+0.002064] smpboot: CPU 4 is now offline
+0.001848] smpboot: CPU 5 is now offline
+0.001784] smpboot: CPU 6 is now offline
+0.001823] smpboot: CPU 7 is now offline
+0.001501] ACPI: Low-level resume complete
+0.000049] PM: Restoring platform NVS memory
+0.000404] Enabling non-boot CPUs ...
+0.000130] smpboot: Booting Node 0 Processor 1 APIC 0x2
+0.013615] CPU1 is up
+0.000095] smpboot: Booting Node 0 Processor 2 APIC 0x4
+0.013620] CPU2 is up
+0.000096] smpboot: Booting Node 0 Processor 3 APIC 0x6
+0.013635] CPU3 is up
+0.000092] smpboot: Booting Node 0 Processor 4 APIC 0x1
+0.013681] CPU4 is up
+0.000089] smpboot: Booting Node 0 Processor 5 APIC 0x3
+0.013666] CPU5 is up
+0.000093] smpboot: Booting Node 0 Processor 6 APIC 0x5
+0.013680] CPU6 is up
+0.000096] smpboot: Booting Node 0 Processor 7 APIC 0x7
+0.013711] CPU7 is up
+0.005764] ACPI: Waking up from system sleep state S3
+0.000597] uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI
+0.000038] uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI
+0.000038] uhci_hcd 0000:00:1a.2: System wakeup disabled by ACPI
+0.010152] ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI
+0.011189] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI
+0.000040] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
+0.000038] uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI
+0.010758] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
+0.034968] /dev/vmmon[0]: HostIFReadUptimeWork: detected settimeofday: fixed uptimeBase old 18445323894521088212 new 18445323894508222961 attempts 1
+0.020273] PM: noirq resume of devices complete after 87.679 msecs
+0.000125] PM: early resume of devices complete after 0.095 msecs
+0.000122] pci 0000:00:1e.0: setting latency timer to 64
+0.000014] ahci 0000:00:1f.2: setting latency timer to 64
+0.000055] mpt2sas0: pdev=0xffff88032f030000, slot=0000:04:00.0, previous operating state [D0]
+0.000029] pcieport 0000:00:1c.1: System wakeup disabled by ACPI
+0.000006] uhci_hcd 0000:00:1a.0: setting latency timer to 64
+0.000007] pcieport 0000:00:1c.2: System wakeup disabled by ACPI
+0.000016] usb usb3: root hub lost power or was reset
+0.000165] uhci_hcd 0000:00:1a.1: setting latency timer to 64
+0.000020] usb usb4: root hub lost power or was reset
+0.000136] uhci_hcd 0000:00:1a.2: setting latency timer to 64
+0.000019] usb usb5: root hub lost power or was reset
+0.000141] ehci-pci 0000:00:1a.7: setting latency timer to 64
+0.000107] snd_hda_intel 0000:00:1b.0: irq 70 for MSI/MSI-X
+0.000115] uhci_hcd 0000:00:1d.0: setting latency timer to 64
+0.000021] usb usb6: root hub lost power or was reset
+0.000089] uhci_hcd 0000:00:1d.1: setting latency timer to 64
+0.000019] usb usb7: root hub lost power or was reset
+0.000094] uhci_hcd 0000:00:1d.2: setting latency timer to 64
+0.000019] usb usb8: root hub lost power or was reset
+0.000066] ehci-pci 0000:00:1d.7: setting latency timer to 64
+0.000094] nouveau DRM] re-enabling device...
+0.000009] nouveau DRM] resuming kernel object tree...
+0.000006] nouveau VBIOS][0000:06:00.0] running init tables
+0.000021] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (12320872 kB)
+0.000066] mpt2sas 0000:04:00.0: irq 71 for MSI/MSI-X
+0.000020] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 71
+0.000001] mpt2sas0: iomem(0x00000000f7ffc000), mapped(0xffffc900168d0000), size(16384)
+0.000001] mpt2sas0: ioport(0x000000000000b000), size(256)
+0.009517] r8169 0000:07:00.0 enp7s0: link down
+0.050348] mpt2sas0: LSISAS2008: FWVersion(14.00.01.00), ChipRevision(0x03), BiosVersion(07.27.00.00)
+0.000003] mpt2sas0: Protocol=(Initiator), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
+0.000057] mpt2sas0: sending port enable !!
+0.243497] ata1: SATA link down (SStatus 0 SControl 300)
+0.004073] ata3: SATA link down (SStatus 0 SControl 300)
+0.000937] ata4: SATA link down (SStatus 0 SControl 300)
+0.151115] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
+0.006434] ata2.00: configured for UDMA/100
+0.084504] nouveau DRM] resuming client object trees...
+0.000806] nouveau DRM] resuming display...
+0.322387] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
+0.000642] ata5.00: supports DRM functions and may not be fully accessible
+0.004717] ata5.00: supports DRM functions and may not be fully accessible
+0.004392] ata5.00: configured for UDMA/133
+0.000123] sd 4:0:0:0: [sda] Starting disk
+0.037149] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
+0.000646] ata6.00: supports DRM functions and may not be fully accessible
+0.004773] ata6.00: supports DRM functions and may not be fully accessible
+0.004408] ata6.00: configured for UDMA/133
+0.000175] sd 5:0:0:0: [sdb] Starting disk
+1.873127] r8169 0000:07:00.0 enp7s0: link up
+4.997502] mpt2sas0: port enable: SUCCESS
+0.000181] mpt2sas0: search for end-devices: start
+0.000001] mpt2sas0: search for end-devices: complete
+0.000001] mpt2sas0: search for raid volumes: start
+0.000001] mpt2sas0: search for responding raid volumes: complete
+0.000001] mpt2sas0: search for expanders: start
+0.000000] mpt2sas0: search for expanders: complete
+0.000001] mpt2sas0: search for end-devices: start
+0.000000] mpt2sas0: search for end-devices: complete
+0.000001] mpt2sas0: search for raid volumes: start
+0.000001] mpt2sas0: search for responding raid volumes: complete
+0.000000] mpt2sas0: search for expanders: start
+0.000001] mpt2sas0: search for expanders: complete
+0.000098] mpt2sas0: removing unresponding devices: start
+0.000001] mpt2sas0: removing unresponding devices: end-devices
+0.000001] mpt2sas0: removing unresponding devices: volumes
+0.000000] mpt2sas0: removing unresponding devices: expanders
+0.000001] mpt2sas0: removing unresponding devices: complete
+0.000001] mpt2sas0: scan devices: start
+0.000224] mpt2sas0: scan devices: expanders start
+0.000100] PM: resume of devices complete after 7799.376 msecs
+0.000086] mpt2sas0: scan devices: expanders complete
+0.000001] mpt2sas0: scan devices phys disk start
+0.000110] mpt2sas0: scan devices: phys disk complete
+0.000001] mpt2sas0: scan devices: volumes start
+0.000068] mpt2sas0: scan devices: volumes complete
+0.000001] mpt2sas0: scan devices: end devices start
+0.000125] PM: Finishing wakeup.
Multiple retries have the same result (it’s lucky that it doesn’t lock me out after three tries), so I don’t think it’s missing the first character. I’ll certainly try typing an extra next time.
My desktop is unmodified KDE, up to date per the Online Update, overlaid with packman (which shouldn’t affect KDE, but might).
Curiously, the problem did not occur this morning, when I had to unplug and replug my USB connections because the hub in the monitor turned off, and I used the power switch instead of the keyboard to reboot. Still, if the problem were something in the USB, that wouldn’t explain why I can log in as another user, or even why I can log in as myself if I merely switch to another user’s login screen.
Do you know which package actually includes the login screen? Perhaps I could try re-installing or reverting it.
More test results: it appears that unplugging the USB mouse/keyboard cable from the computer and plugging it back it fixes the problem, but forces me to use the power switch to bring the system up as the keyboard does not work after that manipulation until the computer is awakened.
Using the front-panel power switch without unplugging the USB cable does not work.
Pressing Backspace before entering my password doesn’t work.
Prefixing my password with a random character doesn’t work.
Switching to a new session and switching back without logging in doesn’t work.
The only things that work:
Switching to an active session, not logging in, and switching back.
Switching to a new session, logging in, and switching back.
Unplugging and replugging the USB cable and then pressing the power switch to awaken.
On Fri, 02 Jan 2015 16:56:02 +0000, freefiber wrote:
> More test results: it appears that unplugging the USB mouse/keyboard
> cable from the computer and plugging it back it fixes the problem, but
> forces me to use the power switch to bring the system up as the keyboard
> does not work after that manipulation until the computer is awakened.
>
> Using the front-panel power switch without unplugging the USB cable does
> not work.
>
> Pressing Backspace before entering my password doesn’t work.
>
> Prefixing my password with a random character doesn’t work.
>
> Switching to a new session and switching back without logging in doesn’t
> work.
>
>
> The only things that work:
>
> 1. Switching to an active session, not logging in, and switching back.
> 2. Switching to a new session, logging in, and switching back.
> 3. Unplugging and replugging the USB cable and then pressing the power
> switch to awaken.
It might be interesting to try initiating a switch user before putting it
to sleep, and then typing in a text field where you can see what’s being
typed to see if, for example, a shift key or the caps-lock key is toggled
when it resumes.
On 2015-01-02 17:56, freefiber wrote:
>
> More test results: it appears that unplugging the USB mouse/keyboard
> cable from the computer and plugging it back it fixes the problem, but
> forces me to use the power switch to bring the system up as the keyboard
> does not work after that manipulation until the computer is awakened.
Means that the thing knows it has to leave the keyboard powered up, so
that you can return by using it. But the screensaver (I guess it is that
one) doesn’t properly initialize it, and some other software (login to
another session) does.
You could try switching to text mode (ctrl-alt-f1), find out if the
keyboard works right, then back (ctrl-alt-f7).
The program that handles the normal login is typically kdm in a kde
setup, and gdm in a gnome setup. But there are others, like lightdm
which is typically used with xfce. But you should be able to use any one
with any desktop.
However, I’m unsure that’s the login prompt you see; it should be the
one from the screen saver.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I was able to switch to text mode (ctrl-alt-F1) and found that all of the character were shifted: Typing “abc123” gave me “ABC!@#”, and that no combination of shift keys or the numeric keypad would let me type numerals, though I could type lower case letters with Shift or Caps Lock.
So it seems like there’s an issue with my wonderful, old IBM keyboard and it’s PS/2 to USB converter. The easiest fix, it seems, is to plug the PS/2 connector directly into my computer, and use the power button on the front panel to awaken the computer.
On 2015-01-03 07:26, freefiber wrote:
>
> I was able to switch to text mode (ctrl-alt-F1) and found that all of
> the character were shifted: Typing “abc123” gave me “ABC!@#”, and that
> no combination of shift keys or the numeric keypad would let me type
> numerals, though I could type lower case letters with Shift or Caps
> Lock.
Wow!
Curious…
> So it seems like there’s an issue with my wonderful, old IBM keyboard
> and it’s PS/2 to USB converter. The easiest fix, it seems, is to plug
> the PS/2 connector directly into my computer, and use the power button
> on the front panel to awaken the computer.
>
> Thanks.
Welcome
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
… try pressing the caps lock 3 times, if that does not work, try pressing it once more and trying again.
If that does not work, try plugging the keyboard into a different USB port, and if still not, yet another port. (This I have seen to make a difference with some keyboards on certain machines.)
Just grabbing at straws, but one of those two things might work.
