Evolution stops functioning when moving a message followed by clicking on an unread message.

[Brian Neltner]

I can reproduce this bug in Ubuntu 12.10 using Evolution 3.5.5 by taking the following steps:

Move a message to a different folder or sub-folder.
Immediately click on an unread message.

After doing this, you will still be able to interact with Evolution, click on messages, access the menus, etc. However, the bottom bar will show a ton of status updates and each time you click it will start a new one. However, the first one never resolves and the message is never moved. Meanwhile, new mail will not be downloaded.

I found similar behavior when printing (which doesn't work at all for me for some reason). It says it is printing, and then refuses to complete any other action until the printing is finished. Even clicking the stop button on those status actions just makes them show (cancelling) next to the message, but it never actually cancels. Additionally, Evolution will refuse to go offline, and will refuse to close.

The only way I have found to recover is to kill evolution with -9. Regular kill does not do it.

Definitely a regression compared to the version in 10.04 and 11.10. Not sure about 12.04.

Because this happens for a wide variety of tasks, it may already have been reported, but I do not know what exactly to search for. Sorry if it is a duplicate, but it is quite frustrating.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: evolution 3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Mon Aug 20 17:47:43 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724.3)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

[Brian Neltner (neltnerb)]

This has fixed the problem for me.

Thanks, rock star!

[Brian Neltner (neltnerb)]

Oops, spoke too soon. This fixed the behavior I specified above in most cases, but it still happens when I move an email with an attachment and then view a new message. Unless the fix hasn't been released to the repositories yet, in which case I haven't actually tested it.

Sorry!

[Brian Neltner (neltnerb)]

Changed the status to "New", because I think I incorrectly put it to "In Progress" when it is still unassigned and so obviously not being worked on. Sorry about that!