Bug 3166 - make notifications non-blocking
Summary: make notifications non-blocking
Status: RESOLVED WORKSFORME
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Plugins/Notification (show other bugs)
Version: 3.10.0
Hardware: PC Linux
: P3 enhancement
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2014-05-13 20:31 UTC by Pierre Fortin
Modified: 2014-05-29 00:26 UTC (History)
0 users

See Also:


Attachments

Description Pierre Fortin 2014-05-13 20:31:07 UTC
If a notification occurs while composing, input is queued until the notification popup/tooltip completes (no Close/Cancel).  I can type nearly two lines before the notification completes.

I don't recall this being an issue with the old notification plugin.

[PS this is 2nd attempt. First attempt at filing returned:
  First, you must pick a product on which to enter a bug:
which was totally unexpected.  With all the bugzillas I've used over the years, this was a first...  Oh well...]
Comment 1 Holger Berndt 2014-05-14 20:38:03 UTC
It doesn't block here.

What is the "old notification plugin"? Nothing changed there recently.
Comment 2 Pierre Fortin 2014-05-14 21:28:25 UTC
A while back the current plugin replaced what we had, or maybe the default config made it appear to be a replacement...  can't recall...

Can other programs share the notification trayicons?  I need to pay closer attention; but it seems like non-CM notifications also appear at times -- if so, they may be the source of my issue.

I see 2 tray icons for my CM instances. Sometimes I see another "icon" over-layed with a number.  Clicking on it shows me a stack of notifications.  

While doing some testing, saw a CM notification that had a "Presen..." button -- clicked on it and all that happened was the button disappeared.  Any clue what it is? "Presen..." is cryptic since it doesn't appear to do anything. :)

Disabled the Popup and Passive Toaster Popup -- will watch to see if that makes a difference...  BTW, what's the difference between those two? Their configs seem identical.
Comment 3 Holger Berndt 2014-05-15 00:16:17 UTC
The plugin uses the infrastructure defined by the desktop notification specification. That's a client-server infrastructure, with many different server implementations. I don't know what kind of server you're using, or what kind of buttons this server uses. Also, there surely can be other clients besides Claws Mail.

The difference between the popup and the trayicon popup is that the first is freestanding, and the second is a popup attached to the tray icon, see e.g. http://www.claws-mail.org/img/notification/notification_trayicon1.png

(Your server may choose to not attach popups to tray icons but display them also free-floating instead - I can't know.)
Comment 4 Pierre Fortin 2014-05-15 02:19:22 UTC
Thanks Holger!  I'll try running with only the tray popups turned on.  Turns out the CM instance that was giving me problems had both popups enabled -- as long as the standalone popup was displaying (about 5 seconds which is the default timeout (and maybe times N messages?)), the compose window wasn't updating. It would resume with queued keystrokes when the popup disappeared.

I'm using Mageia 4 Linux with KDE4 & Plasma if that helps...
Comment 5 Holger Berndt 2014-05-15 20:56:00 UTC
It's not blocking for me even with both active.
Comment 6 Pierre Fortin 2014-05-29 00:26:12 UTC
I just noticed this message when this issue occurs:

(claws-mail:10177): libnotify-WARNING **: Failed to connect to proxy

Any idea which "proxy" libnotify is trying to connect to?

Note You need to log in before you can comment on or make changes to this bug.