It also sounds like the newly created account feels working better ... if I'm not wrong :)Eadwine Rose wrote: Wed Jun 19, 2024 12:43 pm Your post #6 looked like you were complaining on lack of replies.
No autologin activated.
Re: No autologin activated.
Re: No autologin activated.
Interestingly, I encountered an issue with Auto-login last week that I forgot to report. This may have been related to the machine.
I performed a clean Windows 10 installation on a retired 2011 Sony VAIO (2nd Gen i5-2410m, 8GB RAM, new SSD). The machine was so painfully slow, it was taking 1M45s to shutdown and 2M from zero up to the Windows Desktop. I installed Firefox, set the homepage to https://mxlinux.org/, re-timed it and the the extra step took the time from 2M to 2M33s, tested 3 times to confirm.
Thinking this would be a great machine to demonstrate how MX can revitalize an older system, I partitioned off 40GB and booted a freshly made MX-23.3_KDE Live USB. After installing all the updates, I ran the installer then rebooted without the USB key. Having to enter the user PW I realised I had forgotten to set the auto-login option during installation, so using MXUM, I set the user to auto-login, then using Session and Startup I added Firefox to which I had also set to load the MX Homepage to load.
On rebooting, the user acct did not auto-login and checking all the settings, nothing I did at the GUI level was going to make that happen. As per the OP's issue, autologin was not working. I didn't have time to waste so rebooted live, repeated all my earlier steps and ran the installer, selecting auto-login and all went well.
All this to say I have seen first hand what @Johyn is reporting, but I have no evidence to produce. I was recording the whole thing as a time lapse operation at 15x speed with an old phone running a clock timer next to the laptop, but when the process turned into a failure, I deleted the recording. Even if I hadn't, the fine details would have been missed with 4s worth of playback equalling 1M of real time.
I can't go this far without revealing the result of my testing, that would be cruel. The bootup time from grub to FF opening the MX Homepage was 32s with SysVinit, and 36s with SystemD. Shutdown times are 11s with SysVinit, and 2s with SystemD, so significantly faster than Windows10. What is not stated is all the timings here were after my first MX Dual-boot installation, where I could have a fixed and consistent start time for each boot, a Grub OS entry selected and a keyboard tap to start the timer on each startup option.
I performed a clean Windows 10 installation on a retired 2011 Sony VAIO (2nd Gen i5-2410m, 8GB RAM, new SSD). The machine was so painfully slow, it was taking 1M45s to shutdown and 2M from zero up to the Windows Desktop. I installed Firefox, set the homepage to https://mxlinux.org/, re-timed it and the the extra step took the time from 2M to 2M33s, tested 3 times to confirm.
Thinking this would be a great machine to demonstrate how MX can revitalize an older system, I partitioned off 40GB and booted a freshly made MX-23.3_KDE Live USB. After installing all the updates, I ran the installer then rebooted without the USB key. Having to enter the user PW I realised I had forgotten to set the auto-login option during installation, so using MXUM, I set the user to auto-login, then using Session and Startup I added Firefox to which I had also set to load the MX Homepage to load.
On rebooting, the user acct did not auto-login and checking all the settings, nothing I did at the GUI level was going to make that happen. As per the OP's issue, autologin was not working. I didn't have time to waste so rebooted live, repeated all my earlier steps and ran the installer, selecting auto-login and all went well.
All this to say I have seen first hand what @Johyn is reporting, but I have no evidence to produce. I was recording the whole thing as a time lapse operation at 15x speed with an old phone running a clock timer next to the laptop, but when the process turned into a failure, I deleted the recording. Even if I hadn't, the fine details would have been missed with 4s worth of playback equalling 1M of real time.
I can't go this far without revealing the result of my testing, that would be cruel. The bootup time from grub to FF opening the MX Homepage was 32s with SysVinit, and 36s with SystemD. Shutdown times are 11s with SysVinit, and 2s with SystemD, so significantly faster than Windows10. What is not stated is all the timings here were after my first MX Dual-boot installation, where I could have a fixed and consistent start time for each boot, a Grub OS entry selected and a keyboard tap to start the timer on each startup option.
Mike P
Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs
Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs
Re: No autologin activated.
I cannot reproduce this on any of my test machines.
@Johyn Please post your QSI ( MX Menu | Quick System Info | Copy for Forum | paste here )
@Johyn Please post your QSI ( MX Menu | Quick System Info | Copy for Forum | paste here )
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
Re: No autologin activated.
Here it is:
[/code]
But it should be noted that i'm in the turmoil of a high jump eh. I'm now computin from my new user fresh home. The last one is more and more buggy after all the manips of upgradin and restorin, and really on the verge of collapsin. I'm workin on its transition, usin my second window drive to pass on the files. But i have trouble upgradin the kernel to 6.6, withis multiple error in console: '496 WRN: "W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:9 and /etc/apt/'. Guess it's because of my other users instalations. Could i delete them safely, and keep only this new one, for an hypothetical autologin?
Code: Select all
[CODE]System: Kernel: 5.10.0-28-amd64 [5.10.209-2] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-28-amd64 root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.18.1 tk: Gtk 3.24.36 info: xfce4-panel wm: xfwm 4.18.0 vt: 1 dm: startx
Distro: MX-23.3_x64 Libretto October 20 2021 base: Debian GNU/Linux 12 (bookworm)
Machine: Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> Chassis: type: 3
serial: <filter>
Mobo: Gigabyte model: H61M-S2PV serial: <filter> UEFI: American Megatrends v: FG WG
date: 02/19/2013
CPU: Info: Quad Core model: Intel Core i7-2600 bits: 64 type: MT MCP arch: Sandy Bridge
family: 6 model-id: 2A (42) stepping: 7 microcode: 2F cache: L2: 8 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54274
Speed: 3152 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 3152 2: 2614 3: 2523
4: 2933 5: 2486 6: 2456 7: 2664 8: 2640
Vulnerabilities: Type: gather_data_sampling 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: retbleed status: Not affected
Type: spec_rstack_overflow 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: Retpolines, IBPB: conditional, IBRS_FW, STIBP:
conditional, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] vendor: Gigabyte driver: nvidia
v: 535.161.08 bus-ID: 01:00.0 chip-ID: 10de:1c02 class-ID: 0300
Display: server: X.Org 1.21.1.7 compositor: xfwm4 v: 4.18.0 driver: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3")
s-diag: 583mm (23")
Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 102 size: 476x268mm (18.7x10.6")
diag: 546mm (21.5")
Monitor-2: DVI-D-1 res: 1920x1080 hz: 50 dpi: 66 size: 735x420mm (28.9x16.5")
diag: 847mm (33.3")
OpenGL: renderer: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 535.161.08
direct render: Yes
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
Device-2: NVIDIA GP106 High Definition Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f1 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-28-amd64 running: yes
Sound Server-2: PulseAudio v: 16.1 running: yes
Sound Server-3: PipeWire v: 1.0.0 running: yes
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
driver: r8169 v: kernel port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.36 TiB used: 219.87 GiB (15.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000AAKX-75U6AA0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A
serial: <filter> rev: 1H19 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: MQ02ABD100H size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400
serial: <filter> rev: 5A scheme: GPT
Partition: ID-1: / raw-size: 457.5 GiB size: 449.25 GiB (98.20%) used: 219.87 GiB (48.9%) fs: ext4
dev: /dev/sda3 maj-min: 8:3
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 661 KiB (0.3%) fs: vfat
dev: /dev/sda2 maj-min: 8:2
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda1
maj-min: 8:1
Sensors: System Temperatures: cpu: 53.0 C mobo: 27.8 C gpu: nvidia temp: 58 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos: Packages: 2930 note: see --pkg apt: 2891 lib: 1556 flatpak: 39
Active apt repos in: /etc/apt/sources.list
1: deb https://ftp.debian.org/debian/ bookworm contrib main non-free non-free-firmware
2: deb https://ftp.debian.org/debian/ bookworm-updates contrib main non-free non-free-firmware
3: deb https://ftp.debian.org/debian/ bookworm-proposed-updates contrib main non-free non-free-firmware
4: deb https://ftp.debian.org/debian/ bookworm-backports contrib main non-free non-free-firmware
5: deb https://security.debian.org/debian-security/ bookworm-security contrib main non-free non-free-firmware
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 arch=amd64] 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
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/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/lutris.list
1: deb [signed-by=/etc/apt/keyrings/lutris.gpg] https://download.opensuse.org/repositories/home:/strycore/Debian_12/ ./
Active apt repos in: /etc/apt/sources.list.d/microsoft-prod.list
1: deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/debian/11/prod bookworm main
Active apt repos in: /etc/apt/sources.list.d/mono-official-vs.list
1: deb https://download.mono-project.com/repo/debian vs-buster main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.lip6.fr/pub/linux/distributions/mxlinux/packages/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/notepadqq-team-ubuntu-notepadqq-mantic.list
1: deb http://ppa.launchpad.net/notepadqq-team/notepadqq/ubuntu mantic main
Active apt repos in: /etc/apt/sources.list.d/playonlinux.list
1: deb http://deb.playonlinux.com/ stretch main
Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
No active apt repos in: /etc/apt/sources.list.d/steam-beta.list
Active apt repos in: /etc/apt/sources.list.d/steam-stable.list
1: deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
2: deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
Active apt repos in: /etc/apt/sources.list.d/unityhub.list
1: deb [signed-by=/usr/share/keyrings/Unity_Technologies_ApS.gpg] https://hub.unity3d.com/linux/repos/deb stable main
Active apt repos in: /etc/apt/sources.list.d/vscode.list
1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Active apt repos in: /etc/apt/sources.list.d/waydroid.list
1: deb [signed-by=/usr/share/keyrings/waydroid.gpg] https://repo.waydro.id/ bookworm main
Info: Processes: 282 Uptime: 29m wakeups: 0 Memory: 15.58 GiB used: 3.38 GiB (21.7%)
Init: systemd v: 252 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 12.2.0
alt: 10/12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.06
Boot Mode: UEFI
But it should be noted that i'm in the turmoil of a high jump eh. I'm now computin from my new user fresh home. The last one is more and more buggy after all the manips of upgradin and restorin, and really on the verge of collapsin. I'm workin on its transition, usin my second window drive to pass on the files. But i have trouble upgradin the kernel to 6.6, withis multiple error in console: '496 WRN: "W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:9 and /etc/apt/'. Guess it's because of my other users instalations. Could i delete them safely, and keep only this new one, for an hypothetical autologin?
Re: No autologin activated.
Nothing to lose to make sure nothing's missing or broken:
Reboot.
Code: Select all
sudo apt update ; sudo apt reinstall liblightdm-gobject-1-0 lightdm-gtk-greeter-mx23 lightdm-gtk-greeter-settings lightdm-gtk-greeter lightdm-modified-init lightdm -y
Re: No autologin activated.
I'm not authorized to paste on root as a new user...
Last edited by Johyn on Wed Jun 19, 2024 9:43 pm, edited 1 time in total.
Re: No autologin activated.
On MX 23 "user's " pw. is needed for sudo (by default).
... As I said before: A fresh installation would be even faster (just 10-15 min. even with an old pc and most of it is "files are being copied" ... ) :)
... As I said before: A fresh installation would be even faster (just 10-15 min. even with an old pc and most of it is "files are being copied" ... ) :)
Re: No autologin activated.
I cannot change the first user? And i'm tryin to make that fresh install. I'm actually movin in that new user home: just have to transfer some files, proprietary rights, and remove the old home.
Re: No autologin activated.
You can cut-paste or copy-paste data from that user to this one (manually, using the file manager).
Also in MX User Manager there is the copy/Sync tab (however that may copy the unwanted settings, too).
If you mean you cannot open root Thunar (that's another issue, long story):
in a terminal.
Also in MX User Manager there is the copy/Sync tab (however that may copy the unwanted settings, too).
If you mean you cannot open root Thunar (that's another issue, long story):
Code: Select all
pkexec thunar
Re: No autologin activated.
... After everything's ok with the new user (moving etc.) you can delete the old user with MXUM , later (if you like only) you can even rename the new user to that (old) one.