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 337689 - Mouse pointer gets stuck as "moving" cursor... Evolution stops responding
Mouse pointer gets stuck as "moving" cursor... Evolution stops responding
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-04-08 00:30 UTC by Richard Laager
Modified: 2008-10-31 13:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
Backtrace as requested (8.02 KB, text/plain)
2006-06-18 13:48 UTC, Øystein Gisnås
Details
backtrace (7.14 KB, text/plain)
2006-06-19 23:26 UTC, Richard Laager
Details
backtrace #2 (10.40 KB, text/plain)
2006-06-19 23:26 UTC, Richard Laager
Details

Description Richard Laager 2006-04-08 00:30:59 UTC
Steps to reproduce:
1. Move a message to a folder. Make sure the move will take some time. This
means you should move between local folders with lots of messages, or between
remote folders (via IMAP, for example).
2. 
3. 


Stack trace:
Perhaps I shouldn't have filed this as a crasher. It's not segfaulting, but it
does hang. This leads to Evolution being unresponsive. Clicks to other windows
don't work either, making this far worse than a crash. All I can do is kill X,
or switch to a VT and kill evolution.

Other information:
I've had this problem on Evolution in Fedora Core 4 (version 2.2 or 2.4, I'm not
sure which... but whatever is the latest package in FC4), and now in Ubuntu
Dapper (which has version 2.6.. It happens in both "slow move" (large amounts of
messages in local folders, and via IMAP folders).
Comment 1 Richard Laager 2006-04-08 00:33:15 UTC
Oops! Missed the other steps. After step 1, it's...

2. Try to move another message.

Under some conditions (it doesn't happen always), the mouse pointer gets stuck as the message drag-n-drop cursor. I believe it happens when the first move operation completes while I'm still dragging the second message.
Comment 2 Richard Laager 2006-04-10 18:41:30 UTC
Now that I'm using IMAP folders, I'm seeing this far more often than I did with local folders. This hits me every day. Granted, I can learn to move messages slower, but it'd be nice if this could be fixed.
Comment 3 Jeffrey Stedfast 2006-04-10 18:48:47 UTC
agreed :)
Comment 4 Poornima 2006-04-27 13:35:12 UTC
I am using evolution 2.6.1. I am trying to replicate this scenario, I am not seeing any evolution hang.
First of all I feel this is not a critical bug, filters are generally used to move mails to required folder and it looks like a random bug. So lowering priority of the bug to 'Major'.
Anway confirming this bug as 'fell' agrees.
Comment 5 Richard Laager 2006-04-27 14:53:15 UTC
I'm using 2.6.1 and I hit this on average twice daily. It totally prevents me from being able to use any X apps until I switch to a terminal, killall evolution, and switch back. I really think this is a critical bug.

As for filters... I'm hitting this because I move all of my mail to an archive folder when I'm done with it.
Comment 6 Øystein Gisnås 2006-05-08 06:41:23 UTC
This exact same problem is also a serious annoyance for Debian users. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280775

I think Poornima's assumption that everyone filter their mail into folder is wrong. That is for mailing lists and such. If you receive in your INBOX and archive in another folder, that would be either a DnD or Ctrl-Shift-V or similar.

It doesn't render evolution useless, but is still something I'd like to see fixed.
Comment 7 André Klapper 2006-06-17 23:10:57 UTC
would be nice if anyone could provide a gdb stacktrace and attach it to this report.
for more information, see http://www.gnome.org/projects/evolution/bugs.shtml section "Debugging Evolution's Crashes (Getting a backtrace)" - run "gdb evolution", type "run", when evo freezes, hit "control+c" and then enter "thread apply all bt".
thanks in advance.

crashers and freezers are always critical bugs. fullstop.
Comment 8 Øystein Gisnås 2006-06-18 13:48:01 UTC
Created attachment 67574 [details]
Backtrace as requested

On #evolution, Andre gave a clue about workaround that's worth mentioning here. Add 'Option  "AllowDeactivateGrabs"  "yes"' to the ServerFlags section of your xorg.conf file. Then you're able to press Ctrl-Alt-/ (Keypad-Divide) to release the cursor when it's locked. Then you'll be able to kill evolution without switching to console.
Comment 9 André Klapper 2006-06-18 18:01:12 UTC
refering to comment #8: cortana gave that clue, not me. :-)
Comment 10 Richard Laager 2006-06-19 23:26:24 UTC
Created attachment 67660 [details]
backtrace
Comment 11 Richard Laager 2006-06-19 23:26:35 UTC
Created attachment 67661 [details]
backtrace #2
Comment 12 Jeffrey Stedfast 2006-06-20 15:09:13 UTC
looks related to https://bugzilla.novell.com/show_bug.cgi?id=186322
Comment 13 Øystein Gisnås 2006-06-20 17:45:57 UTC
Can't really access that bug report, but. Is that also somewhere in GNOME bugzilla?
Comment 14 Jeffrey Stedfast 2006-06-22 18:53:39 UTC
no, it's just an internal Novell bug report about the same issue (afaict).

might be a gtk drag&drop bug? *shrug*
Comment 15 Ross Golder 2006-07-08 14:44:54 UTC
This has been happening at least twice a day for me now for months - I use IMAP
a lot.

The stacktrace suggests to me that there might be some kind of race condition
between two threads in libcamel. I'll try to build evolution with debugging
symbols and get a more detailed stacktrace at some point.
Comment 16 Milan Crha 2007-08-03 14:34:12 UTC
Is this still a problem? Somehow I could not reproduce it. I tried to get 310 messages into local store from IMAP and then back, it takes long while, but didn't stuck. Even when I moved to the other folder and move other messages in other folder, it didn't stuck.
Could you try it on actual Evolution 2.11.6.1 or better, please?
Comment 17 André Klapper 2007-08-03 21:04:31 UTC
@milan: we can't ask average users to compile an unstable bleeding edge version from svn.
would be cool if richard has the knowledge and will to do this (i just don't know) or is running a distro providing GNOME 2.19.x packages, but *in general* we can't expect our reporters to be advanced users...
Comment 18 Christopher Warner 2007-08-04 14:31:58 UTC
I think this to be related to gtk and the speed at which a IMAP server responds even though I haven't seen it in operation in any other program. There are very few other programs where I'm using this combo of widgets to move stuff around. To reproduce the bug you can to select all, drag slow, normally when i'm looking for the folder to move to. Drop; stuck.

Haven't done it in a while however and haven't noticed this bug in a while.. The IMAP piece comes if the server doesn't respond or responds inappropriately and evo borks. I was looking into this a while ago but using 2.10.1 ubuntu packages I haven't seen it.
Comment 19 Scott Jackson 2007-11-20 18:11:35 UTC
This bug has been plaguing me for almost a year now. I hope it will be considered with reasonably high priority because it renders my workstation unusable. I have to find another workstation and ssh in to kill evolution. Same exact MO. I am on Fedora Core 6 and running evolution-2.8.2.1-3.fc6. This happens nearly every day and frequently several times a day. Let me know if I can provide any helpful info.
Comment 20 Milan Crha 2007-11-20 18:38:39 UTC
I guess the fix from bug #351672 can help you, but it's included in Fedora 8 only, because it is in 2.12.
Comment 21 Kandepu Prasad 2008-08-06 10:56:13 UTC
The patch given in above bug should already be there in Evolution 2.22.x. Can you please try with latest stable Evolution 2.22.3.1? TIA.
Comment 22 Akhil Laddha 2008-10-31 13:05:42 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.24.x or later), please reopen. thanks in advance.