Hello everyone, Recently after some update i wasn’t able to log in into gnome dash: after i inser login credential it just show a black screen and kick me back to login. I was also unable to show terminal with CRTL + ALT + F3 . I found different topic about this bug, some even unresolved. After different tentatives i found out that there were some problem with the combo linux kernel 5.10 - nvidia 460.67 driver. So i:
booted in command line,
edited gdm settings to boot with auto login
booted to gnome-dash and set manjaro to use 5.11 kernel
disabled auto login
upgrading to 5.11 also fixed some bug with boot (suck on plymouth/ black screen).
It’s notable that the nvidia release notes for 460.67 there were different fixes about linux 5.11 drivers.
i’m not very confident with os development but maybe this could be helpfull for someone.
I have the identical problem however I already have 5.11 installed. There were something like 190 packages in the update and I can timeshift back before that. Which package would I need to keep from updating for a temporary fix If I tried it again?
check your gpu driver version and maybe keep from updating the gnome services packages. However for a temporary fix you can simply disable loginscreen, it will compromise your privacy but at least you can do all your things
restart display manager from tty it worked for me.
sudo systemctl restart display-manager
How did you get into a terminal? Ctrl + Alt + F1-4 only gives a blackscreen.
try restarting few times. it was exatly the same for me.
after few times i managed to get into tty.
I have this exact problem.
Login kicks back to login screen. TTY does not work at all.
Did a fresh install, still facing the same problem lol.Tried 5.11, same problem. Tried 5.4 LTS and it works. So yeah, stay on LTS kernels if you don’t have bleeding edge hardware to reduce breakages.
I have 5.10 kernel. Dell XPS.
(as I cannot use tty in my login screen.)
When we have problems gaining access to our systems it is difficult to gather information, let alone fix any problems. Here we will cover common causes and solutions to ‘manjaro wont boot’.
If your desktop does not load properly then you might still be able to use most, if not all, functionality by dropping to a non-graphical TTY.
By default your system will have multiple TTYs, with each corresponding to an Fx key. Your desktop is assigned to one as well - most often F1.
You can change…
Enable auto-login for my user:
So now I can continue troubleshooting.
Most likely the issue is with
Plymouth and GDM. Based on some requests we removed Plymouth support from the regular GDM package. So you can do this:
if you don’t need
Plymouth uninstall its packages and adjust
/etc/default/grub settings including a rebuild of the menu via
mkinitcpio -P as
if you need
Plymouth install gdm-plymouth
I tried to use
splash kernel flag
But still the same behavior. Login kicks back to login screen. TTY changes stays black.
Using auto-login I can use my laptop. Interestingly then logout and login works after first initial login is bypassed.
System: Kernel: 5.10.32-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: GNOME 3.38.4 tk: GTK 3.24.29
wm: gnome-shell dm: GDM 40.0 Distro: Manjaro Linux base: Arch Linux
Machine: Type: Laptop System: Dell product: XPS 15 9570 v: N/A serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: Dell model: 07GHH0 v: A00 serial: <filter> UEFI: Dell v: 1.16.2 date: 04/21/2020
Battery: ID-1: BAT0 charge: 43.1 Wh (61.7%) condition: 69.9/97.0 Wh (72.1%) volts: 11.3 min: 11.4 model: SMP DELL GPM0365
type: Li-ion serial: <filter> status: Discharging
CPU: Info: 6-Core model: Intel Core i9-8950HK bits: 64 type: MT MCP arch: Kaby Lake note: check rev: A cache: L2: 12 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 69597
Speed: 800 MHz min/max: 800/4800 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
9: 800 10: 800 11: 800 12: 800
Graphics: Device-1: Intel UHD Graphics 630 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia v: 460.73.01 bus-ID: 01:00.0 chip-ID: 10de:1c8c
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-12:5 chip-ID: 0c45:671d class-ID: 0e02
Display: x11 server: X.org 1.20.11 compositor: gnome-shell driver: loaded: intel resolution: <missing: xdpyinfo>
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 21.0.3 direct render: Yes
Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
chip-ID: 8086:a348 class-ID: 0403
Sound Server-1: ALSA v: k5.10.32-1-MANJARO running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.26 running: yes
Network: Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Rivet Networks driver: ath10k_pci
v: kernel port: 3000 bus-ID: 3b:00.0 chip-ID: 168c:003e class-ID: 0280
IF: wlp59s0 state: up mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
Bluetooth: Device-1: Qualcomm Atheros QCA61x4 Bluetooth 4.0 type: USB driver: btusb v: 0.8 bus-ID: 1-4:3 chip-ID: 0cf3:e300
Report: rfkill ID: hci0 rfk-id: 2 state: down bt-service: enabled,running rfk-block: hardware: no software: yes
address: see --recommends
Drives: Local Storage: total: 953.87 GiB used: 196.45 GiB (20.6%)
ID-1: /dev/nvme0n1 vendor: Toshiba model: KXG50ZNV1T02 NVMe 1024GB size: 953.87 GiB speed: 31.6 Gb/s lanes: 4
rotation: SSD serial: <filter> rev: AADA4105 temp: 28.9 C scheme: GPT
Partition: ID-1: / size: 937.6 GiB used: 196.45 GiB (21.0%) fs: ext4 dev: /dev/dm-0
ID-2: /boot/efi size: 299.4 MiB used: 440 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 39.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0 fan-2: 0
Info: Processes: 298 Uptime: 35m wakeups: 7 Memory: 30.99 GiB used: 3.68 GiB (11.9%) Init: systemd v: 247 Compilers:
gcc: 10.2.0 Packages: 1427 pacman: 1404 flatpak: 23 Shell: Zsh v: 5.8 running-in: gnome-terminal inxi: 3.3.04
This is from failing boot:
journalctl -b -2 -u gdm
-- Journal begins at Fri 2020-07-31 14:11:37 EEST, ends at Wed 2021-04-28 21:33:55 EEST. --
huhti 28 20:38:06 mine-xps systemd: Starting GNOME Display Manager...
huhti 28 20:38:07 mine-xps systemd: Started GNOME Display Manager.
huhti 28 20:38:28 mine-xps gdm-password]: gkr-pam: unable to locate daemon control file
huhti 28 20:38:28 mine-xps gdm-password]: gkr-pam: stashed password to try later in open session
huhti 28 20:38:28 mine-xps gdm-password]: pam_systemd_home(gdm-password:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
huhti 28 20:38:28 mine-xps gdm-password]: pam_unix(gdm-password:session): session opened for user sff(uid=1000) by (uid=0)
huhti 28 20:38:28 mine-xps gdm-password]: pam_env(gdm-password:session): deprecated reading of user environment enabled
huhti 28 20:38:28 mine-xps gdm-password]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
huhti 28 20:38:32 mine-xps gdm: Gdm: GdmDisplay: Session never registered, failing
huhti 28 20:39:39 mine-xps gdm: Gdm: Tried to look up non-existent conversation gdm-launch-environment
huhti 28 20:39:39 mine-xps gdm: Gdm: Freeing conversation 'gdm-launch-environment' with active job
huhti 28 20:39:39 mine-xps systemd: Stopping GNOME Display Manager...
huhti 28 20:39:39 mine-xps systemd: gdm.service: Succeeded.
huhti 28 20:39:39 mine-xps systemd: Stopped GNOME Display Manager
Now with auto-login:
-- Journal begins at Fri 2020-07-31 14:11:37 EEST, ends at Wed 2021-04-28 21:40:39 EEST. --
huhti 28 20:45:34 mine-xps systemd: Starting GNOME Display Manager...
huhti 28 20:45:34 mine-xps systemd: Started GNOME Display Manager.
huhti 28 20:45:34 mine-xps gdm-autologin]: pam_systemd_home(gdm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
huhti 28 20:45:34 mine-xps gdm-autologin]: pam_unix(gdm-autologin:session): session opened for user sff(uid=1000) by (uid=0)
huhti 28 20:45:34 mine-xps gdm-autologin]: pam_env(gdm-autologin:session): deprecated reading of user environment enabled
huhti 28 20:45:34 mine-xps gdm-autologin]: gkr-pam: gnome-keyring-daemon started properly
I can take more logs if someone know what to look at?
still the same behavior
You many need to enable
early KMS then.
I got my setup to work with:
early KMS .
Thanks for the support!
Update. with 5.11 bootloop problems start again. Definetly fix setting ExecStartPre=/bin/sleep 1 under Service session in gdm-plymouth. Will try now with libgdm-pymouth and kms
enabling kms and installing
libgdm-plymouth worked, but i had to set WaylandEnable=false in /etc/gdm/custom.conf to start de with xserver only.
boot is also faster now.
A post was split to a new topic:
Gnome loops back to login prompt
Closed due to necro-bumping.