GNOME Bugzilla – Bug 426822
hangs while dragging mail, mouse pointer `stuck' in drag mode
Last modified: 2007-04-11 16:22:04 UTC
Steps to reproduce: 1. Drag mail from inbox to subfolder 2. Repeat step 1 several times (works best if these actions overlap, i.e. execute another drag before the first has finished copying files). Also helps if evolution is checking junk mail at the same time. 3. Eventually, the mouse pointer is `stuck' with a `drag' pointer icon (the icon that appears while dragging mail) even when mouse buttons are released. User can no longer click on anything - or even change desktops. (Ctrl+Atl+F1 works, although Ctrl+Alt+Right doesn't) Stack trace: Stack Trace via gdb obtained after killing evolution (it just hung, didn't die by itself): Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread -1233160528 (LWP 21472)] CalDAV Eplugin starting up ... (evolution-2.8:21472): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.8:21472): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution-2.8:21472): DEBUG: mailto URL command: evolution %s ** (evolution-2.8:21472): DEBUG: mailto URL program: evolution [New Thread -1270965344 (LWP 21513)] [New Thread -1279358048 (LWP 21514)] [New Thread -1287750752 (LWP 21515)] [Thread -1287750752 (LWP 21515) exited] [New Thread -1287750752 (LWP 21522)] [New Thread -1296577632 (LWP 21523)] [Thread -1296577632 (LWP 21523) exited] [New Thread -1296577632 (LWP 21531)] (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unhook_event: assertion `CAMEL_IS_OBJECT (obj)' failed (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unhook_event: assertion `CAMEL_IS_OBJECT (obj)' failed (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unhook_event: assertion `CAMEL_IS_OBJECT (obj)' failed (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed [New Thread -1341129824 (LWP 21534)] (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unhook_event: assertion `CAMEL_IS_OBJECT (obj)' failed (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unhook_event: assertion `CAMEL_IS_OBJECT (obj)' failed (evolution-2.8:21472): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution-2.8:21472): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution-2.8:21472): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed [New Thread -1349522528 (LWP 21535)] [Thread -1349522528 (LWP 21535) exited] [New Thread -1349522528 (LWP 21540)] [New Thread -1357915232 (LWP 21541)] (evolution-2.8:21472): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.8:21472): camel-WARNING **: camel_exception_get_id called with NULL parameter. [New Thread -1339802720 (LWP 21554)] DEBUG: INBOX/Subfolrder (imap://xxxx@xxxxxx.xxxxxx.ca/INBOX/Subfolder) report junk?? How is everything Program received signal SIGPIPE, Broken pipe. [Switching to Thread -1287750752 (LWP 21522)] 0xffffe410 in __kernel_vsyscall () Other information:
Happened again - although this time the mouse pointer didn't get stuck (I was just navigating to a subfolder). I suspect what I'm doing doesn't matter so much as what evolution is doing in the background, and I just get different results depending on what I'm doing at the moment the error occurs. This time I got a backtrace through gdb:
+ Trace 125415
Thanks for the bug report. This particular bug appears to be a duplicate of bug 273420 (to be confirmed by the bugsquad), but your backtrace might be useful in the resolution of that bug. Perhaps you could add your backtrace, and any other info you find, to the bug 273420 entry?
Correction to my comment: I meant bug 308354, which is currently still open.
Done. Looks similar enough, so I'll mark this as a duplicate and follow the action over there. *** This bug has been marked as a duplicate of 308354 ***