Skip to content

Betterlockscreen delays and shows freedesktop.DBUS error in awesomewm #284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
arionrefat opened this issue Aug 20, 2021 · 13 comments
Closed

Comments

@arionrefat
Copy link

arionrefat commented Aug 20, 2021

It does work in i3wm, qtile and dwm on the same system

image

@SebTM
Copy link
Collaborator

SebTM commented Aug 20, 2021

Hey, it seems that your dunst-setup is not completely working, could you try the following command used by Betterlockscreen:

dunstctl is-paused
dunstctl set-paused true
dunstctl set-paused false

And also please post the output of "./betterlockscreen -v" :)

@arionrefat
Copy link
Author

Here are the output of the dunstctl commands
image

@arionrefat
Copy link
Author

arionrefat commented Aug 21, 2021

Now, I use i3wm, dwm, qtile and awesomewm. I use dunst for i3wm and dwm. For qtile I use the builtin notification widget and for awesomewm I use the builtin notification module(naughty). Therefore when I'm in awesomewm or in qtile, dunst in turned off. But only in awesomewm the following problem persists. In qtile it works fine, despite I don't use dunst there also.

@arionrefat
Copy link
Author

Here is the output of ./betterlockscreen -v
image

@SebTM
Copy link
Collaborator

SebTM commented Aug 21, 2021

Okay, I understand, will think about a solution for that - if you have an idea I'm open for it :)

@arionrefat
Copy link
Author

Sure, Thanks.

@SebTM
Copy link
Collaborator

SebTM commented Aug 21, 2021

Would it help you, introducing a new option dunst_enabled which besides DUNST_INSTALLED would be checked if dunst should be handled by Betterlockscreen? So you could set this in betterlockscreenrc with a shell-expression you like to, to determinate if dunst is used/usefull and set true if so?

@SebTM SebTM removed the question label Aug 21, 2021
@arionrefat
Copy link
Author

That's really a great idea, Yes, that would really help me.

SebTM added a commit that referenced this issue Sep 17, 2021
…ults twice

* Change declaration of lockargs with "-n" as default because currently we always launch in "non-forking" mode. This makes lockargs also overwritable/extendable in config/hooks. (#188)
* Add $dunst_enabled to let user in config (on runtime) determinate if dunst is enabled in current environment (#284)
* Improve pre & post-Lock to call user-hooks (#245)
* Fixed bug displaying keyboard-layout even when "--show-layout" is not present (#279)
* Bugfix for displays set to higher DPI (thanks to @jeffmhubbard - #287)
* Migrated suspend-command to config for easier adjustments (#137, #174)
@SebTM SebTM mentioned this issue Sep 17, 2021
@gianmarcogg03
Copy link

So did you fix this yet? If yes how do I actually get it to stop doing this with awesome?

@SebTM
Copy link
Collaborator

SebTM commented May 27, 2022

Sorry, haven't had time to work on this - but there is a somehow functioning demo implementation you could adjust for your needs in the Next-PR :)

@nullbyto
Copy link

I have the same issue with AwesomeWM, no problems with Qtile tho. I don't understand what causes that ? Any fixes yet ?

@nullbyto
Copy link

nullbyto commented Aug 12, 2022

I found a workaround in #1285 to disable naughty in awesome.
Add this to rc.lua

package.loaded["naughty.dbus"] = {}

This will make dunst work normally and also betterlockscreen.

SebTM pushed a commit that referenced this issue Oct 9, 2022
…ly we always launch in "non-forking" mode. This makes lockargs also over-writable/extendable in config/hooks. (#188)

* Add $dunst_enabled to let user in config (on runtime) determinate if dunst is enabled in current environment (#284)
* Improve pre & post-Lock to call user-hooks (#245)
* Fixed bug displaying keyboard-layout even when "--show-layout" is not present (#279)
* Bugfix for displays set to higher DPI (thanks to @jeffmhubbard - #287)
* Migrated suspend-command to config for easier adjustments (#137, #174)
SebTM pushed a commit that referenced this issue Oct 9, 2022
…ly we always launch in "non-forking" mode. This makes lockargs also over-writable/extendable in config/hooks. (#188)

* Add $dunst_enabled to let user in config (on runtime) determinate if dunst is enabled in current environment (#284)
* Improve pre & post-Lock to call user-hooks (#245)
* Fixed bug displaying keyboard-layout even when "--show-layout" is not present (#279)
* Bugfix for displays set to higher DPI (thanks to @jeffmhubbard - #287)
* Migrated suspend-command to config for easier adjustments (#137, #174)
SebTM pushed a commit that referenced this issue Oct 9, 2022
…ly we always launch in "non-forking" mode. This makes lockargs also over-writable/extendable in config/hooks. (#188)

* Add $dunst_enabled to let user in config (on runtime) determinate if dunst is enabled in current environment (#284)
* Improve pre & post-Lock to call user-hooks (#245)
* Fixed bug displaying keyboard-layout even when "--show-layout" is not present (#279)
* Bugfix for displays set to higher DPI (thanks to @jeffmhubbard - #287)
* Migrated suspend-command to config for easier adjustments (#137, #174)
SebTM pushed a commit that referenced this issue Oct 9, 2022
…ly we always launch in "non-forking" mode. This makes lockargs also over-writable/extendable in config/hooks. (#188)

* Add $dunst_enabled to let user in config (on runtime) determinate if dunst is enabled in current environment (#284)
* Improve pre & post-Lock to call user-hooks (#245)
* Fixed bug displaying keyboard-layout even when "--show-layout" is not present (#279)
* Bugfix for displays set to higher DPI (thanks to @jeffmhubbard - #287)
* Migrated suspend-command to config for easier adjustments (#137, #174)
@SebTM
Copy link
Collaborator

SebTM commented Dec 26, 2022

@nullbyto Thanks for pointing out - I've included the solution in the readme so it should be easy to find for future users. I would close the issue for now, please let me know if there is anything else :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants