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 319107 - Evolution hangs while dragging/dropping messages from IMAP inbox to another folder on the same server
Evolution hangs while dragging/dropping messages from IMAP inbox to another f...
Status: RESOLVED DUPLICATE of bug 308354
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other All
: Normal blocker
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-10-17 21:11 UTC by vladanian
Modified: 2005-10-18 05:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description vladanian 2005-10-17 21:11:49 UTC
Please describe the problem:
Periodically, when I drag messages from my IMAP inbox to another folder on the
same IMAP server, evo hangs at the drag portion of the operation. The cursor is
changed to the drag-cursor, but it won't drop the item. I can't do anything in
evo and can't switch away to another app. I've only been able to unhang myself
by killing evo, either from a separate termianl or by ctrl-alt-backspace and
killing X.


Steps to reproduce:
1. Open IMAP account in Evolution 2.4.x (I experienced this issue in 2.2.x as well)
2. Drag one or more message items from inbox to some other folder
3. Pointer will move around but won't do anything else, effectively hanging that
X session


Actual results:
Message doesn't drop, and Evo, pointer and X session are stuck

Expected results:
Message gets dropped where I choose to drop it, and life goes on

Does this happen every time?
No, it only happens periodically, but when I set out to reproduce the bug for
this report, it only took a few minutes of concentrated message-moving activity
to reproduce.

Other information:
The IMAP server is Exchange 2000.  I'm using a thinkpad t41.  I've experienced
this issue on Ubuntu Hoary and Breezy, and on SUSE 10.  My current SUSE 10 evo
package is 2.4.0-3.2.

I ran evolution through gdb, reproduced the error, and this was the output in gdb:

GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i586-suse-linux"...(no debugging symbols
found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /opt/gnome/bin/evolution-2.4
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1096957664 (LWP 17822)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
adding hook target 'source'

(evolution-2.4:17822): camel-WARNING **: camel_exception_get_id called
with NULL parameter.
[New Thread 1144064944 (LWP 17836)]
[New Thread 1146559408 (LWP 17837)]
[New Thread 1148660656 (LWP 17838)]
[New Thread 1151044528 (LWP 17839)]
[Thread 1151044528 (LWP 17839) exited]

(evolution-2.4:17822): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion
`GDK_IS_GC (gc)' failed
[New Thread 1151044528 (LWP 17840)]
[New Thread 1191451568 (LWP 17841)]
[New Thread 1193552816 (LWP 17843)]
[New Thread 1195654064 (LWP 17844)]
[Thread 1191451568 (LWP 17841) exited]

(evolution-2.4:17822): camel-WARNING **: camel_exception_get_id called
with NULL parameter.
[New Thread 1191451568 (LWP 17845)]
[Thread 1191451568 (LWP 17845) exited]

(evolution-2.4:17822): camel-WARNING **: camel_exception_get_id called
with NULL parameter.

(evolution-2.4:17822): camel-WARNING **: camel_exception_get_id called
with NULL parameter.

Program received signal SIGTERM, Terminated.
[Switching to Thread 1096957664 (LWP 17822)]
Comment 1 vivek jain 2005-10-18 05:08:45 UTC

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