In a flash, the page reloads and I’m back at the login screen

I have this same issue, but with the Garuda Hyprland.

I’m having a bit of trouble getting Garuda Hyprland up and running after trying a live boot installation.

Here’s what’s happening:

  • I booted the ISO from a USB drive and everything seemed to go smoothly.

  • After the installation, I have the option to restart or keep using the live environment. ‍:female_sign:

  • When I restart and try to log in with my credentials, it looks like I’m about to enter the desktop…

  • …but then, in a flash, the page reloads and I’m back at the login screen.

I’m hoping someone can help me figure out this login loop!

Here are some additional details that might be helpful:

  • I currently have no OS currently installed.
  • I used the Garuda Hyprland from Live Boot, and used the Mod+i to go through the installation.
  • For the partitioning, I selected the Erase Disk option so the Garuda Hyprland has Full disk space.

Any advice or suggestions would be greatly appreciated!

Thanks in advance!

P.S. I’m still learning the ropes with Linux, so please be gentle with the technical jargon.

Looking forward to hearing from the community!

From there you can post the garuda-inxi, please.
I think it is the nvidia problem.
I moved your post, so you are missing the template.


:warning: Missing information requested in the template may result in not receiving assistance :warning:

Make sure you have done the following before you post:

Issue still unresolved? Then:

  • ONE issue per topic.
  • Describe your issue in detail. The more we know, the better we can help
  • Show us the results of your searches, and what you’ve tried
  • After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)
  • Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text

Read
https://forum.garudalinux.org/t/hyprland-downloads-231213-fixes-nvidia/29246/193

3 Likes

Here, below is the FULL output of my garuda-inix


 ╭─garuda@garuda in ~ as 🧙 
 ╰─λ garuda-inxi
System:
  Kernel: 6.5.9-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=garuda root=miso:LABEL=GARUDA_HYPRLAND_RAPTOR quiet
    systemd.show_status=1 ibt=off driver=free nouveau.modeset=1
    i915.modeset=1 radeon.modeset=1
  Desktop: Hyprland info: waybar vt: 1 dm: SDDM Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 20SL v: Lenovo ThinkBook 14-IIL
    serial: <superuser required> Chassis: type: 10 v: Lenovo ThinkBook 14-IIL
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40697 WIN
    serial: <superuser required> UEFI: LENOVO v: DJCN20WW date: 08/10/2020
Battery:
  ID-1: BAT1 charge: 9.8 Wh (26.6%) condition: 36.8/45.0 Wh (81.8%)
    power: 15.0 W volts: 10.6 min: 11.1 model: Celxpert L19C3PF9 type: Li-poly
    serial: <filter> status: discharging cycles: 1394
CPU:
  Info: model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake
    gen: core 10 level: v4 note: check built: 2019-21 process: Intel 10nm
    family: 6 model-id: 0x7E (126) stepping: 5 microcode: 0xBC
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 2 MiB desc: 4x512 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 940 high: 1301 min/max: 400/3600 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1218 2: 1273 3: 798
    4: 1301 5: 452 6: 819 7: 400 8: 1264 bogomips: 19046
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Iris Plus Graphics G1 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-11 process: Intel 10nm built: 2019-21 ports: active: eDP-1
    empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:8a56 class-ID: 0300
  Device-2: Lite-On [] driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 3-6:3 chip-ID: 04ca:7070 class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2
    compositor: Hyprland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 1
  Monitor-1: eDP-1 model: AU Optronics 0x203d built: 2018 res: 1920x1080
    hz: 60 dpi: 158 gamma: 1.2 scale: 1 size: 309x174mm (12.17x6.85")
    diag: 355mm (14") ratio: 16:9 modes: 1920x1080
  API: Vulkan v: 1.3.269 layers: 3 device: 0 type: integrated-gpu name: Intel
    UHD Graphics (ICL GT1) driver: mesa intel v: 23.2.1-arch1.2
    device-ID: 8086:8a56 surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 16.0.6 256 bits) driver: mesa llvmpipe
    v: 23.2.1-arch1.2 (LLVM 16.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_icl
    bus-ID: 00:1f.3 chip-ID: 8086:34c8 class-ID: 0403
  API: ALSA v: k6.5.9-zen2-1-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 0.3.83 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 Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:34f0 class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp1s0 state: down mac: <filter>
Drives:
  Local Storage: total: 505.81 GiB used: 3.57 GiB (0.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZALQ512HALU-000L2 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: AL2QFXV7 temp: 31.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: TransMemory
    size: 28.87 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 2.0 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
    fw-rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 7.28 GiB used: 3.37 GiB (46.2%)
    priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:6
Sensors:
  System Temperatures: cpu: 65.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 265 Uptime: 1d 13h 52m wakeups: 42 Memory: total: 8 GiB
  note: est. available: 7.28 GiB used: 4.63 GiB (63.5%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1228 libs: 356 tools: paru Shell: fish v: 3.6.1
  running-in: foot inxi: 3.3.30
Garuda (2.6.17-1):
  System install date:     2023-12-17
  Last full system update: 2023-12-17 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       <superuser required>
  Failed units:            snapper-cleanup.service

Whatever the problem may be, I am confident I’ll get the best support from this community. I’ll be on standby

1 Like

Welcome to the Garuda forums! :smiley:
It’s possibly related to an unset keymap problem if you didn’t opt for the US layout upon installation: Unset Keymap Preventing Login

To see if this is the issue:

  1. Change to a different tty by pressing ctrl alt F1-F7 (any will do, you just need the terminal available)
  2. Type localectl status - if the VC layout is unset, this is the problem that’s not letting you log in
  3. If it’s unset, use the US layout for now as it will definitely let you login: localectl set-keymap us.

If you ran localectl status and your VC layout was set, then please run Hyprland and see the crash dump file (which should be somewhere in ~/.hyprland). If you have a USB stick mounted then you should be able to copy it there, and then post the contents here :slight_smile:

1 Like

This is old.
Try
https://iso.builds.garudalinux.org/iso/community/hyprland/231219/

2 Likes

Alt :slight_smile:

1 Like

Good catch! :joy:


Anywho, if the new ISO installation still doesn’t let you log in, then try the steps I posted above.

1 Like

I was about to respond to everyone’s messages and I realised I could no longer connect to available networks. I just did the Live Boot again, so give me a sec. I’ll respond to y’all

ALright, I just realised I could no longer connect to Available networks because of the ctrl alt F7 :joy:

Non of the combos from ctrl alt F1-F6 worked though.

I am already able to launch the terminal using the Mod + Enter and as soon as I do, it launches, while displaying the Garuda brand? in ASCII text, with my System Info, like the neofetch does.

Below is the output from having executed the command in the second suggestion

╭─garuda@garuda in ~ as 🧙 
 ╰─λ localectl status
System Locale: LANG=en_US.UTF-8
    VC Keymap: us
   X11 Layout: us
    X11 Model: pc105+inet
  X11 Options: terminate:ctrl_alt_bksp

Running Hyprland did something weird. It zoomed my screen and I think Hyprland launched floating with the terminal in half-screen.

Below is the out in the terminal.

Welcome to Hyprland!
[LOG] Instance Signature: 7f4b0aaadc8348e8814285d7ec582cf737b62d3b_1702995538
[LOG] Hyprland PID: 8039
[LOG] ===== SYSTEM INFO: =====
[LOG] System name: Linux
[LOG] Node name: garuda-hyprland
[LOG] Release: 6.5.9-zen2-1-zen
[LOG] Version: #1 ZEN SMP PREEMPT_DYNAMIC Thu, 26 Oct 2023 00:51:53 +0000


[LOG] GPU information:
00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller])


[LOG] os-release:
NAME="Garuda Linux"
PRETTY_NAME="Garuda Linux"
ID=garuda
ID_LIKE=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://garudalinux.org/"
DOCUMENTATION_URL="https://wiki.garudalinux.org/"
SUPPORT_URL="https://forum.garudalinux.org/"
BUG_REPORT_URL="https://gitlab.com/groups/garuda-linux/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=garudalinux

[LOG] ========================



[INFO] If you are crashing, or encounter any bugs, please consult https://wiki.hyprland.org/Crashes-and-Bugs/


[LOG] 
Current splash: I'm still standing, better than I ever did


[LOG] Creating the HookSystem!
[LOG] Creating the KeybindManager!
[LOG] [hookSystem] New hook event registered: configReloaded
[LOG] Creating the AnimationManager!
[LOG] Created a bezier curve, baked 255 points, mem usage: 4.08kB, time to bake: 26.30µs. Estimated average calc time: 0.04µs.
[LOG] Creating the ConfigManager!
[LOG] Creating the CHyprError!
[LOG] [hookSystem] New hook event registered: focusedMon
[LOG] [hookSystem] New hook event registered: preRender
[LOG] Creating the LayoutManager!
[LOG] Reloading the config!
[LOG] Created a bezier curve, baked 255 points, mem usage: 4.08kB, time to bake: 16.18µs. Estimated average calc time: 0.03µs.
[LOG] Using config: /home/garuda/.config/hypr/hyprland.conf
[LOG] Created a bezier curve, baked 255 points, mem usage: 4.08kB, time to bake: 16.18µs. Estimated average calc time: 0.03µs.
[LOG] Registered dynamic var "$mainMod" -> SUPER
Failed to acquire service name: File exists
Is a notification daemon already running?
/bin/sh: line 1: exec: xrdb: not found
/bin/sh: line 1: wl-clipboard-history: command not found
Cannot register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
[2023-12-19 14:18:59.072] [info] Using configuration file /home/garuda/.config/waybar/config
[2023-12-19 14:18:59.073] [info] Using CSS file /home/garuda/.config/waybar/style.css
basic_string::_M_create
[2023-12-19 14:18:59.110] [info] Hyprland IPC starting
[2023-12-19 14:18:59.127] [warning] module temperature: Disabling module "temperature", Can't open /sys/class/hwmon/hwmon7/temp1_input
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: CopyQ server is already running.

** (waybar:8083): WARNING **: 14:18:59.294: Status Notifier Item with bus name ':1.7' and object path '/org/ayatana/NotificationItem/nm_applet' is already registered
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--       0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--       0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--       0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--       0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--       0    37    0     0    0     0      0      0 --:--:--  0:00:05 --:--:--     100    37  100    37    0     0      6      0  0:00:06  0:00:05  0:00:01     9

My windows (or tiles?) still look zoomed and weird :sweat_smile:

To be safe, I probably should stick to the .iso no?

Wait, were you doing all this on the live ISO session? The steps were supposed to be taken after installation if you still couldn’t log into your installed Garuda Linux :sweat_smile:
If you can use mod+enter to open the terminal (which should only work if you’re logged in), then there is no point to running Hyprland because you’ll be trying to run Hyprland within Hyprland.

Yes just stick to the ISO file, unless you’d like to check the SHA256sum.

So basically, if you install using the new ISO and then still can’t login, take my steps listed in the other post.

And yes, this is an example of how it should look. However, if the VC Keymap is listed as unset, it is something that can prevent you from logging in as Hyprland doesn’t know how to deal with it and therefore decides dying is the better option :joy:

:sweat_smile: :sweat_smile:Alright. I’ll use the Mod + i to begin installing the Garuda Hyprland.

Afterwards, I’ll take out the USB? right? but I won’t reboot, cuz it’s when I reboot that I am unable to log in.

and then I’ll follow the steps you outlined below as:


To see if this is the issue:

    Change to a different tty by pressing ctrl alt F1-F7 (any will do, you just need the terminal available)
    Type localectl status - if the VC layout is unset, this is the problem that’s not letting you log in
    If it’s unset, use the US layout for now as it will definitely let you login: localectl set-keymap us.

If you ran localectl status and your VC layout was set, then please run Hyprland and see the crash dump file (which should be somewhere in ~/.hyprland). If you have a USB stick mounted then you should be able to copy it there, and then post the contents here :slight_smile:

If it doesn’t work, I’ll pick up the ISO file from the url https://iso.builds.garudalinux.org/iso/community/hyprland/231219/.

Any tips on how to make it bootable. Haven’t done this using the Garuda Hyprland before, only have experience with it using Fedora Media Writer

Yes take out the USB, but no, you need to reboot and try to log into your installed Garuda, otherwise there’s not really any point to this thread, is there? :slight_smile:
After you reboot and boot into your installed Garuda, then run localectl status and see what’s up there. If it looks normal, then it’s time to run Hyprland and get the crash dump.

Also, please try to keep your responses to one post if no one else has responded yet, as this is a forum and not a social chat. If an admin or moderator gets on your case, they won’t be so nice about it :'D
You can edit your posts to do this.

3 Likes

Me: Gently took out the USB and hoped for the best.

Me Again: Log in worked after reboot and I stared at the screen, well over 17 mins waiting for it to crash, not believing the successful log in.

Thank you all so much.
Super grateful for the support here. It helped me in more ways, especially beyond the main issue. I think I might feel at home here.

Thank you once again.
Thank you. :bowing_man: :bowing_man: :bowing_man:

3 Likes

Good to know the problem is solved! :partying_face:
I said it before, but it never hurts to say it a second time: Welcome to the Garuda community! Enjoy your stay here, and have fun with your system! :smiley:

5 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.