Hello everybody,
After an update I am not able to login on my AVL system anymore. I installed lightdm and a webkit2-greeter-theme some months ago, togheter with the packages I needed to toggle the desktop icons (the feature that displays the wallpaper is actually cool but I need to see the icons in order to not forget things).
Everything looks to work fine, I can type my password, just the enter key is doing nothing. Lately I can't even open a tty (with ctrl+alt+f*) because it freezes, but if I press ctrl+alt+f7, I am always able to type the password again (but again, no enter key). The keyboard is perfectly working with the grub menu at the begining or with the tty, when I am able to switch to it
Any idea to recover the system?
Can't login on my AVL-MXE system
Re: Can't login on my AVL-MXE system
Have you tried to login as root?
Or: If you have a live usb/cd/dvd ("any" Linux, no matter old/new..) (..or another Linux system installed on pc...) boot with that and check whether partition(s) got full. While you're at it: delete the .Xauthority file in /home/yourusername/ of the installed AVL.
Or: If you have a live usb/cd/dvd ("any" Linux, no matter old/new..) (..or another Linux system installed on pc...) boot with that and check whether partition(s) got full. While you're at it: delete the .Xauthority file in /home/yourusername/ of the installed AVL.
Re: Can't login on my AVL-MXE system
I erased the .Xauthority file but nothing changes. I logged in on my other partition's MX installation and ran GParted: the AVL home partition is the most full and it has 2,5 Gb of free space... I really don't know how to login as root in this conditions.Huckleberry Finn wrote: ↑Wed Oct 05, 2022 5:35 pm Have you tried to login as root?
Or: If you have a live usb/cd/dvd ("any" Linux, no matter old/new..) (..or another Linux system installed on pc...) boot with that and check whether partition(s) got full. While you're at it: delete the .Xauthority file in /home/yourusername/ of the installed AVL.
Re: Can't login on my AVL-MXE system
I managed to load the session via tty. Posting some outputs that I hope might be helpful, since I don't know where and what to look for.
Code: Select all
# cat /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=2310
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/02_MX.conf
[+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: [LightDM] contains unknown option greeter-session
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.03s] DEBUG: Monitoring logind for seats
[+0.03s] DEBUG: New seat added from logind: seat0
[+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.03s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.03s] DEBUG: Seat seat0: Starting
[+0.03s] DEBUG: Seat seat0: Creating greeter session
[+0.03s] DEBUG: Seat seat0: Creating display server of type x
[+0.03s] DEBUG: Seat seat0: Plymouth is running on VT 1, but this is less than the configured minimum of 7 so not replacing it
[+0.03s] DEBUG: Quitting Plymouth
[+0.81s] DEBUG: Using VT 7
[+0.81s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.81s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.81s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.81s] DEBUG: XServer 0: Launching X Server
[+0.81s] DEBUG: Launching process 2566: /bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.81s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.81s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.81s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.84s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.84s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+1.39s] DEBUG: Got signal 10 from process 2566
[+1.39s] DEBUG: XServer 0: Got signal from X server :0
[+1.39s] DEBUG: XServer 0: Connecting to XServer :0
[+1.44s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+1.44s] DEBUG: Session pid=2648: Started with service 'lightdm-greeter', username 'lightdm'
[+1.45s] DEBUG: Session pid=2648: Authentication complete with return value 0: Success
[+1.45s] DEBUG: Seat seat0: Session authenticated, running command
[+1.45s] DEBUG: Launching process 2651: /usr/bin/lightdm-shutdown
[+1.46s] DEBUG: Process 2651 exited with return value 0
[+1.46s] DEBUG: Seat seat0: Exit status of /usr/bin/lightdm-shutdown: 0
[+1.46s] DEBUG: Session pid=2648: Running command /bin/lightdm-webkit2-greeter
[+1.46s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+1.46s] DEBUG: Session pid=2648: Logging to /var/log/lightdm/seat0-greeter.log
[+1.48s] DEBUG: Activating VT 7
[+1.48s] DEBUG: Activating login1 session c1
[+1.48s] DEBUG: Seat seat0 changes active session to c1
[+1.48s] DEBUG: Session c1 is already active
[+11.58s] DEBUG: Seat seat0 changes active session to
[+74.52s] DEBUG: Seat seat0 changes active session to 2
Code: Select all
# cat /var/log/lightdm/seat0-greeter.log
(WebKitWebProcess:2682): GLib-WARNING **: 00:14:59.805: ../../../glib/giounix.c:410Error while getting flags for FD: Descrittore di file errato (9)
(WebKitWebProcess:2682): GLib-WARNING **: 00:14:59.805: Invalid file descriptor.
** (WebKitWebProcess:2682): CRITICAL **: 00:15:05.370: lightdm_greeter_cancel_authentication: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:05.370: lightdm_greeter_authenticate: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:05.913: lightdm_greeter_cancel_authentication: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:05.913: lightdm_greeter_authenticate: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:06.212: lightdm_greeter_cancel_authentication: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:06.212: lightdm_greeter_authenticate: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:06.481: lightdm_greeter_cancel_authentication: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:06.481: lightdm_greeter_authenticate: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:06.745: lightdm_greeter_cancel_authentication: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:06.745: lightdm_greeter_authenticate: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:07.016: lightdm_greeter_cancel_authentication: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:07.016: lightdm_greeter_authenticate: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:07.295: lightdm_greeter_cancel_authentication: assertion 'priv->connected' failed
** (WebKitWebProcess:2682): CRITICAL **: 00:15:07.295: lightdm_greeter_authenticate: assertion 'priv->connected' failed
Code: Select all
# dmesg | grep error
[ 0.067578] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors
[ 0.255671] pcieport 0000:00:1c.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 0.255896] pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[ 2.072597] ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20210930/psparse-529)
[ 2.216362] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 2.276812] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-67.ucode failed with error -2
[ 2.276835] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-66.ucode failed with error -2
[ 2.276856] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-65.ucode failed with error -2
[ 2.276876] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-64.ucode failed with error -2
[ 88.270017] traps: nitrogen[3394] trap int3 ip:7f5a03c18ca7 sp:7fffff0fe010 error:0 in libglib-2.0.so.0.6600.8[7f5a03bdc000+88000]
[ 93.320856] traps: nitrogen[3835] trap int3 ip:7f775f44dca7 sp:7fffa6b4f580 error:0 in libglib-2.0.so.0.6600.8[7f775f411000+88000]
Code: Select all
System: Kernel: 5.16.0-18.1-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: audit=0 intel_pstate=disable hpet=disable BOOT_IMAGE=/boot/vmlinuz-5.16.0-18.1-liquorix-amd64
root=UUID=<filter> ro audit=0 intel_pstate=disable quiet threadirqs splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 1 dm: LightDM 1.26.0
Distro: Debian GNU/Linux 11 (bullseye) base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: ASUSTeK product: ZenBook UX534FTC_UX533FTC v: 1.0 serial: <filter>
Mobo: ASUSTeK model: UX534FTC v: 1.0 serial: <filter> UEFI: American Megatrends v: UX534FTC.305 date: 04/13/2020
Battery: ID-1: BAT0 charge: 60.5 Wh (100.0%) condition: 60.5/71.0 Wh (85.2%) volts: 15.8 min: 15.8
model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Not charging cycles: 48
CPU: Info: Quad Core model: Intel Core i7-10510U bits: 64 type: MT MCP arch: Kaby Lake note: check family: 6
model-id: 8E (142) stepping: C (12) microcode: F0 cache: L2: 8 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 36799
Speed: 4290 MHz min/max: 400/2301 MHz boost: enabled Core speeds (MHz): 1: 4290 2: 1800 3: 1800 4: 1800 5: 1800
6: 1800 7: 1800 8: 1800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
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
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 status: Vulnerable: eIBRS with unprivileged eBPF
Type: srbds mitigation: TSX disabled
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0
chip-ID: 8086:9b41 class-ID: 0300
Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: ASUSTeK driver: nvidia v: 470.141.03
bus-ID: 02:00.0 chip-ID: 10de:1f91 class-ID: 0302
Device-3: IMC Networks USB2.0 HD IR UVC WebCam type: USB driver: uvcvideo bus-ID: 1-5:3 chip-ID: 13d3:56cb
class-ID: 0e02 serial: <filter>
Display: server: X.Org 1.20.13 compositor: xfwm4 v: 4.16.1 driver: loaded: modesetting,nvidia
unloaded: fbdev,nouveau,vesa alternate: nv display-ID: :1.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6") diag: 395mm (15.5")
OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 21.2.5 direct render: Yes
Audio: Device-1: Intel Comet Lake PCH-LP cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel
alternate: snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0403
Device-2: Yamaha Steinberg UR44C type: USB driver: snd-usb-audio bus-ID: 1-1:2 chip-ID: 0499:1730 class-ID: 0103
Sound Server-1: ALSA v: k5.16.0-18.1-liquorix-amd64 running: yes
Sound Server-2: JACK v: 1.9.21 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Network: Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel port: 4000 bus-ID: 00:14.3 chip-ID: 8086:02f0
class-ID: 0280
IF: wlo1 state: up mac: <filter>
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 chip-ID: 8087:0026 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 sub-v: 24bf hci-v: 5.2
rev: 24bf
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept
service-classes: rendering, capturing, audio
Drives: Local Storage: total: 1.42 TiB used: 307.48 GiB (21.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLQ512HALU-00000 size: 476.94 GiB block-size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: FXV7000Q temp: 20.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Crucial model: ATA CT1050MX size: 978.09 GiB block-size:
physical: 512 B logical: 512 B type: N/A serial: <filter> rev: R040 scheme: MBR
Partition: ID-1: / raw-size: 26.7 GiB size: 26.12 GiB (97.80%) used: 20.69 GiB (79.2%) fs: ext4 dev: /dev/nvme0n1p6
maj-min: 259:6
ID-2: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.45%) used: 403 KiB (0.4%) fs: vfat dev: /dev/nvme0n1p5
maj-min: 259:5
ID-3: /home raw-size: 9.07 GiB size: 8.83 GiB (97.35%) used: 6.46 GiB (73.2%) fs: ext4 dev: /dev/nvme0n1p7
maj-min: 259:7
Swap: Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 15.62 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors: System Temperatures: cpu: 61.0 C mobo: N/A
Fan Speeds (RPM): cpu: 3100
Repos: Packages: note: see --pkg apt: 3005 lib: 1709 flatpak: 0
No active apt repos in: /etc/apt/sources.list
No active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://it.mxrepo.com/mx/repo/ bullseye main non-free
Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
Info: Processes: 327 Uptime: 13m wakeups: 1926 Memory: 15.44 GiB used: 2.7 GiB (17.5%) Init: SysVinit v: 2.96 runlevel: 5
default: 5 tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: Bash v: 5.1.4
running-in: quick-system-info-mx inxi: 3.3.06
Boot Mode: UEFI
Re: Can't login on my AVL-MXE system
On login screen click the username box, select "Other" , then type root as the username into the below box, and the root pw under that ...
You can also press F3 (in both trials, normal user and root) and use the "onboard" , at least for the Enter key to make it sure..
If still not, you can create a new user on live session (we'll go on) at least to see if it's possible to login with that..
Re: Can't login on my AVL-MXE system
I made a post also on the xfce forum and it looks like there's a bug in the "webkit" package newly installed. I have to understand its exact name and I will open a bug report.
Thank you for your support.
https://forum.xfce.org/viewtopic.php?id=16156
Thank you for your support.
https://forum.xfce.org/viewtopic.php?id=16156
Re: Can't login on my AVL-MXE system
You can login again that way (and if you have internet):
https://forum.mxlinux.org/viewtopic.php ... 28#p698028
(Or, do it when booted with live usb (it can even be your snapshot iso you created previously) after chrooting with "Chroot Rescue Scan" from menu.)
Also see the rest of that thread :)
https://forum.mxlinux.org/viewtopic.php ... 28#p698028
(Or, do it when booted with live usb (it can even be your snapshot iso you created previously) after chrooting with "Chroot Rescue Scan" from menu.)
Also see the rest of that thread :)
Re: Can't login on my AVL-MXE system
For future reference AV Linux by default uses SLiM not lightDM so this should not be a recurrent issue..
Thanks for the feedback and Huck for your assistance as I know very little about lightDM
Thanks for the feedback and Huck for your assistance as I know very little about lightDM