Can not login to personal user, but as root

Support
,
1

Continuing the discussion from Can log in only as root, even with a fresh user:

my situation is similar to this linked Topic. I am on xfce4 though.

I …

  • can not login (password not accepted) with any user, but
  • can login as root (with gui) since just 30 minutes ago.

The last successful login happened yesterday. After that I might have installed oh-my-bash on one of the user’s accounts (not 100% sure whether that was before or after that successful reboot though).

I …

  • set password(s) of personal users successfully.
  • created new personal users with useradd (none of these existing, nor new user accounts can login (password not accepted))
  • can do su [username] in the terminal (not being prompted for the users password)
  • can do (as personal user) sudo ls -l /root. The users password is accepted in that situation
  • can not run podman ps as personal user (RunRoot is pointing to a path (/run/user/1000/containers) which is not writable. Most likely podman will fail.), but
  • can do sudo podman ps without any problem as personal user
  • can not start any multimedia applications (vlc, clementine). It seems they are complaining about pusleaudio

I have not tried yet …

  • … to allow passwordless login (because I do not know how)
  • … login directly into a tty session as a personal user. There is a button at the lightdm (I assume that is what I m loggin in to) login which let’s you choose the session type, but that only offers xfce as an option.

any ideas how to get over this?

ADDITION:

trying to run some applications as personal user, starting them from the bash I tend to see errors like …

  • Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
  • [14864:1004/104246.809822:ERROR:ozone_platform_x11.cc(240)] Missing X server or $DISPLAY

and in fact the personal users have nothing in the DISPLAY environment variable.
Would it be an idea trying to get in there what root has (:0.0)? If so,how do I do that?

2

Hi @vrms,

Not really, no. However, it does sound to me that login as your user is just disallowed for some reason. So let’s see if we can see anything. Please provide the output of:

cat /etc/passwd

…I’m guessing it will be as your root user, since that seems to be all you can use at the moment.

Have you made sure that your drives are working and that it didn’t fail mid-use, removing a partition from the mounts?

3

no nologin entries in passwd where they do not belong (I guess that is what you are up for)

also my mounts seem to be as they should

manolo@manj-laptop ~ → for i in $(cat /etc/fstab | tail -n +10 | awk {'print $2'} | sed '/^ *$/d' | sed "s# / ##") ; do mount | grep $i ; done

/dev/sda1 on /home type btrfs (rw,noatime,compress=zstd:3,ssd,space_cache,user_subvol_rm_allowed,commit=120,subvolid=257,subvol=/@home)
/dev/sda1 on /btrfs type btrfs (rw,noatime,compress=zstd:3,ssd,space_cache,user_subvol_rm_allowed,commit=120,subvolid=5,subvol=/)
/dev/sda1 on /var/lib/docker/btrfs type btrfs (rw,noatime,compress=zstd:3,ssd,space_cache,user_subvol_rm_allowed,commit=120,subvolid=256,subvol=/@)
/dev/sda1 on /.snapshots type btrfs (rw,noatime,compress=zstd:3,ssd,space_cache,user_subvol_rm_allowed,commit=120,subvolid=269,subvol=/@snapshots)
tmpfs on /tmp type tmpfs (rw,noatime,inode64)
/dev/sda3 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /var/lib/lxd/shmounts type tmpfs (rw,relatime,size=100k,mode=711,inode64)
4

So you installed this?

If that’s the case, taking a quick look there’s no easy way to tell what the installer does via curl. But it’s looking like it modifies your .bashrc. Try removing/replacing with the Manjaro default.

5
  1. I can not really say whether I rebooted afterwards already sucessful
  2. yes, it does some stuff to .dot files in the ~ directory of the user, setting up a ton of .bashrc stuff
  3. this would not explain the same behavior for other users
6

I am adding some more findings to the original post

7

Your new findings make it look or sound like you don’t have X installed, yet root seems to be working, which it wouldn’t is X was missing…so this maked me think it’s a permissioning error, or something…

Just for giggle, let’s see if there are any disk-related errors. In a terminal, run:

sudo smartctl --all /dev/sda

…and provide the output…

I’m not :100: on this, but it might also help to resync the system…at least it shouldn’t do any harm…

pamac upgrade

But first! Try seeing if there’s anything in the logs when you run this in the terminal directly after a failed login attempt:

journalctl --boot=0 --priority=warning..err --no-pager

Where:

  • --boot=0 limits the messages to the current boot;
  • --priority=warning..err limits the messages to be warnings and errors only; and
  • --no-pager formats the output nicely for use here, on thew forum.

Please provide that output here for us. Maybe it’s something small, but we wouldn’t know.

Because, something is seriously wrong here, and I have no idea what it could be…

8

looks harmless to me

[manj-laptop ~]# smartctl --all /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.53-1-MANJARO] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Marvell based SanDisk SSDs
Device Model:     SanDisk SDSSDH3500G
Serial Number:    184411421293
LU WWN Device Id: 5 001b44 4a9220726
Firmware Version: X61170RL
User Capacity:    500.107.862.016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Oct  4 11:19:23 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x11) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  10) minutes.

SMART Attributes Data Structure revision number: 4
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0032   100   100   ---    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   ---    Old_age   Always       -       12375
 12 Power_Cycle_Count       0x0032   100   100   ---    Old_age   Always       -       1640
165 Total_Write/Erase_Count 0x0032   100   100   ---    Old_age   Always       -       6133929355216
166 Min_W/E_Cycle           0x0032   100   100   ---    Old_age   Always       -       72
167 Min_Bad_Block/Die       0x0032   100   100   ---    Old_age   Always       -       54
168 Maximum_Erase_Cycle     0x0032   100   100   ---    Old_age   Always       -       143
169 Total_Bad_Block         0x0032   100   100   ---    Old_age   Always       -       512
170 Unknown_Marvell_Attr    0x0032   100   100   ---    Old_age   Always       -       0
171 Program_Fail_Count      0x0032   100   100   ---    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   100   100   ---    Old_age   Always       -       0
173 Avg_Write/Erase_Count   0x0032   100   100   ---    Old_age   Always       -       104
174 Unexpect_Power_Loss_Ct  0x0032   100   100   ---    Old_age   Always       -       123
184 End-to-End_Error        0x0032   100   100   ---    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   ---    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   ---    Old_age   Always       -       7
194 Temperature_Celsius     0x0022   073   060   ---    Old_age   Always       -       27 (Min/Max 8/60)
199 SATA_CRC_Error          0x0032   100   100   ---    Old_age   Always       -       0
230 Perc_Write/Erase_Count  0x0032   100   100   ---    Old_age   Always       -       5158 2600 5158
232 Perc_Avail_Resrvd_Space 0x0033   100   100   004    Pre-fail  Always       -       100
233 Total_NAND_Writes_GiB   0x0032   100   100   ---    Old_age   Always       -       51962
234 Perc_Write/Erase_Ct_BC  0x0032   100   100   ---    Old_age   Always       -       123631
241 Total_Writes_GiB        0x0030   253   253   ---    Old_age   Offline      -       67450
242 Total_Reads_GiB         0x0030   253   253   ---    Old_age   Offline      -       45872
244 Thermal_Throttle        0x0032   000   100   ---    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

The above only provides legacy SMART information - try 'smartctl -x' for more

that would be …

  1. log out of root, try login in as myself (and fail)
  2. login again as root and then (45 sec later)
  3. run journalctl --boot=0 --priority=warning..err --no-pager

that’s what you mean, correct? I gotta walk my dogs for a second not though … and will do that once I come back

9

Correct, yes.

Say hi to your dogs for me!

10

the relevant output from that seems to be

...
Okt 04 11:17:48 manj-laptop kernel: BTRFS warning (device sda1): qgroup rescan init failed, qgroup is not enabled
...
Okt 04 13:22:17 manj-laptop lightdm[23399]: gkr-pam: unable to locate daemon control file
Okt 04 13:22:32 manj-laptop lightdm[23415]: gkr-pam: unable to locate daemon control file
Okt 04 13:25:15 manj-laptop systemd[7695]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Okt 04 13:25:24 manj-laptop lightdm[23676]: gkr-pam: unable to locate daemon control file
Okt 04 13:25:37 manj-laptop lightdm[23691]: gkr-pam: unable to locate daemon control file
Okt 04 13:25:38 manj-laptop tumblerd[23816]: Failed to load plugin "tumbler-gepub-thumbnailer.so": libgepub-0.7.so.0: cannot open shared object file: No such file or directory

so I guess the so-called daemon control file gkr-pam is looking for mught be the intial culprid. Any suggestion, how to fix this?

I\ll start studying those for a start

11

These messages seem to be harmless:

Regardine this: :point_down:

It’s filesystem-related, although I know nothing about BTRFS, I use ext4 and I’m quite happy with it.

All I can do is point you here:

https://unix.stackexchange.com/questions/641173/btrfs-qgroups-warning-error

I’m thinking this :point_down:

…is because Gnome can’t start.

Please,

Don’t cut things out, as requested here:

Please provide the complete output.

We need to see what’s causing the problem, so it might not be in thee logs you provided, seeing as those errors only look like symptoms of the problem, not the problem itself.

12

I see, here you go:

Okt 04 09:34:25 manj-laptop kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Okt 04 09:34:25 manj-laptop kernel:  #3
Okt 04 09:34:25 manj-laptop kernel: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
Okt 04 09:34:25 manj-laptop kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Okt 04 09:34:25 manj-laptop kernel: i8042: Warning: Keylock active
Okt 04 09:34:25 manj-laptop kernel: v4l2loopback: loading out-of-tree module taints kernel.
Okt 04 09:34:25 manj-laptop kernel: BTRFS warning (device sda1: state M): remount supports changing free space tree only from ro to rw
Okt 04 09:34:25 manj-laptop kernel: kauditd_printk_skb: 4 callbacks suppressed
Okt 04 09:34:25 manj-laptop systemd-udevd[321]: /etc/udev/rules.d/40-libsane.rules:26 GOTO="libsane_rules_end" has no matching label, ignoring.
Okt 04 09:34:25 manj-laptop systemd-udevd[321]: /etc/udev/rules.d/S99-2000S1.rules:26 GOTO="libsane_rules_end" has no matching label, ignoring.
Okt 04 09:34:26 manj-laptop kernel: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
Okt 04 09:34:27 manj-laptop kernel: FAT-fs (sda3): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Okt 04 09:34:27 manj-laptop kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20220331/utaddress-204)
Okt 04 09:34:27 manj-laptop kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)
Okt 04 09:34:27 manj-laptop kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)
Okt 04 09:34:27 manj-laptop kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20220331/utaddress-204)
Okt 04 09:34:27 manj-laptop kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Okt 04 09:34:27 manj-laptop kernel: i801_smbus 0000:00:1f.3: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration
Okt 04 09:34:27 manj-laptop kernel: wl: module license 'MIXED/Proprietary' taints kernel.
Okt 04 09:34:27 manj-laptop kernel: Disabling lock debugging due to kernel taint
Okt 04 09:34:27 manj-laptop kernel: wlan0: Broadcom BCM4727 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
Okt 04 09:34:27 manj-laptop kernel: 
Okt 04 09:34:27 manj-laptop kernel: dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface not supported(0), try upgrading to a newer BIOS
Okt 04 09:34:28 manj-laptop kernel: at24 0-0050: supply vcc not found, using dummy regulator
Okt 04 09:34:29 manj-laptop NetworkManager[798]: <warn>  [1696404869.5561] platform-linux: do-change-link[2]: failure 23 (Too many open files in system) (assume success changing address)
Okt 04 09:34:30 manj-laptop (uetoothd)[1016]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Okt 04 09:34:30 manj-laptop NetworkManager[798]: <warn>  [1696404870.2087] platform-linux: do-change-link[2]: failure 23 (Too many open files in system) (assume success changing address)
Okt 04 09:34:30 manj-laptop NetworkManager[798]: <warn>  [1696404870.2098] device (wlp2s0): no secrets: No agents were available for this request.
Okt 04 09:34:30 manj-laptop NetworkManager[798]: <warn>  [1696404870.2103] device (wlp2s0): Activation: failed for connection 'helloThere'
Okt 04 09:34:30 manj-laptop NetworkManager[798]: <warn>  [1696404870.2126] platform-linux: do-change-link[2]: failure 23 (Too many open files in system) (assume success changing address)
Okt 04 09:34:30 manj-laptop bluetoothd[1016]: src/plugin.c:plugin_init() System does not support csip plugin
Okt 04 09:34:30 manj-laptop bluetoothd[1016]: src/plugin.c:plugin_init() System does not support vcp plugin
Okt 04 09:34:30 manj-laptop bluetoothd[1016]: src/plugin.c:plugin_init() System does not support mcp plugin
Okt 04 09:34:30 manj-laptop bluetoothd[1016]: src/plugin.c:plugin_init() System does not support bass plugin
Okt 04 09:34:30 manj-laptop bluetoothd[1016]: src/plugin.c:plugin_init() System does not support bap plugin
Okt 04 09:34:30 manj-laptop kernel: Bluetooth: hci0: BCM: firmware Patch file not found, tried:
Okt 04 09:34:30 manj-laptop kernel: Bluetooth: hci0: BCM: 'brcm/BCM20702A1-413c-8197.hcd'
Okt 04 09:34:30 manj-laptop kernel: Bluetooth: hci0: BCM: 'brcm/BCM-413c-8197.hcd'
Okt 04 09:34:30 manj-laptop dnsmasq[1077]: no servers found in /etc/resolv.conf, will retry
Okt 04 09:34:30 manj-laptop dnsmasq[1097]: warning: no upstream servers configured
Okt 04 09:34:30 manj-laptop libvirtd[903]: ignoring dangling symlink '/home/manolo/.steampath'
Okt 04 09:34:30 manj-laptop libvirtd[903]: cannot open directory '/home/manolo/LinuxPlayground/scripts': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: internal error: Failed to autostart storage pool 'scripts': cannot open directory '/home/manolo/LinuxPlayground/scripts': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: cannot open directory '/run/media/manolo/1TB/isos/pks_vm': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: internal error: Failed to autostart storage pool 'usb_drive': cannot open directory '/run/media/manolo/1TB/isos/pks_vm': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: cannot open directory '/run/media/manolo/1TB/isos': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: internal error: Failed to autostart storage pool 'isos-1': cannot open directory '/run/media/manolo/1TB/isos': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: cannot open directory '/home/manolo/temp': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: internal error: Failed to autostart storage pool 'temp': cannot open directory '/home/manolo/temp': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: cannot open directory '/home/manolo/Downloads/ERPnext vm': No such file or directory
Okt 04 09:34:30 manj-laptop libvirtd[903]: internal error: Failed to autostart storage pool 'ERPnext_vm': cannot open directory '/home/manolo/Downloads/ERPnext vm': No such file or directory
Okt 04 09:34:30 manj-laptop kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
Okt 04 09:34:30 manj-laptop libvirtd[903]: internal error: Too many snapshots claiming to be current for domain ws19core
Okt 04 09:34:30 manj-laptop libvirtd[903]: internal error: Too many snapshots claiming to be current for domain ws19core
Okt 04 09:34:36 manj-laptop kernel: kauditd_printk_skb: 57 callbacks suppressed
Okt 04 09:34:38 manj-laptop dnsmasq[1494]: no servers found in /etc/resolv.conf, will retry
Okt 04 09:34:39 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:39 manj-laptop lightdm[1182]: gkr-pam: unable to locate daemon control file
Okt 04 09:34:39 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:39 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:39 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:39 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:39 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:40 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:40 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:40 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:40 manj-laptop kernel: NOHZ tick-stop error: local softirq work is pending, handler #200!!!
Okt 04 09:34:46 manj-laptop kernel: kauditd_printk_skb: 27 callbacks suppressed
Okt 04 09:34:52 manj-laptop kernel: kauditd_printk_skb: 25 callbacks suppressed
Okt 04 09:35:04 manj-laptop lightdm[7678]: gkr-pam: unable to locate daemon control file
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: Configuration file /root/.config/autostart/xfce-panel-workaround.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: Configuration file /root/.config/autostart/xfce-pbw.sh is marked executable. Please remove executable permission bits. Proceeding anyway.
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: Configuration file /root/.config/autostart/disable-dpms.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: Configuration file /root/.config/autostart/live-session.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: Configuration file /root/.config/autostart/pulseaudio-ctl.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: /root/.config/autostart/ma-launcher.desktop: not generating unit, error parsing Exec= line: No such file or directory
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: /root/.config/autostart/disable-dpms.desktop: not generating unit, error parsing Exec= line: No such file or directory
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: /root/.config/autostart/pulseaudio-ctl.desktop: not generating unit, error parsing Exec= line: No such file or directory
Okt 04 09:35:05 manj-laptop systemd-xdg-autostart-generator[7702]: /root/.config/autostart/live-session.desktop: not generating unit, error parsing Exec= line: No such file or directory
Okt 04 09:35:07 manj-laptop tumblerd[7867]: Failed to load plugin "tumbler-gepub-thumbnailer.so": libgepub-0.7.so.0: cannot open shared object file: No such file or directory
Okt 04 09:35:07 manj-laptop NetworkManager[798]: <warn>  [1696404907.8140] platform-linux: do-change-link[2]: failure 23 (Too many open files in system) (assume success changing address)
Okt 04 09:35:08 manj-laptop upowerd[8024]: g_udev_device_get_sysfs_path: assertion 'G_UDEV_IS_DEVICE (device)' failed
Okt 04 09:35:08 manj-laptop upowerd[8024]: g_udev_client_query_by_sysfs_path: assertion 'sysfs_path != NULL' failed
Okt 04 09:35:55 manj-laptop NetworkManager[798]: <warn>  [1696404955.0745] device (wlp2s0): no secrets: User canceled the secrets request.
Okt 04 09:35:55 manj-laptop NetworkManager[798]: <warn>  [1696404955.0787] platform-linux: do-change-link[2]: failure 23 (Too many open files in system) (assume success changing address)
Okt 04 09:35:55 manj-laptop NetworkManager[798]: <warn>  [1696404955.0793] device (wlp2s0): Activation: failed for connection 'helloThere'
Okt 04 09:36:03 manj-laptop NetworkManager[798]: <warn>  [1696404963.7966] platform-linux: do-change-link[2]: failure 23 (Too many open files in system) (assume success changing address)
Okt 04 09:36:04 manj-laptop wpa_supplicant[896]: bgscan simple: Failed to enable signal strength monitoring
Okt 04 10:28:28 manj-laptop conmon[13554]: conmon c68216345c704fdffdaa <error>: Failed to create container: exit status 1
Okt 04 11:17:48 manj-laptop kernel: BTRFS warning (device sda1): qgroup rescan init failed, qgroup is not enabled
Okt 04 13:22:17 manj-laptop lightdm[23399]: gkr-pam: unable to locate daemon control file
Okt 04 13:22:32 manj-laptop lightdm[23415]: gkr-pam: unable to locate daemon control file
Okt 04 13:25:15 manj-laptop systemd[7695]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Okt 04 13:25:24 manj-laptop lightdm[23676]: gkr-pam: unable to locate daemon control file
Okt 04 13:25:37 manj-laptop lightdm[23691]: gkr-pam: unable to locate daemon control file
Okt 04 13:25:38 manj-laptop tumblerd[23816]: Failed to load plugin "tumbler-gepub-thumbnailer.so": libgepub-0.7.so.0: cannot open shared object file: No such file or directory
Mi 4. Okt 13:26:22 CEST 2023

Unless you see anything else in the above I figured this far that it might be related to an older bug in lightdm.

No I would be wondering how I can disable lightdm in the startup-process in order to see whether I can login to the terminal and start xfce from there.

13

Well, not being a Gnome user, I can’t see anything. That doesn’t mean there’s nothing to find, though. However, I did think of on last thing to try. and that is removing the ~/.config directory to see if it works.

So let’s backup the .config directory:

mv /home/<userName>/.config /home/<userName>/.config.backup

Where <userName> is equal to, you guessed it, your username.

If it works, start copying the configs files back one-by-one, to find the one causing the problems.

If that doesn’t work, well then I’m fresh out of ideas.

14

that issue is not limited to GNOME I believe. I myself am using xfce4. Would you still believe that this is not to be worked around by trying i.e. another DM?

my $USER/.config/ contains 56320 files, so it might be tricky to try them one by one. If still this is the way to go I guess I start ruling out that newest ones.

15

Apologies. I read the xfce tag, but it kind of slipped my mind seeing as xfce also uses GTK…

I honestly don’t know…But it can’t hurt to try. Or first you can try a new user.

In fact, do that and see if it works, if it does, it confirms it’s some kind of user-configuration.

Do that once you’ve confirmed it is a config file…

16

how would i just switch off the usage of ‘lightdm’ in order to see whether I can login to terminal and ‘startx’ (assuming this will kick me into the Desktop environment (xfce)) from there?

Just disabling the lightdm.service ?

17

I suspect so, yes. But I’m not :100: on it, though. Or stop it first:

systemctl stop lightdm.service

…to see what happens.

:man_shrugging:

19

so, going aroun lightdm was not it (the method for that you digged out in the other thread was spot-on btw).

I could not log in to anybody else then root in the tty session neither. it is getting more mysteroius by the minute somehow.

Luckily I am not for my live depending on this machine right now (besides sucking big time).

btw: thx a mil for all the support till here @Mirdarthos & anybody else

20

Have you got space on your home partition?

Have you checked faillock? Even if it’s not your problem, it may be activated due to failed logins and so complicate matters.

1 Like
21

good point, but

df -h /home
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       443G  397G   44G  91% /home

I never heard of faillock, will look into this. thx