I recently updated an installation of Manjaro XFCE and switched to the 5.5 kernel. Now, after a suspend, it asks for a password twice before letting me in. Any suggestions? Thanks in advance!
Are any (display manager related) problems/errors visible in logs?
other than a whole bunch of errors from the discord application, this is what journalctl said:
Jan 25 22:21:13 thinkcentre dbus-daemon: [session uid=1000 pid=970] Successfully activated service 'org.gnome.GConf' Jan 26 23:22:52 thinkcentre pulseaudio: W: [alsa-sink-ALC662 rev3 Analog] alsa-util.c: Could not recover alsa device from SUSPENDED sta> Jan 26 23:23:10 thinkcentre systemd: run-user-970-gvfs.mount: Succeeded.
dmesg: read kernel buffer failed: Operation not permitted
and here's system info:
System: Kernel: 5.5.2-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.5-x86_64 root=UUID=22d180c5-6363-4b1a-b6c7-71db1093e85e rw quiet apparmor=1 security=apparmor resume=UUID=fb8e7462-b6cd-42fa-89dc-002ce33e9c8e udev.log_priority=3 Desktop: Xfce 4.14.2 tk: Gtk 3.24.13 info: xfce4-panel wm: xfwm4 dm: LightDM 1.30.0 Distro: Manjaro Linux Machine: Type: Desktop System: LENOVO product: 10A90014US v: ThinkCentre M93p serial: <filter> Mobo: LENOVO model: SHARKBAY v: 0B98401 PRO serial: <filter> BIOS: LENOVO v: FBKT56AUS date: 11/18/2013 CPU: Topology: Quad Core model: Intel Core i7-4770 bits: 64 type: MT MCP arch: Haswell family: 6 model-id: 3C (60) stepping: 3 microcode: 27 L2 cache: 8192 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54303 Speed: 1397 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 1354 2: 1309 3: 1298 4: 1337 5: 1299 6: 1301 7: 1310 8: 1301 Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds mitigation: Clear CPU buffers; SMT vulnerable Type: meltdown mitigation: PTI Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412 Display: x11 server: X.Org 1.20.7 driver: intel unloaded: modesetting alternate: fbdev,vesa resolution: 1440x900~60Hz, 1440x900~60Hz, 1440x900~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.3.4 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 Device-3: Logitech H600 [Wireless Headset] type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 2-5:6 chip ID: 046d:0a29 serial: <filter> Sound Server: ALSA v: k5.5.2-1-MANJARO Network: Device-1: Intel Ethernet I217-LM vendor: Lenovo driver: e1000e v: 3.2.6-k port: f080 bus ID: 00:19.0 chip ID: 8086:153a IF: eno1 state: down mac: <filter> Device-2: Intel Centrino Wireless-N 105 driver: iwlwifi v: kernel port: 0580 bus ID: 02:00.0 chip ID: 8086:0895 IF: wlp2s0 state: up mac: <filter> Drives: Local Storage: total: 1.42 TiB used: 520.29 GiB (35.7%) ID-1: /dev/sda vendor: Western Digital model: WD15EARS-00Z5B1 size: 1.36 TiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 0A80 scheme: MBR ID-2: /dev/sdb model: Industrial SSD size: 59.00 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 0A scheme: MBR Partition: ID-1: / raw size: 57.04 GiB size: 55.89 GiB (97.99%) used: 26.98 GiB (48.3%) fs: ext4 dev: /dev/sdb1 ID-2: /home raw size: 1.33 TiB size: 1.31 TiB (98.36%) used: 493.30 GiB (36.7%) fs: ext4 dev: /dev/sda2 ID-3: swap-1 size: 32.23 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default) cache pressure: 100 (default) dev: /dev/sda1 Sensors: System Temperatures: cpu: 34.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 330 Uptime: 23h 28m Memory: 15.32 GiB used: 4.72 GiB (30.8%) Init: systemd v: 242 Compilers: gcc: 9.2.0 clang: 9.0.1 Shell: bash v: 5.0.11 running in: xfce4-terminal inxi: 3.0.37
Jan 26 23:22:52 from the first (failing?) try and
Jan 26 23:23:10 from the second?
sudo for that
dmesg call. Alternativly you can use
journalctl -k without
sudo if you're a member of
Seen this happen before: You're asked for your screen saver and your login password. Turn off your screen saver password or uninstall it altogether and slam the lid shut whenever you don't want
the kids seeing you surf pr0n anyone to use your computer when you're away.
I didn't think I had a screensaver installed, but I tried going into power manager and setting "Automatically lock the session" to "never", and that seemed to work. Thanks for that idea! I wonder what part of the update caused that
Finding out which update caused that is going to take a few hours of investigation.
As Ian Fleming famously said. “Once is happenstance. Twice is coincidence. Thrice is enemy action”.
Only when you have enemy action you dig in and
defend yourself investigate.
interestingly enough, it just happened again ;-;
appears to be intermittent
Did the screen saver turn itself on again?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.