Skip to content
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

[BUG] Notifications disappear immediately. #248

Open
not-night-but opened this issue Jan 30, 2024 · 4 comments
Open

[BUG] Notifications disappear immediately. #248

not-night-but opened this issue Jan 30, 2024 · 4 comments

Comments

@not-night-but
Copy link

not-night-but commented Jan 30, 2024

Just started trying out deadd, and I'm loving it so far. My only gripe is that notifications get dismissed less than a second after they are received. My default timeout is set to 10000ms and raising that number doesn't seem to have an effect. I've also tried a match/modify rule to force the notification to stay until dismissed, but no joy. This doesn't happen using dunst so I'm assuming it's an issue with deadd or something to do with my setup specifically (if the latter is the case, no worries, I'll soldier on).

I'm on Garuda Linux using bspwm. I installed deadd using the deadd-notification-center-git package in the chaotic-aur.

Thanks in advance for any help you can send my way.

@phuhl
Copy link
Owner

phuhl commented Feb 8, 2024

Hi, thanks for the report. When you say dismissed, do you mean the popup disappears?

@not-night-but
Copy link
Author

@phuhl yeah the popup disappears. Still visible in the notification center, but my expectation was that the popup would stay for the timeout length, unless that assumption was wrong?

@phuhl
Copy link
Owner

phuhl commented Feb 8, 2024

That's strange. Is it happening with all notifications? Can you share your config?

@TheStutterNerd
Copy link

TheStutterNerd commented Oct 1, 2024

Comment before edit

I've just updated to the latest version. Happening to me too. Same story when using default config.

I hadn't known the config had changed to using yaml so it were either using the defaults or it wasn't using any config at all. Would have been nice if it gave a warning if an older 'deadd.conf' existed.

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

No branches or pull requests

3 participants