Sudo password not updated

System:
Kernel: 5.16.4-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f1250705-50f0-494d-af74-04602be03ceb rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=4be56dd4-ede9-43d7-b8ee-2e20c33d086d loglevel=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX Z370-E GAMING v: Rev X.0x
serial: UEFI-[Legacy]: American Megatrends v: 0408
date: 08/31/2017
CPU:
Info: model: Intel Core i7-8700K bits: 64 type: MT MCP arch: Coffee Lake
family: 6 model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xEA
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 4701 high: 4704 min/max: 800/4700 scaling:
driver: intel_pstate governor: performance cores: 1: 4702 2: 4703 3: 4700
4: 4702 5: 4701 6: 4701 7: 4703 8: 4700 9: 4704 10: 4701 11: 4701
12: 4700 bogomips: 88796
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
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
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: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: Gigabyte
driver: nvidia v: 510.47.03 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
chip-ID: 10de:1b06 class-ID: 0300
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3440x2208 s-dpi: 107 s-size: 817x524mm (32.2x20.6")
s-diag: 971mm (38.2")
Monitor-1: HDMI-1 res: 1366x768 hz: 60 dpi: 158
size: 220x132mm (8.7x5.2") diag: 257mm (10.1")
Monitor-2: DP-2 res: 3440x1440 dpi: 109 size: 798x335mm (31.4x13.2")
diag: 865mm (34.1")
OpenGL: renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
v: 4.6.0 NVIDIA 510.47.03 direct render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
class-ID: 0403
Device-2: NVIDIA GP102 HDMI Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel bus-ID: 01:00.1 chip-ID: 10de:10ef class-ID: 0403
Device-3: Creative Sound BlasterX G1 type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-13.1:7
chip-ID: 041e:3249 class-ID: 0300 serial:
Device-4: Kingston HyperX 7.1 Audio type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-13.3:9
chip-ID: 0951:16a4 class-ID: 0300 serial:
Sound Server-1: ALSA v: k5.16.4-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.44 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac:
Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: ASUSTeK
driver: rtw_8822be v: N/A modules: rtw88_8822be port: d000 bus-ID: 04:00.0
chip-ID: 10ec:b822 class-ID: 0280
IF: wlp4s0 state: down mac:
IF-ID-1: anbox0 state: down mac:
Bluetooth:
Device-1: ASUSTek Bluetooth Radio type: USB driver: btusb v: 0.8
bus-ID: 1-7:3 chip-ID: 0b05:185c class-ID: e001 serial:
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address:
Drives:
Local Storage: total: 939.14 GiB used: 289.61 GiB (30.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial:
rev: 2B2QEXM7 temp: 46.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: rev: 1B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: rev: 2B6Q scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: SMI (STMicroelectronics)
model: USB DISK size: 7.61 GiB block-size: physical: 512 B logical: 512 B
type: N/A serial: rev: 1100 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 431.35 GiB size: 431.35 GiB (100.00%)
used: 289.61 GiB (67.1%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-2: /home raw-size: 431.35 GiB size: 431.35 GiB (100.00%)
used: 289.61 GiB (67.1%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /var/log raw-size: 431.35 GiB size: 431.35 GiB (100.00%)
used: 289.61 GiB (67.1%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw-size: 431.35 GiB size: 431.35 GiB (100.00%)
used: 289.61 GiB (67.1%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 34.4 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: swap-2 type: zram size: 31.28 GiB used: 2.2 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 47 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 314 Uptime: 15m wakeups: 0 Memory: 31.28 GiB
used: 4.04 GiB (12.9%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 Packages: pacman: 1834 lib: 536 Shell: fish v: 3.3.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.12
Garuda (2.5.4-1):
System install date: 2022-02-02
Last full system update: 2022-02-03
Is partially upgraded: No
Relevant software: NetworkManager
Windows dual boot:
Snapshots: Snapper
Failed units:

So i login in my machine, i change password with passwd or the garuda settings manager, and after that everything constantly says i have the password wrong, i cant add an user cause it also freezes.

Basicly im stuck with a weird bug that allows me to login but doesnt allow me to do anything else.

What happens if you revert your password to the original one? Have you tried creating a new user? If so, what were the results? Are you a member of the 'wheel' group?

Perhaps using su might give different results?

2 Likes

I could be mistaken, but didn't we get some account related updates recently? (Forgot when the sudo update hit too). Try to update , then restart and try again.

1 Like

Press CTRL+ALT+F3

Try logging in on the root account, then:

pacman -Syyuu

That command is not for general use, but is reserverved for rare occasions. Best not to use it unless you have been requested to do so.

Hopefully after updating, your issue may be corrected. If not then more complicated measures must be taken.

5 Likes

It hangs when i try to create a new user and i also cant update cause it doesnt allow me since i dont have correct "sudo" password

Why don't you try using a live USB, use chroot functionality in the Garuda Welcome, so you will be root in your installed system, then you might be able to update, and maybe you could also use it to change password to both root (passwd) and your user (passwd <username>).

5 Likes

Considering your last update time, it might have to do with this?

Doing what @filo said should fix your issue .

5 Likes

We know that. Read again.

This means that you go to TTY3, where you are asked to login. For user name enter root and for password enter the root password you selected when installing the system (if you chose to have the same password as your 1st normal user, it should be the same).

OTOH, the system does what it is told to. If you haven't changed your password, then maybe you changed keyboard layout. What have you changed just before this happen?
If a package update is supposed to produce this problem, then every Archlinux user should have the same issue. You have probably, either forgot your password, or your keyboard has a broken key, or you changed keyboard layout configuration.

3 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.