Summary: | claws-mail notification plugin miscounts new messages | ||||||
---|---|---|---|---|---|---|---|
Product: | Claws Mail (GTK 2) | Reporter: | Mike Kelly <pioto> | ||||
Component: | Plugins/Notification | Assignee: | users | ||||
Status: | NEW --- | ||||||
Severity: | normal | CC: | d.bedrenko, netuse | ||||
Priority: | P3 | ||||||
Version: | other | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Attachments: |
|
As a further bit of information, the tooltip on the system tray icon has the right counts. Just the libnotify popup is wrong. A quick addition of debug code seems to indicate that popup_timeout_fun is not being called, as far as I can tell, which would cause the trouble I'm seeing. I'll see if I can find out why it isn't. I can confirm that this bug is reproducible on Arch Linux too with Claws 3.7.6 and version 0.25 of the notification plugin. Confirmed on Ubuntu with claws mail 3.7.6 and plugin version 0.25 Bug is reproducible on ArchLinux, Claws v3.9.2. What are the exact steps to reproduce then? 1. Start Claws (as restarting claws resets the "new" messages counter). 2. Receive an email (or send one to yourself) and the libnotify popup displays all the details of the message: "New Mail message [FROM_NAME] <[FROM_ADDRESS]> [SUBJECT] [EMAIL FOLDER]" 3. Close the popup. 4. Read the message so that it becomes "un-new" and unread. 5. Receive a second message and the libnotify popup wrongly displays: "Mail message 2 new messages arrived" This is wrong because in my folder list I can see only a single "new" message. 6. Read this second message to make it "un-new". 7. Receive another email and the popup will say "3 new messages arrived" and so on. ---------- I hope this is what you wanted; let me know if you need anything else. Same on Debian 7.9 and 3.13.1. Is it possible to set the "Platform" metadata field of this bug to include linux? It may be that developers are not giving this priority as they believe it doesn't affect many users, as BSD has far fewer users. (In reply to comment #9) > Is it possible to set the "Platform" metadata field of this bug to include > linux? It may be that developers are not giving this priority as they > believe it doesn't affect many users, as BSD has far fewer users. It's mentioned in the title also. (In reply to comment #10) > (In reply to comment #9) > > Is it possible to set the "Platform" metadata field of this bug to include > > linux? It may be that developers are not giving this priority as they > > believe it doesn't affect many users, as BSD has far fewer users. > > It's mentioned in the title also. Not that those things speed up fixing things here, but done ;-) |
Created attachment 875 [details] [NotificationPlugin] part of my clawsrc There seems to be some sort of a bug with your notification plugin. I am on FreeBSD, and it seems that it the notifications don't know how to count. The count of unread messages just seems to increase, but never go back down when I actually read a message. For example, I could start of claws with no unread mail. I get one message, I get the libnotify notice for a single message. Then, I read that message. Then, I get another message, and rather than just showing that single message, it says I have 2 unread messages. And so on. Restarting claws seems to reset the counter. I don't seem to have this problem on my linux box at home, just on my freebsd box at work. Any suggestions? I'm using claws-mail-3.7.6_1 and claws-mail-notification-0.25_1 from FreeBSD ports. I've attached the relevant snippet of my clawsrc in case that's helpful.