After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 408471 - Evolution hangs X11 while attempting a drag and dropping emails to folders
Evolution hangs X11 while attempting a drag and dropping emails to folders
Status: RESOLVED DUPLICATE of bug 351672
Product: evolution
Classification: Applications
Component: Mailer
2.8.x (obsolete)
Other Linux
: Normal blocker
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-02-16 02:11 UTC by Martin Sevior
Modified: 2008-01-20 20:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
gdb backtrace (31.85 KB, text/plain)
2007-03-07 00:07 UTC, Nick Stoughton
Details
backtrace after the X11 hang (438 bytes, text/plain)
2007-03-07 04:44 UTC, Martin Sevior
Details

Description Martin Sevior 2007-02-16 02:11:16 UTC
If you drag and and drop emails from the current open folder to another in the side pane you can cause X11 to hang if you do the drag and drop too fast. It appears the bug is triggered if an update of the UI has not been completed before a new drop attempt is offered. I think the bug could also be triggered if the message is dropped between different folders.

The only way to recover is to log into a different consol and manually killall evolution.

I have around 1.9 GB of mail on a locally connected imap server.
Comment 1 Veerapuram Varadhan 2007-02-26 22:27:55 UTC
(In reply to comment #0)
> If you drag and and drop emails from the current open folder to another in the
> side pane you can cause X11 to hang if you do the drag and drop too fast. It
> appears the bug is triggered if an update of the UI has not been completed
> before a new drop attempt is offered. I think the bug could also be triggered
> if the message is dropped between different folders.
> 
> The only way to recover is to log into a different consol and manually killall
> evolution.
> 
> I have around 1.9 GB of mail on a locally connected imap server.
> 
Can you get a gdb trace, before killing the process?
Comment 2 Nick Stoughton 2007-03-06 23:32:40 UTC
This looks like a dup of bug 308354 ... see comments there also.
Comment 3 Nick Stoughton 2007-03-07 00:07:27 UTC
Created attachment 84128 [details]
gdb backtrace

gdb backtrace for each of the 9 threads ...
Comment 4 Martin Sevior 2007-03-07 04:44:26 UTC
Created attachment 84140 [details]
backtrace after the X11 hang

I haven;t tried to do much drag and dropping for a while, but I did today and hung X11 as usual. Here is the backtrace.
Comment 5 Martin Sevior 2007-03-07 04:45:13 UTC
Backtrace after connecting to the evo that hung X11 is attached.
Comment 6 Veerapuram Varadhan 2007-03-12 08:37:24 UTC
Moving the priority of the bug to Critical from blocker and moving target to the next stable dot release.  Mailer team is working on it - though, not easily reproducible, we are trying to fix using the comments mentioned in bug#408471.
Comment 7 Nick Stoughton 2007-03-12 16:17:52 UTC
It is in fact fairly easy to reproduce if you have a somewhat slow IMAP server. If you drag and drop a message from your INBOX (or any IMAP folder) to another folder (also on the IMAP server), then do the same thing again BEFORE the first move is complete, you will get the hang. 

If the mail mail index pane get updated by one thread while you are dragging and dropping another different item, you will get the freeze.

If new mail arrives in the displayed folder while you are dragging and droppping, you will get the freeze.

If your junk mail filters remove something from the displayed folder while you are dragging and dropping, you will get the freeze.

Basically, if the mail index window is updated while you are in the midst of d-n-d you will get this freeze.
Comment 8 Martin Sevior 2007-08-27 07:17:34 UTC
This is a really, really bad bug. You guys have got to fix it. My University is currently doing an email migration and the word is out to not drag and drop emails into folders because of evolution is known to hand the computer.

This is worse than a crash on drag and drop.
Comment 9 Srinivasa Ragavan 2007-08-28 19:36:14 UTC
I think it is same as bug #351672
Comment 10 Milan Crha 2007-09-12 09:36:53 UTC
I agree with Srini, it looks similar and because the second bug's patch is in trunk, then if Martin could not reproduce this bug, (he probably could not with that applied patch) then this is solved too.
Martin, are you able to try to reproduce with actual Evolution? (like 2.11.92 2007-09-03 where the patch is included.)
Comment 11 Martin Sevior 2007-09-12 10:43:30 UTC
I haven't yet tried evo 2.11.92 or later.

I'll build it tomorrow to see if the bug is still present.
Comment 12 Srinivasa Ragavan 2007-10-05 06:06:28 UTC
Just test it with 2.12 and close it if it works
Comment 13 Christopher Beland 2008-01-18 17:26:44 UTC
I'm still able to experience this problem with evolution-2.12.2-2.fc8 for Fedora 8. I did selected multiple messages at the same time to make sure that the system was slowed down enough for me to DnD another message before it finished with the
first batch.

This looks like a duplicate of bug 308354 and bug 351672.
Comment 14 Martin Sevior 2008-01-18 22:46:38 UTC
Yes. I confirm that this bug still exists in Fedora 8 but it is now harder to trigger. However the general rule is the if the remote folder is on an imap server and it is still digesting a previous drag of of message then another attempt to drag and drop a message triggers the bug.
Comment 15 Srinivasa Ragavan 2008-01-20 20:17:20 UTC

*** This bug has been marked as a duplicate of 351672 ***