Betterlockscreen commands take way too much time

[zPhoeniqz]

Is there an existing issue for this?

• [X] I have searched the existing issues

Operating system

Reborn OS (Arch-based)

Installation method

Package Manager (from OS)

Betterlockscreen & Dependency-Versions

Betterlockscreen: version: v4.0.4 (dunst: true, feh: true)
i3lock: version 2.13.c.4 © 2010 Michael Stapelberg, © 2015 Cassandra Fox, © 2021 Raymond Li
Version: ImageMagick 7.1.0-43 Q16-HDRI x86_64 20237 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI Modules OpenCL OpenMP(4.5)
Delegates (built-in): bzlib cairo djvu fontconfig freetype heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png raqm raw rsvg tiff webp wmf x xml zip zlib
Compiler: gcc (12.1)
dunst version: v4.3
Dunst controlling interface not available. Is the version too old?
feh version 3.9
Compile-time switches: curl exif inotify help magic stat64 verscmp xinerama
[B] Betterlockscreen

Bug description

Any betterlockscreen command, e. G. betterlockscreen -h for the help menu takes 25 seconds to complete.

Steps to reproduce

1. Install betterlockscreen from the AUR
2. Run betterlockscreen -h or any other betterlockscreen command

Relevant log output

No response

[boatinalamp]

Hey zphoenix, i have the same problem, have you found a fix yet?

[Absolpega]

i had the same issue, deleting the lines DUNST_INSTALLED=false && [[ -e "$(command -v dunstctl)" ]] && DUNST_INSTALLED=true and DUNST_IS_PAUSED=false && [[ "$DUNST_INSTALLED" == "true" ]] && DUNST_IS_PAUSED=$(dunstctl is-paused) fixed it

[SebTM]

Sounds like misconfiguration env or something, tested both commands individually and combined and take under a second. Can you try this script for measurement if the problem is reproducible with it:

#!/usr/bin/env bash
start_time=$(date +%s)

command -v dunstctl
dunstctl is-paused

end_time=$(date +%s)
printf 'Elapsed time is %d seconds\n' $((end_time - start_time))

You can try comment out each of the commands to measure them individually if only one is the problem.

[dlip]

I tried your command and it took 25 seconds, I installed dunst and it took 0 seconds so i guess i must use dunst

[SebTM]

I've made the test on my machine and uninstalled dunst - still 0 seconds. Which of the commands (try to comment out one and try again) produces the wait time? What bash version are you using bash --version? (My tests were made with GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu))

Can you also provide the OS/Debugging information like ./betterlockscreen -v.

[SebTM]

I'm going to close the issue as can't reproduce and no further information's provided :)

[Absolpega]

I have just reinstalled arch and ran into this issue again.

I am running awesomewm which uses its own notifications daemon. I tried installing dunst for a different WM when I then tried to lock the screen on awesome (without dunst running) it took a really long time as before.

The problem seems to be with dbus-send in dunstctl waiting 25 seconds for a response.