GNOME Bugzilla – Bug 602039
hang trying to add CC
Last modified: 2011-05-20 12:06:22 UTC
I simply tried to add a CC to a message being composed and evolution hung while the CC box "drop-down" was displayed and this in fact locked my mouse focus on evolution while it was hung. Yes. Very, very very bad.
+ Trace 219117
Thread 1 (Thread 0xb7ef6b00 (LWP 5678))
And another, immediately after killing the last instance and trying again...
+ Trace 219118
Thread 1 (Thread 0xb7f45b00 (LWP 19983))
And yet another. When are we going to quit developing new features and eye-candy and whatnot and get back to the basic functionality of evolution, a lot of which is buggy, unreliable and just plain, don't work? Yes, I am frustrated. Yes, I cannot even compose a simple freakin' message and add a simple freakin' contact! I have filed a half a dozen bugs on evo just this weekend alone!
+ Trace 219119
Thread 1 (Thread 0xb7fbcb00 (LWP 21532))
(In reply to comment #2) > And yet another. When are we going to quit developing new features and > eye-candy and whatnot and get back to the basic functionality of evolution, a > lot of which is buggy, unreliable and just plain, don't work? I don't know when you and your team are doing this, but it's up to you to change it (I can't find any other way to interpret your "we").
(In reply to comment #3) > > I don't know when you and your team I don't have a team. The "team" is the evolution team. > are doing this, but it's up to you to > change it (I can't find any other way to interpret your "we"). The use of "we" in that context is a colloquialism that can be interpreted roughly as "you". It's usually interpreted as a less-blame-focused way of addressing a group when one is more interested in making one's point than focusing on the party being addressed. It can also be used in such a fashion as "we are all in this together, in various ways".
I mean seriously... you have to admit, that there are a lot of bugs in evolution, many of them are many years old and are just not getting any attention at all. One very sore spot in general is evolutions lack of ability to recognize that network services fail. So many bugs in evolution are happen when a network service fails to respond, or responds slowly, etc. But let's not digress this ticket into a discussion about other bugs. I was just frustrated and have been so for the last two (at least) evolution releases. It's time to fix bugs. Please.
I see bonobo and Orbit related traces and Evolution doesn't depend on them 2.30.x onwards. Can you please check again whether this issue still happens in Evolution 2.32.2 or 3.0 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Thank you for reporting this bug and we are sorry it could not be fixed for your version.Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!