Hyprlock service failed with "core-dump"

[goldsphere48]

I've created service for launching hyprlock on system startup:

[Unit]
Description=Hyprlock Display Manager
After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service

[Service]
ExecStart=/usr/bin/hyprlock --hyprland
Restart=always
IgnoreSIGPIPE=no
KillMode=process
RestartSec=2

[Install]
WantedBy=getty.target
Alias=display-manager.service

Then I'am doing:

sudo systemctl enable hyprlock.service
sudo systemctl start hyprlock.service
reboot
sudo systemctl status hyprlock.service

Firstly, I have no hyprlock screen on start. And status give an error: sudo systemctl enable hyprlock.service.

coredumpctl dump result is:

PID: 2531 (hyprlock)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Sun 2024-03-24 15:32:12 +10 (1s ago)
  Command Line: /usr/bin/hyprlock --hyprland
    Executable: /usr/bin/hyprlock
 Control Group: /system.slice/hyprlock.service
          Unit: hyprlock.service
         Slice: system.slice
       Boot ID: 22e1602a634b41a5a8933e2436cca95f
    Machine ID: 33e33da2c24840ceb63744d7cb31e519
      Hostname: archpc
       Storage: /var/lib/systemd/coredump/core.hyprlock.0.22e1602a634b41a5a8933e2436cca95f.2531.1711258332000000.zst (inaccessible)
       Message: Process 2531 (hyprlock) of user 0 dumped core.

                Stack trace of thread 2531:
                #0  0x000074c3fc977fdd n/a (libc.so.6 + 0x159fdd)
                #1  0x00005c42cbf3a20b n/a (hyprlock + 0x4020b)
                #2  0x00005c42cbf0fb77 n/a (hyprlock + 0x15b77)
                #3  0x00005c42cbf08064 n/a (hyprlock + 0xe064)
                #4  0x000074c3fc843cd0 n/a (libc.so.6 + 0x25cd0)
                #5  0x000074c3fc843d8a __libc_start_main (libc.so.6 + 0x25d8a)
                #6  0x00005c42cbf0adc5 n/a (hyprlock + 0x10dc5)
                ELF object binary architecture: AMD x86-64

My system is Arch Linux.

[vaxerski]

build hyprlock from source in debug, that stacktrace is useless

[mooncoffee1]

maybe after hyprlock, another cool idea its to have a DM ? like lightdm, or sddm, honestly, sddm is trash, starts xorg with it, if u run htop u will see xorg there too, but if u launch hyprland from tty, no xorg process, thats bc sddm runs on xorg ig, shit. HyprDM, sounds a good idea

[vaxerski]

no

[mooncoffee1]

no

sed, i think you are skilled enough to do it, but u dont want ;(

[vaxerski]

correct

[mooncoffee1]

correct

sussy baka, just do it, we will do anything -_-

[rafal11ck]

Also on Arch Linux after launch

[ERR] Config has errors:
Config error in file /home/rafal/.config/hypr/hyprlock.conf at line 40: config option <input-field:swap_font_color> does not exist.
Proceeding ignoring faulty entries
...

After unlocking:

[LOG] auth: authenticated for hyprlock
[LOG] Unlocking session
[LOG] Unlocked, exiting!
[LOG] Reached the end, exiting
Aborted (core dumped)

full log.txt

I experienced above only in version from arch repo.

I compiled from source and neither of above happened.

Instead I get following

[LOG] Unlocking session
[LOG] Unlocked, exiting!
[LOG] Unlocking session
[ERR] Unlock already happend?
[TRACE] timer thread firing
[LOG] Reached the end, exiting

log.txt

[vaxerski]

please try on -git

[rafal11ck]

Same result as when compiled from source manually.

log: hyprlock-git.txt

[PaideiaDilemma]

The "[ERR] Unlock already happend?" is fine but ideally should not happen. But you can ignore it. Has no effect on the usage or anything else really.