| Summary: | when running via su|ssh, CM stalls for 60 seconds on each received message | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Claws Mail (GTK 2) | Reporter: | Pierre Fortin <pf> | ||||||||||
| Component: | Plugins/Notification | Assignee: | users | ||||||||||
| Status: | RESOLVED INVALID | ||||||||||||
| Severity: | normal | ||||||||||||
| Priority: | P3 | ||||||||||||
| Version: | 3.17.2 | ||||||||||||
| Hardware: | PC | ||||||||||||
| OS: | Linux | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1917 [details]
--debug output of test message processing
Patched CM instance 2 to add timestamps (except plugins).
This output shows 2 test messages arriving in different polls.
The first was sent by mailx and the 2nd from CM instance 1.
Message from:
mailx: no delay in processing
CM: 60 second hang
The full contents of these 2 messages are included at the end of this file.
as was already suggested on the mailing list, disable the notification plugin as it is libnotify that appears to be causing the delay. Created attachment 1918 [details]
modified debug output
Continued testing. Added various debug_print statements and discovered 60 second delay is really 35 seconds and 25 seconds.
Created attachment 1919 [details]
debug output
Correction: 80s = 25s + 25s + 10s
Found the 25+25+10 second delays; but I don't know how to fix these; yet...
The first 25 second delay occurs in notification_trayicon.c:662
caps = notify_get_server_caps();
which is getting a GList and looking for "actions".
Added notify_is_initted() test which returns TRUE just before that call.
The second 25 second delay occurs in notification_trayicon.c:739
if(!notify_notification_show(popup.notification, &(popup.error))) {
The 10 second delay occurs in notification_trayicon.c:743
g_object_unref(G_OBJECT(popup.notification));
|
Created attachment 1916 [details] debug output I run 2 instances of CM (only POP3), one on my primary Linux account and another via "su - userid2" (or "ssh userid2@localhost"). On the main instance, incoming messages are checked and all seems fine. On the 2nd instance, when mail arrives, I'm seeing long delays where CM is totally unresponsive. Ran with --debug which confirms 60 second delay -- see comments in debug output. For this test, I started CM and waited until it began polling on its own.