after Aug 13 upgrade cant get past LOG IN screen

[AA BB]

On Aug 13 I did an MX 23 upgrade on two laptops. On one (and only one) of the laptops, after logging in, I always get returned to the LOG IN screen i.e. my password gets rejected on repeated log in attempts.

Aug 13 upgrade installed two new kernels (for sysD and sysV) so I now have 2 new ones and two previous ones, but the same log-in problem applies to whichever of the 4 kernels I select at boot time.

Everything worked OK on both PCs prior to Aug 13 upgrade.

FWIW I have a recent live USB created from a snapshot on the PC that has the problem.

[CharlesV]

Please post your QSI. ( MX Menu, Quick System Info, Copy for Forum, Paste here )
Use the live usb if you need too.

Chances are a partition is full, so while you are in the USB have a look and see what your partition free space is. (Root, and Home partitions.)

[asqwerth]

I'm not at my computer, but potentially OP could try switching to a tty screen (is it ALT-F2.?) from the login screen and using the full inxi terminal command to get a true QSI output.

Or while in live USB, use chroot rescue scan to enter the actual install and use said full inxi command to get the QSI output.

[siamhie]

Aug 13 upgrade installed two new kernels (for sysD and sysV)

You only got one kernel upgrade and two new init entries for that kernel.
So now you have two kernels installed that can be booted to either SysV or systemd.

What else was updated besides the kernel because your old kernel should still be bootable.

[AA BB]

QSI obtained from live USB...other requested info will be posted later

Code: Select all

Snapshot created on: 20250803_1128
System:
  Kernel: 6.1.0-37-amd64 [6.1.140-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: quiet splash
    lang=en_US kbd=us tz=America/New_York
  Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.6_fluxbox_x64
    Libretto May 19 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: Dell product: Latitude E7250 v: N/A serial: <superuser required> Chassis:
    type: 9 serial: <superuser required>
  Mobo: Dell model: 0TVD2T v: A01 serial: <superuser required> UEFI-[Legacy]: Dell v: A24
    date: 04/10/2020
Battery:
  ID-1: BAT0 charge: 24.1 Wh (90.9%) condition: 26.5/38.4 Wh (69.1%) volts: 12.5 min: 11.1
    model: LGC-LGC3.4 DELL WG6RP64 type: Li-poly serial: <filter> status: charging
CPU:
  Info: model: Intel Core i7-5600U bits: 64 type: MT MCP arch: Broadwell gen: core 5 level: v3
    note: check built: 2015-18 process: Intel 14nm family: 6 model-id: 0x3D (61) stepping: 4
    microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 747 high: 798 min/max: 500/3200 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 793 2: 798 3: 600 4: 798 bogomips: 20750
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  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: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow 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 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics:
  Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel arch: Gen-8
    process: Intel 14nm built: 2014-15 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:1616 class-ID: 0300
  Device-2: Sunplus Innovation Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-1.6:4
    chip-ID: 1bcf:2b8d class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: eDP-1 model: LG Display 0x0450 built: 2014 res: 1366x768 hz: 60 dpi: 125 gamma: 1.2
    size: 277x156mm (10.91x6.14") diag: 318mm (12.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 5500 (BDW GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:03.0
    chip-ID: 8086:160c class-ID: 0403
  Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0 class-ID: 0403
  API: ALSA v: k6.1.0-37-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I218-LM vendor: Dell driver: e1000e v: kernel port: f080 bus-ID: 00:19.0
    chip-ID: 8086:15a2 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 8086:095a class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-1.3:3
    chip-ID: 8087:0a2a class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: 1000 hci-v: 4.2 rev: 1000
  Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 245.74 GiB used: 2.45 GiB (1.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: LITE-ON model: LMH-256V2M-11 MSATA 256GB size: 238.47 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 10C
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 type: USB model: USB Flash Memory size: 7.27 GiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda6
    maj-min: 8:6
Sensors:
  System Temperatures: cpu: 41.0 C mobo: 34.0 C sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 1852 libs: 910 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0
    pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 207 Uptime: 2m wakeups: 2 Memory: 15.5 GiB used: 985 MiB (6.2%) Init: SysVinit v: 3.06
  runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

[AA BB]

You only got one kernel upgrade and two new init entries for that kernel.
So now you have two kernels installed that can be booted to either SysV or systemd.

What else was updated besides the kernel because your old kernel should still be bootable.

correct ...each update generates two kernels sysV and sysD.... neither of the two pre- update kernels get me past the LOG IN screen

Dont recall what else the Aug 13 update added to my system

[AA BB]

Chances are a partition is full, so while you are in the USB have a look and see what your partition free space is. (Root, and Home partitions.)

cant take QuickShot of GParted output but UNUSED boot, swap and root partitions = 2.05, 7.81, 11.78 GB
I dont have a home partition

[j2mcgreg]

Your Lite On SSD is nine years old according to this Dell site:
https://www.dell.com/support/home/en-ca ... erid=5g2nv
It might be time to consider a replacement.

[Adrian]

What happens if you try to log in at CLI (press CTRL-ALT-F1) with your user name and password can you do it? Can you also log in with root (if you have a root account setup)?
If you can then maybe examine /var/log/Xorg.0.log and look for EE (Error) lines.

Also, in you past posts you seemed intent to "slim" down your install, maybe you slimmed it too much and removed something critical, I haven't seen anybody else having problems with the update.

Also in general, I would like to discourage people on forum to say "this broke after a update" because.
1. you don't actually know what happened before you had the issue
2. everything happens after a update. There are updates pretty much daily. So whatever problem you might have it will necessarily happen after a update, now... if it's cause by a update it's a totally different thing.

The only exception is if you can replicate this, boot a clean MX ISO, do a upgrade and that breaks the system then it would be worth reporting it like that.

[AA BB]

@Adrian.. " Also, in you past posts you seemed intent to "slim" down your install, maybe you slimmed it too much and removed something critical, I haven't seen anybody else having problems with the update".

Ever since I switched to MX-23 there have been no attempts to "slim down". As of MX 23, all MX installs are made on PCs that dual boot MX and Windows 10 and all are mxfb installs as released.

I also note that a live USB created from a recent snapshot (pre Aug 13 update) on the problem PC works fine.

... I can log in with my user name using CTRL-ALT-F1...there is only one user account on the problem PC