GNOME Bugzilla – Bug 315329
Evolution crashed on launching
Last modified: 2013-09-10 13:54:05 UTC
1.Created a web calendar in which webcal url was wrong. 2.On restarting evolution , evolution crashed. Backtrace was generated from '/opt/gnome/bin/evolution' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1097744000 (LWP 6823)] [New Thread 1133300656 (LWP 6850)] [Thread debugging using libthread_db enabled] [New Thread 1097744000 (LWP 6823)] [New Thread 1133300656 (LWP 6850)] [Thread debugging using libthread_db enabled] [New Thread 1097744000 (LWP 6823)] [New Thread 1133300656 (LWP 6850)] [New Thread 1116490672 (LWP 6836)] [New Thread 1114389424 (LWP 6835)] [New Thread 1107692464 (LWP 6828)] 0xffffe410 in ?? ()
+ Trace 62726
Thread 1 (Thread 1097744000 (LWP 6823))
Doesnt happen always
Removed configured exchange Id. Restarted evolution again evolution crashed with following traces Backtrace was generated from '/opt/gnome/bin/evolution' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1097744000 (LWP 7149)] [New Thread 1120623536 (LWP 7181)] [Thread debugging using libthread_db enabled] [New Thread 1097744000 (LWP 7149)] [New Thread 1120623536 (LWP 7181)] [Thread debugging using libthread_db enabled] [New Thread 1097744000 (LWP 7149)] [New Thread 1120623536 (LWP 7181)] [New Thread 1118522288 (LWP 7180)] [New Thread 1110117296 (LWP 7176)] 0xffffe410 in ?? ()
+ Trace 62727
Thread 1 (Thread 1097744000 (LWP 7149))
Removed web calendar even then evolution is crashing. In Free/Busy publish i have provided URL to which free/busy information is not getting published (as there is some problem in the URL provided). Evolution is crashing due to wrong url in Free/Busy publish. Removed that URL after that evolution is not crashing.
Created attachment 52014 [details] [review] Fixes the bug e-pub-utils.c (e_pub_publish): Set the client as NULL, after g_object_unref (client)
Marking it as duplicate. *** This bug has been marked as a duplicate of 273322 ***