GNOME Bugzilla – Bug 332300
Crash with 30 boxes
Last modified: 2013-09-10 13:42:14 UTC
Steps to reproduce: Description of the crash: EDS crashed when you add an iCalendar subscription from 30boxes Steps to reproduce the crash: 1. Create an account on 30 boxes. Add some events to it 2. Goto <username>'s Settings (top right). Goto Syndication. 3. Copy and paste the ICalendar URL into a new calendar in Evolution Expected Results: The 30boxes calendar should be added to Evolution How often does this happen? Everytime I add or try to access a 30 boxes calendar Additional Information: 30boxes is new so it might be that their iCal stuff is subtly broken. But still shouldn't crash EDS Stack trace: Backtrace was generated from '/usr/libexec/evolution-data-server-1.4' 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) (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) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1219373376 (LWP 15255)] [New Thread -1223586896 (LWP 15256)] (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) 0xffffe410 in ?? ()
+ Trace 66439
Thread 1 (Thread -1219373376 (LWP 15255))
Other information:
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Created attachment 67845 [details] stacktrace for the crash
I've installed the debug verison of Evo and recreated the crash and got a stacktrace - see attached. Let me know if you need anything else. Paul
Paul, is it a crash or a hang. I don't see any sigsegv happening here. I also do not find any calendar related functions in stack trace. Adding mail guys in CC list.
Paul, Do you still observe this issue? Could you please check if this works for you with the latest stable release (2.22.x)?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for with current version 2.22.3.1 Thanks!