GNOME Bugzilla – Bug 244943
Evolution crashes when printing a calendar with overlapping appointments
Last modified: 2013-09-10 14:03:39 UTC
Package: Evolution Priority: Normal Version: 1.4.0 Synopsis: Evolution crashes when i try to print from the calendar or a specific calendar appointment Bugzilla-Product: Evolution Bugzilla-Component: Calendar BugBuddy-GnomeVersion: 2.0 (2.2.1) Description: Description of Problem: Whenever i try to print anything from the calendar (or the task-module for that matter) evolution crashes Steps to reproduce the problem: 1. Enter the calendar 2. Choose to print 3. BANG! Actual Results: Expected Results: How often does this happen? Everytime Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (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)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 1328)] [New Thread 32769 (LWP 1331)] [New Thread 16386 (LWP 1332)] [New Thread 32771 (LWP 1333)] [New Thread 49156 (LWP 1334)] (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)...(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)...0x4104baf9 in wait4 () from /lib/libc.so.6
+ Trace 37864
Thread 1 (Thread 16384 (LWP 1328))
Unknown reporter: markus.olsson.deblists@galaxen.se, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Cant reproduce this.
*** bug 257494 has been marked as a duplicate of this bug. ***
I reported the dup -- is there anything I can do to help debug this? I'd like to get printing working again.
*** bug 259016 has been marked as a duplicate of this bug. ***
*** bug 257531 has been marked as a duplicate of this bug. ***
Hi guys I have some additional information that might help. BTW I reported bug 259016. The crash only occurred when I tried to print two specific days in my calendar (using the day view). I could print from other Evo modules such as email and I could print other days. I went back to look at what might be different about these two days. There were two things I noticed , but ..... life isn't simple. 1) Some events on the days that crashed Evo had icons in them. One day had a reminder icon (bell) and on the other day there was a meeting invitation sent by someone else and so that appointment had a bunch-of-heads icon in it. I chose the first day and removed the reminder from this appointment, exited Evo then restarted Evo and then went to print. Unfortunately it crashed again! 2) The second thing that I noticed that was different about these two days is that they both contained appointments that overlapped the std time period. This means that the appointments showed side by side on the day view rather than one under the other. I moved one of these overlapping appointments from the first day to another (much) later day; exited Evo; re-started Evo and went to print. Voila! Evo printed without crashing! Aha! I though, I have found it and so to try to prove that I went to the (much) later day and caused the appointment on that day to overlap with another appointment and tried printing that day..... Well, unfortunately it printed without crashing and so things aren't as simple as I thought. Back I went to the second day that causes Evo to crash while printing. I tried printing that day and sure enough it crashed as well, as is, and with the iconic appointment removed. However, as soon as I moved the overlapping appointment to a different day, it too printed without crashing. Therefor, there seems to be a definite link between the crashing when attempting to print and overlapping appointments but it isn't as simple as creating an overlapping appointment and then trying to print that. Something else needs to be present as well and I don't know what that is. Lastly, the only other thing that I have changed on Evo lately is that just prior to the crashes, I changed the configuration to extend the definition of a working day from 9:00am through 5:00pm to 8:00am through 6:00pm. This seems a bit obscure and may be a red herring but, what the heck, more info is better than less info (sometimes). Doug
*** bug 261807 has been marked as a duplicate of this bug. ***
*** bug 256780 has been marked as a duplicate of this bug. ***
adding version info and keyword
changing subject since this bug is very likely based on overlapping appointments...
Still happens in 2.0.2
*** http://bugzilla.ximian.com/show_bug.cgi?id=70527 has been marked as a duplicate of this bug. ***
I too see these problems, with evolution 1.4.6 but printing a task. Based on backtrace, seems to happen in get_uri_without_password () from /usr/lib/evolution/1.4/components/libevolution-calendar.so. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 8387)] 0x411251b7 in memcpy () from /lib/libc.so.6 (gdb) thread apply all bt
+ Trace 54999
Thread 5 (Thread 3076 (LWP 8392))
Thread 4 (Thread 2051 (LWP 8391))
Thread 3 (Thread 1026 (LWP 8390))
Thread 1 (Thread 1024 (LWP 8387))
Still unable to reproduce this locally on 1.4, even with the calendar provided in 56780. Saw nothing in valgrind on 2.2. Maybe someone who can reliably reproduce this can run valgrind?
*** Bug 303222 has been marked as a duplicate of this bug. ***
James: Does this crash occur for all tasks or a for a specific task. If its for a particular task if you could attach that task.ics or can you give more information on what all the data is there in that task.
Created attachment 46370 [details] Task which crashes evolution when printing How to crash: I emailed this task to myself pressed 'Ok' next to 'Choose an action: Update' The task showed up in my task list. I highlighted the task, right clicked on it, than clicked 'Print'. Clicked 'Print' in the print dialog (note that printing to a file also crashes evolution) Evolution usually just disappears, but every once in a while bug-buddy catches it. This task crashes both 1.4.6 (from gnome2.2 Debian woody backport) and 2.0.2 from Official Debian Sarge.
Actually, it is for 2.0.4 from Debian Sarge.
To answer your questions, most tasks print ok. The above attached task crashes evolution. Tasks with long descriptions don't crash when printing, but the whole task doesn't print either. Eg I added the result of 'ls -l /usr/bin' to the Description field of a task, and then printed it. Though evolution was extremely slow while working with this task, evolution did not crash, but I only got one page of output (even on print to file). This may be a different bug.
James: Thank you for inputs, i am not able to reproduce so far the crash for task attached, i will try different ways to get this task into my task list and print.
I just confirmed that if I do: click on the below task in firefox right clicking and doing 'Save page as' then saving it to disk as crash.ics use evolution to mail crash.ics as an attachment use 'Update' in evolution on the email with this attachment highlight the task in evolution right click, print print to file (or printer-- doesn't matter) click Print crash
Here are my package versions: -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages evolution depends on: ii evolution-data-serve 1.0.4-1 evolution database backend server ii gconf2 2.8.1-5 GNOME configuration database syste ii gnome-icon-theme 2.8.0-4 GNOME Desktop icon theme ii gtkhtml3.2 3.2.5-1 HTML rendering/editing library - b ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit ii libaudiofile0 0.2.6-6 Open-source version of SGI's audio ii libbonobo2-0 2.8.1-2 Bonobo CORBA interfaces library ii libbonoboui2-0 2.8.1-2 The Bonobo UI library ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libcompfaceg1 1989.11.11-24 Compress/decompress images for mai ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [ ii libebook8 1.0.4-1 Client library for evolution addre ii libecal6 1.0.4-1 Client library for evolution calen ii libedataserver3 1.0.4-1 Utily library for evolution data s ii libegroupwise6 1.0.4-1 Client library for accessing group ii libesd0 0.2.35-2 Enlightened Sound Daemon - Shared ii libfontconfig1 2.3.1-2 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgail-common 1.8.4-1 GNOME Accessibility Implementation ii libgail17 1.8.4-1 GNOME Accessibility Implementation ii libgal2.2-1 2.2.5-1 G App Libs (run time library) ii libgal2.2-common 2.2.5-1 G App Libs (common files) ii libgconf2-4 2.8.1-5 GNOME configuration database syste ii libgcrypt11 1.2.0-4 LGPL Crypto library - runtime libr ii libglade2-0 1:2.4.2-2 library to load .glade files at ru ii libglib2.0-0 2.6.4-1 The GLib library of C routines ii libgnome-keyring0 0.4.2-1 GNOME keyring services library ii libgnome-pilot2 2.0.12-1.2 Support libraries for gnome-pilot ii libgnome2-0 2.8.1-2 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.8.0-1 A powerful object-oriented display ii libgnomeprint2.2-0 2.8.2-1 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.8.2-2 GNOME 2.2 print architecture User ii libgnomeui-0 2.8.1-3 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.8.4-3 The GNOME virtual file-system libr ii libgnutls11 1.0.16-9 GNU TLS library - runtime library ii libgpg-error0 1.0-1 library for common error values an ii libgtk2.0-0 2.6.4-1 The GTK+ graphical user interface ii libgtkhtml3.2-11 3.2.5-1 HTML rendering/editing library - r ii libice6 4.3.0.dfsg.1-12.0.1 Inter-Client Exchange library ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libldap2 2.1.30-6 OpenLDAP libraries ii libnspr4 2:1.7.7-2 Netscape Portable Runtime Library ii libnss3 2:1.7.7-2 Network Security Service Libraries ii liborbit2 1:2.12.2-1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio ii libpisock8 0.11.8-10 Library for communicating with a P ii libpisync0 0.11.8-10 Synchronization library for PalmOS ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm6 4.3.0.dfsg.1-12.0.1 X Window System Session Management ii libsoup2.2-7 2.2.3-2 an HTTP library implementation in ii libtasn1-2 0.2.10-3 Manage ASN.1 structures (runtime) ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li ii libxml2 2.6.16-7 GNOME XML library ii xlibs 4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime
James: Thanks for inputs. I could reproduce the bug. It is specific to 'Debian', I am not able to reproduce it on SUSE 9.x/ NLD. Developers over here will look into it tomorrow, I will follow up with them to provide fix for this as soon as possible.
I added a bug to the Debian BTS referencing this bug a few days ago: 308962@bugs.debian.org
It might be a packaging issue.
This is not a accessibility bug. Please remove the accessibility keyword.
harry: done
anyone able to reproduce this bug with any newer version of evolution, like 2.4.2.1 or 2.6 on debian? i have only seen 2.0 reports on this.
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. Thanks!
I just tried this on Ubuntu Dapper 6.06.1 and it caused a crash. This is a debian based distribution, but I don't know how close the evolution and gnome packaging is to Debian though.
This is evolution 2.6.1 BTW. I can't see how to re-open this, but it is defintely not fixed yet.
James can you install debuggin packages, please, and post a backtrace?
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1231623968 (LWP 29083)] 0xb71129dc in memcpy () from /lib/tls/i686/cmov/libc.so.6 (gdb) thread apply all bt
+ Trace 71220
Thread 1 (Thread -1231623968 (LWP 29083))
thank you, so bound_text (pc=0xa40f0f0, font=0x8418780, text=<value optimized out>, left=29.763779527559059, right=565.51181102362204, top=592.94976624656124, bottom=42.094488188976385, indent=0) at print.c:757 is leading up to a bogus memcpy() ...
*** This bug has been marked as a duplicate of 324221 ***