Cannot log in, cannot do updates

I have solved many issues but 2 have me stumped:

  1. During installation I opted for the same password for me and root and for autologin. It takes 7 minutes to boot and eventually shows the login screen. I can login as root but not as myself. It does not say “Invalid password” it bounces back to the terminal and back to the login screen. I created a new user with the same password and this works fine, surprisingly I did this from the guest account! The guest account also works with the same password. I have used the User S/w to change the password but stll cannot login and there is no option to delete the account.How can I delete the faulty account? How can I get autologin to work?
  2. I have 95 updates pending but when I try to install as root or guest or as my new user I get the message “failed to run transaction hooks”.

I would like to test this interesting distro further but these 2 bugs are preventing me from continuing. Also I need to investigate the 7 minute bootup

Give us output of

inxi -Fxxxza


systemd-analyze blame

Also which edition are you using ?

Guest account does not require password for login.

1 Like

Please post in and output from

passwd -S
cat /etc/passwd
man passwd

passwd -S

-S, --status
Displays information about the account status. The status information consists of seven fields. The first field
is the login name of the user. The second field indicates whether the user account has a locked password
(L), no password (NP) or has a usable password §. The third field shows the date of the last
Change password. The next four fields are the minimum age, the maximum age, the duration of
Warning and the duration of inactivity for the password. The periods are expressed in days.

I think it is a corrupt installation or you copied something from another distribution into the ~/ folder.
Some DE use UID 1000 Garuda use 1001
and for Guest UID 1001 Garuda use 1000

After installing Garuda or in your previous life :wink: ?

Best would be to download the ISO again and reinstall it.

@librewish Garuda does seem to have some kind of issue with passwords Last night for the second time My password would not be excepted till I did a reboot. First time was the previous install along side Manjaro, and last night with this install having the entire drive.

4:54:16  [email protected]  ~ 
$ inxi -Fxxxza
System:    Kernel: 5.8.3-zen1-1-zen x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen 
           root=UUID=70792e81-488b-45ca-9bfb-794308996c9f rw [email protected] quiet 
           splash loglevel=3 
           Desktop: KDE Plasma 5.19.4 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM 
           Distro: Garuda Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx 
           serial: <filter> UEFI: American Megatrends v: 3103 date: 06/17/2020 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360 
           serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
           status: Discharging 
CPU:       Info: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 
           type: MCP arch: Zen+ family: 17 (23) model-id: 18 (24) stepping: 1 
           microcode: 8108109 L2 cache: 2048 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 28744 
           Speed: 3331 MHz min/max: 1400/3600 MHz boost: enabled Core speeds (MHz): 
           1: 3102 2: 2690 3: 2755 4: 2766 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           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 AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] vendor: 
           driver: nvidia v: 450.66 alternate: nouveau,nvidia_drm bus ID: 01:00.0 
           chip ID: 10de:2187 
           Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 driver: nvidia 
           display ID: :0 screens: 1 
           Screen-1: 0 s-res: 2560x1080 s-dpi: 97 s-size: 670x283mm (26.4x11.1") 
           s-diag: 727mm (28.6") 
           Monitor-1: HDMI-0 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2") 
           diag: 730mm (28.8") 
           OpenGL: renderer: GeForce GTX 1650 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 450.66 
           direct render: Yes 
Audio:     Device-1: NVIDIA TU116 High Definition Audio vendor: 
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:1aeb 
           Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 0a:00.6 chip ID: 1022:15e3 
           Sound Server: ALSA v: k5.8.3-zen1-1-zen 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k 
           port: d000 bus ID: 04:00.0 chip ID: 8086:1539 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 9.21 TiB used: 3.67 TiB (39.8%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 model: Viper M.2 VPN100 size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: ECFM22.6 scheme: GPT 
           ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 120GB size: 111.79 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 2B6Q scheme: GPT 
           ID-3: /dev/sdb vendor: Western Digital model: WD10EARS-00Y5B1 size: 931.51 GiB 
           block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> 
           rev: 0A80 scheme: GPT 
           ID-4: /dev/sdc vendor: Samsung model: ST3000DM001-1E6166 size: 2.73 TiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: SC48 scheme: GPT 
           ID-5: /dev/sdd type: USB vendor: Samsung model: Seagate Expansion 
           size: 1.82 TiB block size: physical: 4096 B logical: 512 B serial: <filter> 
           rev: 9300 scheme: GPT 
           ID-6: /dev/sde type: USB vendor: MediaMax model: WL3000GSA6454 size: 3.41 TiB 
           block size: physical: 4096 B logical: 512 B rotation: 5400 rpm serial: <filter> 
           scheme: GPT 
Partition: ID-1: / raw size: 238.17 GiB size: 238.17 GiB (100.00%) used: 28.62 GiB (12.0%) 
           fs: btrfs dev: /dev/nvme0n1p2 
           ID-2: /home raw size: 238.17 GiB size: 238.17 GiB (100.00%) 
           used: 28.62 GiB (12.0%) fs: btrfs dev: /dev/nvme0n1p2 
Swap:      Kernel: swappiness: 5 (default 60) cache pressure: 50 (default 100) 
           ID-1: swap-1 type: zram size: 496.7 MiB used: 2.0 MiB (0.4%) priority: 32767 
           dev: /dev/zram0 
           ID-2: swap-2 type: zram size: 496.7 MiB used: 2.0 MiB (0.4%) priority: 32767 
           dev: /dev/zram1 
           ID-3: swap-3 type: zram size: 496.7 MiB used: 1.8 MiB (0.4%) priority: 32767 
           dev: /dev/zram2 
           ID-4: swap-4 type: zram size: 496.7 MiB used: 1.8 MiB (0.4%) priority: 32767 
           dev: /dev/zram3 
Sensors:   System Temperatures: cpu: 44.1 C mobo: N/A gpu: nvidia temp: 45 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:      Processes: 320 Uptime: 12h 31m Memory: 7.76 GiB used: 3.20 GiB (41.3%) 
           Init: systemd v: 246 Compilers: gcc: 10.2.0 clang: 10.0.1 Packages: 2009 
           pacman: 1987 lib: 556 flatpak: 22 snap: 0 Shell: Zsh v: 5.8 running in: konsole 
           inxi: 3.1.06 

 04:55:44  [email protected]  ~ 
$ systemd-analyze blame
14.568s man-db.service                                                                       >
 3.605s NetworkManager-wait-online.service                                                   >
 2.617s systemd-swap.service                                                                 >
 1.321s lvm2-monitor.service                                                                 >
 1.089s evdev-rce.service                                                                    >
  852ms dev-nvme0n1p2.device                                                                 >
  679ms upower.service                                                                       >
  676ms systemd-logind.service                                                               >
  672ms systemd-machined.service                                                             >
  530ms udisks2.service                                                                      >
  477ms vboxweb.service                                                                      >
  442ms [email protected]                                                     >
  348ms ananicy.service                                                                      >
  310ms systemd-udevd.service                                                                >
  308ms snapd.service                                                                        >
  307ms systemd-journald.service                                                             >
  242ms systemd-timesyncd.service                                                            >
  228ms [email protected]                                                     >
  225ms ModemManager.service                                                                 >
  215ms mnt-Music.mount                                                                      >
  212ms [email protected]                                                     >
  200ms ldconfig.service                                                                     >
  199ms mnt-Movies.mount                                                                     >
  198ms systemd-remount-fs.service                                                           >
  196ms NetworkManager.service                                                               >
  195ms mnt-Movies\x202.mount                                                                >
  191ms mnt-Music\x20Videos.mount                                                            >
  184ms [email protected]
$ passwd -S
alienprober P 08/22/2020 0 99999 7 -1

 04:59:07  [email protected]  ~ 
$ cat /etc/passwd
dbus:x:81:81:System Message Bus:/:/usr/bin/nologin
systemd-journal-remote:x:982:982:systemd Journal Remote:/:/usr/bin/nologin
systemd-network:x:981:981:systemd Network Management:/:/usr/bin/nologin
systemd-resolve:x:980:980:systemd Resolver:/:/usr/bin/nologin
systemd-timesync:x:979:979:systemd Time Synchronization:/:/usr/bin/nologin
systemd-coredump:x:978:978:systemd Core Dumper:/:/usr/bin/nologin
git:x:977:977:git daemon user:/:/usr/bin/git-shell
avahi:x:970:970:Avahi mDNS/DNS-SD daemon:/:/usr/bin/nologin
named:x:40:40:BIND DNS Server:/:/usr/bin/nologin
colord:x:969:969:Color management daemon:/var/lib/colord:/usr/bin/nologin
cups:x:209:209:cups helper user:/:/usr/bin/nologin
dnsmasq:x:968:968:dnsmasq daemon:/:/usr/bin/nologin
flatpak:x:967:967:Flatpak system helper:/:/usr/bin/nologin
geoclue:x:966:966:Geoinformation service:/var/lib/geoclue:/usr/bin/nologin
murmur:x:122:122:Murmur User:/var/db/murmur:/usr/bin/nologin
nm-openconnect:x:964:964:NetworkManager OpenConnect:/:/usr/bin/nologin
nm-openvpn:x:963:963:NetworkManager OpenVPN:/:/usr/bin/nologin
ntp:x:87:87:Network Time Protocol:/var/lib/ntp:/bin/false
nvidia-persistenced:x:143:143:NVIDIA Persistence Daemon:/:/usr/bin/nologin
ldap:x:439:439:LDAP Server:/var/lib/openldap:/usr/bin/nologin
polkitd:x:102:102:PolicyKit daemon:/:/usr/bin/nologin
sddm:x:962:962:Simple Desktop Display Manager:/var/lib/sddm:/usr/bin/nologin
tss:x:961:961:tss user for tpm2:/:/usr/bin/nologin
usbmux:x:140:140:usbmux user:/:/usr/bin/nologin
ice:x:101:101:Ice User:/var/lib/ice:/usr/bin/nologin

check if you got hit by this bug

1 Like

Must be 1001:1001
Guest must be 1000:1000
or ???

I never have this, only if you try convert a other DE to Garuda.

I don’t even have any idea what that is, much less know how to change it. Must of been changed somehow when I removed the Guest, but then again in the other install I hadn’t touched guest. I can tell you it refused to remove the Guest 2 times before it finally did remove it. As for trying to convert another distro to Garuda, simply no. This ISO for this and the last install was straight from you’re home page.

That could be the case for both of us. Before wiping this drive Manjaro had just done a good size update that include updates for that “pam” and they posted a pretty strong warning about possible bugs.

I can see now that other users have had problems when installing alongside other distros. I did this and elected not to install grub. I used my other distro to run update-grub. This did not find Garuda so I had to modify the Garuda file system to remove the ‘@’ from the folder names. This enabled me to boot into Garuda but I had the root partition with a home folder containg Guest plus a complete copy of the root partition including another home folder. My users were in /home/guest and /home/home/michael. The new user I created was in /home. This explains why michael would not load and probably explains a myriad other problems I was hoping to solve. I will re-install and give it a fair go. Thanks for all your replies and congrats on a very interesting distro.

So you modified btrfs subvolume layout

Timeshit needs @ and @home subvolume layout
To make snapshots

So you basically changed this

So the transaction hooks wont work
As timeshift fails because you changed subvolume layout

So what you need to do is
Now either restore the layout to @ and @home or

sudo pacman -R timeshift-autosnap

1 Like

Just a question here - why is that? Is there some advantage to it being contrary to most distros defaults? I’ve certainly run into a few disadvantages… :grin:

Well thats because of systemd-guest-user

Yeah - I know how it got that way, but still wondering about an advantage? After all, if the useradd includes -mu 1002, then uid 1000 is still there for the new system ‘owner’. Which saves a LOT of trouble for interacting with other distros and resources…

1 Like

Please explain what you think actually happened since I did not convert another DE to Garuda. and how to correct it and get rid of Guess once and for all. Was not amused to see a guess account I did not create, was not amused to find this Guess account cannot be deleted, which is probably what changed the above. 3 attempts to remove it, get told it’s gone, only to find during a logoff that it’s still there. Might want to split these off to anew thread. Thanks

sudo pacman -R systemd-guest-user

1 Like

Thanks for that, but still does not explain why when going to users under system settings it will not remove.

Sorry, I’m just trying something out but it didn’t work, now everything should be back to the way it was before. :slight_smile:

1 Like

Because its a systemd service

And the guest user gets created at startup and deleted at shutdown