GNOME Bugzilla – Bug 586520
Crash in camel_folder_change_info_add_uid at camel-folder.c line 2465
Last modified: 2010-04-27 11:07:16 UTC
What were you doing when the application crashed? Tagging all messages from a just moved folder with a custom tag Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.29-2-686 #1 SMP Sun May 3 12:46:00 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 268554240 vsize: 268554240 resident: 131940352 share: 21508096 rss: 131940352 rss_rlim: 18446744073709551615 CPU usage: start_time: 1245580060 rtime: 19434 utime: 19099 stime: 335 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb62ae770 (LWP 20596)] [New Thread 0xaaefeb90 (LWP 21410)] [New Thread 0xb11eab90 (LWP 21409)] [New Thread 0xb2c01b90 (LWP 20867)] [New Thread 0xa9efcb90 (LWP 20865)] [New Thread 0xaa6fdb90 (LWP 20864)] [New Thread 0xb349eb90 (LWP 20821)] [New Thread 0xb22ffb90 (LWP 20820)] [New Thread 0xb3402b90 (LWP 20619)] [New Thread 0xb3db7b90 (LWP 20618)] [New Thread 0xb45b8b90 (LWP 20615)] [New Thread 0xb5a63b90 (LWP 20613)] (no debugging symbols found) 0xb8078424 in __kernel_vsyscall ()
+ Trace 216107
Thread 1 (Thread 0xb62ae770 (LWP 20596))
----------- .xsession-errors (117 sec old) --------------------- DEBUG: CXWindowsClipboard.cpp,348: close clipboard 1 camel-Message: -- Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect Avertissement du gestionnaire de fenêtres : Attempt to perform window operation 20 on window none when operation 20 on none already in effect --------------------------------------------------
Here's the scenario : - I move a folder into some other folder - I select all the folder's messages - I tag them with a (custom) tag (named 'archive') -> crash The tagging should remove these messages from some vfolders (which index only messages not tagged 'archive'). Hope this helps.
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Hi. Here's a better log of the same reproducible crash : Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb61b5770 (LWP 473)] [New Thread 0xac9fdb90 (LWP 1010)] [New Thread 0xb2a08b90 (LWP 1009)] [New Thread 0xb10f2b90 (LWP 592)] [New Thread 0xb19c6b90 (LWP 591)] [New Thread 0xb3209b90 (LWP 490)] [New Thread 0xb3b8db90 (LWP 489)] [New Thread 0xb438eb90 (LWP 486)] [New Thread 0xb596ab90 (LWP 484)] 0xb7f7f424 in __kernel_vsyscall ()
+ Trace 216158
Thread 3 (Thread 0xb2a08b90 (LWP 1009))
----------- .xsession-errors (58 sec old) --------------------- (evolution:473): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:473): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:473): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:473): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:473): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:473): camel-WARNING **: camel_exception_get_id called with NULL parameter. ** (nm-applet:5335): WARNING **: Unhandled setting secret type (write) '802-1x/private-key' : 'GArray_guchar_' ** (nm-applet:5335): WARNING **: Unhandled setting secret type (write) '802-1x/phase2-private-key' : 'GArray_guchar_' --------------------------------------------------
The second trace is a different issue and still misses debug symbols for glib2...
Here's a new version with glib-dev package installed, hoping it's better this time : Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb6137770 (LWP 23217)] [New Thread 0xb1072b90 (LWP 23524)] [New Thread 0xb2969b90 (LWP 23523)] [New Thread 0xb3221b90 (LWP 23273)] [New Thread 0xb2168b90 (LWP 23272)] [New Thread 0xb316ab90 (LWP 23236)] [New Thread 0xb3a8db90 (LWP 23235)] [New Thread 0xb428eb90 (LWP 23232)] [New Thread 0xb58ecb90 (LWP 23230)] 0xb7f01424 in __kernel_vsyscall ()
+ Trace 216164
Thread 3 (Thread 0xb2969b90 (LWP 23523))
----------- .xsession-errors (196 sec old) --------------------- (evolution:15092): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:15092): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:15092): camel-WARNING **: camel_exception_get_id called with NULL parameter. camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- /home/olivier/bin/evolution.sh: line 7: 15092 Complété PATH=$HOME/bin/in_path:$PATH evolution Fermeture de evolution-exchange-storage (Moteur principal Exchange du calendrier Evolution / Moteur Exchange du carnet d'adresses Evolution) Fermeture de evolution-data-server-2.26 (Fichier et moteur webcal pour le calendrier d'Evolution / Fichier du moteur du carnet d'adresse d'Evolution) Fermeture de evolution-alarm-notify (Service de notification d'alarme du calendrier d'Evolution) (evolution:23217): e-data-server-ui-WARNING **: Le fichier est vide --------------------------------------------------
Nice trace, thanks. Can you still reproduce it with steps from comment #1, please? I would like to know what account type you are working on and how is your vfolder configured. Were those moved messages in some other vfolder before and now should be moved to other, and so on. You know, as many details as possible. Thanks in advance.
NEEDINFO, awaiting a response for comment#6 Please try against evolution 2.28.3 or 2.30.0 and report back.
The newer bug #616318 contains a patch for this, thus I'm marking this one as a duplicate of it. *** This bug has been marked as a duplicate of bug 616318 ***