GNOME Bugzilla – Bug 326123
Crash while Drop And Drag Email To Tomboy
Last modified: 2013-09-13 00:55:07 UTC
Please describe the problem: Even though I would have guessed a crash would come from Tomboy, it was Evolution that crashed. When I tried to drop and drag an email message into Tomboy, Evo .5.4 crashed. This feature is supported in Tomboy. Backtrace was generated from '/opt/gnome/bin/evolution-2.6' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232468288 (LWP 22941)] [New Thread -1309680720 (LWP 22968)] [Thread debugging using libthread_db enabled] [New Thread -1232468288 (LWP 22941)] [New Thread -1309680720 (LWP 22968)] [Thread debugging using libthread_db enabled] [New Thread -1232468288 (LWP 22941)] [New Thread -1309680720 (LWP 22968)] [New Thread -1301288016 (LWP 22967)] [New Thread -1292895312 (LWP 22966)] [New Thread -1282942032 (LWP 22965)] [New Thread -1274549328 (LWP 22964)] [New Thread -1257243728 (LWP 22955)] [New Thread -1265640528 (LWP 22950)] [New Thread -1246757968 (LWP 22948)] [New Thread -1242039376 (LWP 22946)] [New Thread -1241957456 (LWP 22945)] 0xffffe410 in ?? ()
+ Trace 65023
Thread 1 (Thread -1232468288 (LWP 22941))
Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
i'm shortening the summary so it's readable in bugzilla search results. hmm, stacktrace misses some symbols. is this 100% reproducible, and if yes, can you attach another stacktrace? thanks in advance. :-)
Hope this one is better, run with gdb running. It crashes every time. Program received signal SIGSEGV, Segmentation fault.
+ Trace 65064
Thread 1098254464 (LWP 27240)
Hi, I'm not sure this is the same, so it might have to be changed. I'm running latest Ubuntu dapper. If you wan't a better report, please hint as to which dbg-packages I need to install. Bjørn Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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) [Thread debugging using libthread_db enabled] [New Thread 915572960 (LWP 17012)] [New Thread 839502768 (LWP 17028)] [New Thread 865074096 (LWP 17027)] [New Thread 848288688 (LWP 17024)] [New Thread 856681392 (LWP 17023)] [New Thread 884128688 (LWP 17020)] [New Thread 875563952 (LWP 17019)] [New Thread 892521392 (LWP 17015)] [New Thread 900963248 (LWP 17014)] [New Thread 909355952 (LWP 17013)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 66347
Thread 1 (Thread 915572960 (LWP 17012))
Just for completeness. Strangely tomboy crashes also, but it always operates normally for approx 30. sec. after evo. crashes before it crashes. I've filed a bug report for tomboy, bug #331877 (In reply to comment #3) > Hi, I'm not sure this is the same, so it might have to be changed. I'm running > latest Ubuntu dapper. If you wan't a better report, please hint as to which > dbg-packages I need to install. > > Bjørn
Not 100% sure but I think I've just fixed it, see https://launchpad.net/distros/ubuntu/+source/evolution/+bug/33026 for my previous bug report for dapper. after applying the upcoming patch, DnD from evolution to nautilus/tomboy stops crashing.
Created attachment 61054 [details] [review] call gfree later
Wow nice, I'll be happy to test this once it's in the build. I'm trying to ping someone on IRC to accept and commit this patch.
Setting proper Priority for crashes. Since we already got a patch that needs to be reviewed, setting Target Milestone. Confirming as per the previous comments.
The patch looks fine. Ok to commit. Commit to HEAD and stable branch
Is it supposed to be commited to evolution 2.6 ? I have juste reinstalled dapper, now with evolution 2.6.0 and the patch is not in. building it on my own again... please apply it before gnome 2.14, DnD of mails to nautilus is so nice :)
(In reply to comment #10) > Is it supposed to be commited to evolution 2.6 ? > I have juste reinstalled dapper, now with evolution 2.6.0 and the patch is not > in. Weird, I'm running latest Dapper including Evo 2.6 and all other upgrades commited during the night. And it's working for me.
> Weird, I'm running latest Dapper including Evo 2.6 and all other upgrades > commited during the night. And it's working for me. > Sorry, it was working when i tried this morning, but now it's a no-go for me to:(
uhm, just went through the patch backlog and saw this one here directly after committing patrick's patch for 335203 which is 100% the same, so i'm marking this bug as a duplicate of the newer one. :-/ fix was committed both to gnome-2-14 branch and cvs head, so it will be included in evolution 2.6.1 and evolution 2.7.x. thanks anyway for providing the patch. :-) *** This bug has been marked as a duplicate of 335203 ***