emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: org-notify dbus send message to KDE/Plasma caused desktop suspend
Date: Wed, 11 Sep 2019 16:51:22 -0500	[thread overview]
Message-ID: <87blvqec2t.fsf@alphapapa.net> (raw)
In-Reply-To: CAL1eYuJAg-nyu4rF5iBgrZE7d0=ugqyoGvg1OVgSwshKWJXP5g@mail.gmail.com

"numbchild@gmail.com" <numbchild@gmail.com> writes:

> org-notify dbus send message to KDE/Plasma caused desktop suspend and high CPU,memory resources.
>
> Here is my config:
> ```elisp
> (setq org-notify-audible nil)
> (org-notify-add 'default
>                 '(:time "1h" :period "1h" :duration 8
>                         :actions (-ding -notify/window)
>                         :audible t))
> (org-notify-start (* 60 2))
> ```
>
> When I have about 10 deadline tasks to be reminded at once, dbus suspend desktop soon because send dbus message too fast?
>
> Maybe add a sequence delay to improve this situation?

That workaround might be helpful, but it sounds like a bug somewhere
else in the Plasma/dbus/etc. stack.  I recommend trying to reproduce it
with e.g. the notify-send shell command; if you can, you'll know the bug
isn't with Emacs/Org.

I recommend filing a bug report with KDE, or perhaps with your Linux
distro as a first step.

By the way, I'm not sure what you mean by "desktop suspend."  The word
"suspend" is typically used to mean putting the system into a low-power
sleep state, but I'm guessing you mean that some part of the Plasma UI
is freezing and causing high CPU usage.

  reply	other threads:[~2019-09-11 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  1:02 org-notify dbus send message to KDE/Plasma caused desktop suspend numbchild
2019-09-11 21:51 ` Adam Porter [this message]
2019-09-13 23:40   ` numbchild

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blvqec2t.fsf@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).