crash during folder move exchange->this_computer

[indium]

Binary package hint: evolution

When drag-and-dropping folders with emails and subfolders from an Exchange 2003 account to "This Computer", Evolution crashes in ~50% of the situations.

Also, moving of a folder with 1 sub folder and less than 100 small emails can take minutes.

Moving such a 'folder-structure' back to the exchange server doesn't work at all: it never ends and two messages are displayed in the bottom status line: "storing folder (100% complete)" and "generating message list (0% complete)".

I'm running ubuntu 10.10 on a Macbookpro 6,2.

Maybe someone can try to reproduce this.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu7.2
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Wed Jan 5 14:39:50 2011
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: evolution
XsessionErrors: (polkit-gnome-authentication-agent-1:1834): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[indium (indium)]

Dear Pedro,

we have moved to exchange 2010, so I cannot reproduce this bug anymore.
Please close it indeed.

On 02/06/11 22:14, Pedro Villavicencio wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. However, your crash report is either missing or
> challenging to deal with as a ".crash" file. Please follow these
> instructions to have apport report a new bug about your crash that can
> be dealt with by the automatic retracer.
>
> If you are running the Ubuntu Stable Release you might need to enable
> apport in /etc/default/apport and restart.
>
> Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
> If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.
>
> I'm closing this bug report since the process outlined above will
> automatically open a new bug report which can then dealt with more
> efficiently. Thanks in advance for your cooperation and understanding.
>
> ** Changed in: evolution (Ubuntu)
> Status: New => Invalid
>