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.

Sign up for GitHub

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

Jump to bottom

Fix #79 #81

Closed
wants to merge 1 commit into from
Closed

Fix #79 #81

wants to merge 1 commit into from

Conversation

KAMiKAZOW
Copy link
Contributor

Fix #79

@KAMiKAZOW
Copy link
Contributor Author

This is still not a "well formatted" notification as KDE devs would like but the actual problem of the notification getting lost is prevented by --urgency=critical (it shows up in Do Not Disturb mode as well).

On a related note: Why is the notify-send command specified twice?

@hakavlad
Copy link
Owner

On a related note: Why is the notify-send command specified twice?

  1. If started as non-root: run notify-send directly without env.
  2. If started as root: run sudo -u user env notify-send... to notify all logged users.
    See https://github.com/rfjakob/earlyoom#notifications

@hakavlad hakavlad closed this Jan 26, 2020
@hakavlad
Copy link
Owner

I think low memory warnings should not appear in history. I want to set critical urgency only for notifications of terminated processes. Low memory notifications are the same and do not contain uniqe information. I also want to test it better with different DE.

@KAMiKAZOW KAMiKAZOW deleted the patch-4 branch January 26, 2020 10:06
@KAMiKAZOW KAMiKAZOW mentioned this pull request Jan 26, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[KDE] notifications "don't deserve to be in history"
2 participants
@KAMiKAZOW @hakavlad