Bug #716433 “evolution crashes when using calendar” : Bugs : evolution package : Ubuntu

Revision history for this message

In Red Hat Bugzilla #598950, Aleksy (aleksy-redhat-bugs) wrote on 2010-06-02:

#16

abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution -c mail --sync
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 6f27b1bde132b66c0cb0916f3aa4d685a8a00814
kernel: 2.6.33.5-112.fc13.i686.PAE
package: evolution-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

comment
-----
Evloution dies with the message:

Gdk-ERROR **: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 1919308 error_code 13 request_code 60 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...

when run with --sync it prints out

[alx@aronia ~]$ (evolution:11072): e-data-server-DEBUG: Loading categories from "/home/alx/.evolution/categories.xml"
(evolution:11072): e-data-server-DEBUG: Loaded 47 categories

** (evolution:11072): CRITICAL **: categories_icon_theme_hack: assertion `filename != NULL && *filename != '\0'' failed
evolution: xcb_io.c:452: _XReply: Assertion `!dpy->xcb->reply_data' failed.

[1]+ Aborted (core dumped) evolution --sync -c mail

How to reproduce
-----
1. Run evolution
2. Change view to Calendar
3.

Revision history for this message

In Red Hat Bugzilla #598950, Aleksy (aleksy-redhat-bugs) wrote on 2010-06-02:

#17

Created attachment 419006
File: backtrace

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-02-10:

#1

Dependencies.txt Edit (7.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-02-10:

#2

Or
Open evolution in calendar
scroll up one click (with mouse wheel) - hangs

It also seems that I am unable to cut and paste items in the calendar views (may not be related)
right click an item, select copy
move to another day
right click, select paste - nothing happens or crash.

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-02-18:

#3

I upgraded to Maverick (clean install, home directory retained) in the hope of improving the situation - it seems to be worse, and now often closes when I just click on the calendar.

In case it was a problem with char encoding (as suggested elsewhere) I created a new calendar.ics file (utf-8/windows) with no improvement.

When started from the terminal and it crashes I get this:

The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 17035 error_code 13 request_code 66 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Please help.... I really need the calendar to work and there doesn't seem to be a viable alternative other than MS Outlook.

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-02-18:

#4

I found the same bug reported for fedora:

https://bugzilla.redhat.com/show_bug.cgi?id=598950

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2011-02-18:

#5

Could you please check whether you have crash files for evolution under /var/crash ? This is normally where evolution closing because of a crash would create files; which you can then send using the "ubuntu-bug file_name.crash" command to open a new bug. Please send the crash files with the above command if you find any, then report with the bug number here (or mention it if there are no crash files).

Changed in evolution (Ubuntu):
status:	New → Incomplete

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-02-20:

#6

There are no crash files in /var/crash, in either the previous installation (10.04) or the new one (10.10).

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2011-03-10:

#7

Steve,

Please try the following two things to add additional information to this bug report:

- Run evolution with the following command: evolution -c calendar --sync . This should allow us to figure out what causes the X error you pasted above. Reproduce the issue, then paste or attach the output here.

- Please attach a copy of .xsession-errors after reproducing the issue. There may be a useful error message. Note that the above command will contain the same information.

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-03-11:

#8

Download full text (7.8 KiB)

Mathieu,

Thanks for your continued interest:

Running with the sync option as suggested evolution flashes up briefly, then immediately closes, before any chance to interact with it, resulting in similar but different errors with each attempt (mostly they don't seem too helpful), see below, but on one occasion I got a more extensive output (at the bottom), not sure if it helps:

This is the most common outcome
drgrumpy@sjr06x:~$ evolution -c calendar --sync
EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

drgrumpy@sjr06x:~$ evolution -c calendar --sync
EI: MAIL PREFS*** glibc detected *** evolution: free(): corrupted unsorted chunks: 0x0000000003363c00 ***
Segmentation fault

drgrumpy@sjr06x:~$ evolution -c calendar --sync
EI: MAIL PREFSThe program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 4010 error_code 13 request_code 66 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

drgrumpy@sjr06x:~$ evolution -c calendar --sync
EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 3996 error_code 13 request_code 60 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

drgrumpy@sjr06x:~$ evolution -c calendar --sync
EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Once I got this:

drgrumpy@sjr06x:~$ evolution -c calendar --sync
EI: MAIL PREFS*** glibc detected *** evolution: double free or corruption (out): 0x000000000217a6e0 ***
======= Backtrace: =========
/lib/libc.so.6(+0x774b6)[0x7f4af64b44b6]
/lib/libc.so.6(cfree+0x73)[0x7f4af64bac83]
/usr/lib/libX11.so.6(+0x4a362)[0x7f4af34ed362]
/usr/lib/libX11.so.6(_XReply+0x140)[0x7f4af34ed9b0]
/usr/lib/libX11.so.6(XSync+0x63)[0x7f4af34e1333]
/usr/lib/libX11.so.6(+0x3e4eb)[0x7f4af34e14eb]
/usr/lib/libX11.so.6(XFreeGC+0xa4)[0x7f4af34c73f4]
/usr/lib/libgdk-x11-2.0.so.0(+0x5eb98)[0x7f4af8d43b98]
/usr/lib/libgobject-2.0.so.0(g_object_unref+0x174)[0x7f4af70c3e14]
/usr/lib/evolution/2.30/libetable.so.0(+0x26875)[0x7f4af513b875]
/usr/lib/evolution/2.30/libetable.so.0(+0x228dd)[0x7f4af51378dd]
/usr/lib/evolution/2.30/libetable.so.0(+0x44028)[0x7f4af5159028]
/usr/lib/evolution/2.30/libetable.so.0(+0x44144)[0x7f4af5159144]
/usr/lib/evolution/2.30/libetable.so.0(+0x441b4)[0x7f4af51591b4]
/usr/lib/libgo...

Mathieu,

Thanks for your continued interest:

Running with the sync option as suggested evolution flashes up briefly, then immediately closes, before any chance to interact with it, resulting in similar but different errors with each attempt (mostly they don't seem too helpful), see below, but on one occasion I got a more extensive output (at the bottom), not sure if it helps:

This is the most common outcome
drgrumpy@sjr06x:~$ evolution -c calendar --sync 
EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

drgrumpy@sjr06x:~$ evolution -c calendar --sync 
EI: MAIL PREFS*** glibc detected *** evolution: free(): corrupted unsorted chunks: 0x0000000003363c00 ***
Segmentation fault

drgrumpy@sjr06x:~$ evolution -c calendar --sync 
EI: MAIL PREFSThe program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 4010 error_code 13 request_code 66 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

drgrumpy@sjr06x:~$ evolution -c calendar --sync 
EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 3996 error_code 13 request_code 60 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

drgrumpy@sjr06x:~$ evolution -c calendar --sync 
EI: MAIL PREFSevolution: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Once I got this:

drgrumpy@sjr06x:~$ evolution -c calendar --sync 
EI: MAIL PREFS*** glibc detected *** evolution: double free or corruption (out): 0x000000000217a6e0 ***
======= Backtrace: =========
/lib/libc.so.6(+0x774b6)[0x7f4af64b44b6]
/lib/libc.so.6(cfree+0x73)[0x7f4af64bac83]
/usr/lib/libX11.so.6(+0x4a362)[0x7f4af34ed362]
/usr/lib/libX11.so.6(_XReply+0x140)[0x7f4af34ed9b0]
/usr/lib/libX11.so.6(XSync+0x63)[0x7f4af34e1333]
/usr/lib/libX11.so.6(+0x3e4eb)[0x7f4af34e14eb]
/usr/lib/libX11.so.6(XFreeGC+0xa4)[0x7f4af34c73f4]
/usr/lib/libgdk-x11-2.0.so.0(+0x5eb98)[0x7f4af8d43b98]
/usr/lib/libgobject-2.0.so.0(g_object_unref+0x174)[0x7f4af70c3e14]
/usr/lib/evolution/2.30/libetable.so.0(+0x26875)[0x7f4af513b875]
/usr/lib/evolution/2.30/libetable.so.0(+0x228dd)[0x7f4af51378dd]
/usr/lib/evolution/2.30/libetable.so.0(+0x44028)[0x7f4af5159028]
/usr/lib/evolution/2.30/libetable.so.0(+0x44144)[0x7f4af5159144]
/usr/lib/evolution/2.30/libetable.so.0(+0x441b4)[0x7f4af51591b4]
/usr/lib/libgobject-2.0.so.0(g_object_run_dispose+0x60)[0x7f4af70c4270]
/usr/lib/evolution/2.30/libetable.so.0(+0x3975f)[0x7f4af514e75f]
/usr/lib/libgobject-2.0.so.0(g_object_run_dispose+0x60)[0x7f4af70c4270]
/usr/lib/evolution/2.30/libetable.so.0(+0x35fac)[0x7f4af514afac]
/usr/lib/evolution/2.30/libetable.so.0(+0x36168)[0x7f4af514b168]
/usr/lib/evolution/2.30/libetable.so.0(+0x56915)[0x7f4af516b915]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f4af70c1a6e]
/usr/lib/libgobject-2.0.so.0(+0x24de7)[0x7f4af70d7de7]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7e6)[0x7f4af70d92a6]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83)[0x7f4af70d9863]
/usr/lib/evolution/2.30/libevolution-calendar.so.0(+0x3d67f)[0x7f4aeccf067f]
/usr/lib/evolution/2.30/libevolution-calendar.so.0(+0x9159b)[0x7f4aecd4459b]
/usr/lib/evolution/2.30/libevolution-calendar.so.0(+0x9101e)[0x7f4aecd4401e]
/lib/libglib-2.0.so.0(+0x6b73f)[0x7f4af682b73f]
/lib/libglib-2.0.so.0(+0x697e4)[0x7f4af68297e4]
/lib/libpthread.so.0(+0x7971)[0x7f4afa7d3971]
/lib/libc.so.6(clone+0x6d)[0x7f4af652392d]
======= Memory map: ========
00400000-00404000 r-xp 00000000 08:08 267745                             /usr/bin/evolution
00603000-00604000 r--p 00003000 08:08 267745                             /usr/bin/evolution
00604000-00605000 rw-p 00004000 08:08 267745                             /usr/bin/evolution
014d2000-023bc000 rw-p 00000000 00:00 0                                  [heap]
7f4ad4000000-7f4ad4083000 rw-p 00000000 00:00 0 
7f4ad4083000-7f4ad8000000 ---p 00000000 00:00 0 
7f4ad872e000-7f4ad8732000 r-xp 00000000 08:08 267857                     /usr/lib/evolution/2.30/plugins/liborg-gnome-backup-restore.so
7f4ad8732000-7f4ad8931000 ---p 00004000 08:08 267857                     /usr/lib/evolution/2.30/plugins/liborg-gnome-backup-restore.so
7f4ad8931000-7f4ad8932000 r--p 00003000 08:08 267857                     /usr/lib/evolution/2.30/plugins/liborg-gnome-backup-restore.so
7f4ad8932000-7f4ad8933000 rw-p 00004000 08:08 267857                     /usr/lib/evolution/2.30/plugins/liborg-gnome-backup-restore.so
7f4ad8933000-7f4ad8939000 r-xp 00000000 08:08 267859                     /usr/lib/evolution/2.30/plugins/liborg-gnome-templates.so
7f4ad8939000-7f4ad8b38000 ---p 00006000 08:08 267859                     /usr/lib/evolution/2.30/plugins/liborg-gnome-templates.so
7f4ad8b38000-7f4ad8b39000 r--p 00005000 08:08 267859                     /usr/lib/evolution/2.30/plugins/liborg-gnome-templates.so
7f4ad8b39000-7f4ad8b3a000 rw-p 00006000 08:08 267859                     /usr/lib/evolution/2.30/plugins/liborg-gnome-templates.so
7f4ad8b3a000-7f4ad8b3e000 r-xp 00000000 08:08 267762                     /usr/lib/evolution/2.30/plugins/liborg-gnome-plugin-manager.so
7f4ad8b3e000-7f4ad8d3d000 ---p 00004000 08:08 267762                     /usr/lib/evolution/2.30/plugins/liborg-gnome-plugin-manager.so
7f4ad8d3d000-7f4ad8d3e000 r--p 00003000 08:08 267762                     /usr/lib/evolution/2.30/plugins/liborg-gnome-plugin-manager.so
7f4ad8d3e000-7f4ad8d3f000 rw-p 00004000 08:08 267762                     /usr/lib/evolution/2.30/plugins/liborg-gnome-plugin-manager.so
7f4ad8d3f000-7f4ad8d48000 r-xp 00000000 08:08 267838                     /usr/lib/evolution/2.30/plugins/liborg-gnome-save-calendar.so
7f4ad8d48000-7f4ad8f47000 ---p 00009000 08:08 267838                     /usr/lib/evolution/2.30/plugins/liborg-gnome-save-calendar.so
7f4ad8f47000-7f4ad8f48000 r--p 00008000 08:08 267838                     /usr/lib/evolution/2.30/plugins/liborg-gnome-save-calendar.so
7f4ad8f48000-7f4ad8f49000 rw-p 00009000 08:08 267838                     /usr/lib/evolution/2.30/plugins/liborg-gnome-save-calendar.so
7f4ad8f49000-7f4ad8f4f000 r-xp 00000000 08:08 268538                     /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4ad8f4f000-7f4ad914e000 ---p 00006000 08:08 268538                     /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4ad914e000-7f4ad914f000 r--p 00005000 08:08 268538                     /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4ad914f000-7f4ad9150000 rw-p 00006000 08:08 268538                     /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4ad9150000-7f4ad9165000 r-xp 00000000 08:08 1310799                    /lib/libgcc_s.so.1
7f4ad9165000-7f4ad9364000 ---p 00015000 08:08 1310799                    /lib/libgcc_s.so.1
7f4ad9364000-7f4ad9365000 r--p 00014000 08:08 1310799                    /lib/libgcc_s.so.1
7f4ad9365000-7f4ad9366000 rw-p 00015000 08:08 1310799                    /lib/libgcc_s.so.1
7f4ad9366000-7f4ad944e000 r-xp 00000000 08:08 265810                     /usr/lib/libstdc++.so.6.0.14
7f4ad944e000-7f4ad964d000 ---p 000e8000 08:08 265810                     /usr/lib/libstdc++.so.6.0.14Aborted

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-03-11:

#9

.xsession-errors Edit (112.4 KiB, text/plain)

Also .xsession-errors attached

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-03-23:

#10

No improvement with latest kernel update to 2.6.35.-28-generic

Revision history for this message

corneil (corneil) wrote on 2011-04-18:

#11

I have had the same problems for some time now on lucid, maverick and natty beta 1 & 2.

Connect Evolution to my Google account using IMAP.
Create Calendar to Google Calendar using the same account.

Select Calendar view. Watch with 'System Monitor' you can see the memory usage of e-calendar-factory climb until all available memory is used.

Crash message says 'Not enough memory to report error'

My Calendar on Google isn't very full maybe 2-4 events per week most of them recurring weekly and about 80-120 annual recurring items.

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2011-04-18:

#12

Steve,
Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem. These logs should be taken without the --sync option ;)

corneil, please file a separate bug using 'ubuntu-bug evolution' so we can identify your problem. It doesn't look like this would be the same thing.

Revision history for this message

Steve Roberts (drgrumpy) wrote on 2011-04-26:

#13

Dear Mathieu,

Sorry for slow response. I actually already obtained a valgrind log at your request and posted it, some time ago, here:

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/655405/comments/30

Apologies if I have confused things.

Steve

Revision history for this message

Julian Suarez (juliansuarezlopera) wrote on 2011-05-12:

#14

You are not alone I'm also suffering from this bug :-(

Revision history for this message

In Red Hat Bugzilla #598950, Bug (bug-redhat-bugs) wrote on 2011-06-02:

#18

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message

In Red Hat Bugzilla #598950, Bug (bug-redhat-bugs) wrote on 2011-06-27:

#19

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message

Jörg Frings-Fürst (jff-de) wrote on 2013-11-06:

#15

since 2011-02-18 status Incomplete

change status to invalid

Changed in evolution (Ubuntu):
status:	Incomplete → Invalid

Bug Watch Updater (bug-watch-updater) on 2017-10-27

Changed in evolution (Fedora):
importance:	Unknown → Medium
status:	Unknown → Won't Fix

Affects		Status	Importance	Assigned to	Milestone
	evolution (Fedora)	Won't Fix	Medium	redhat-bugs #598950
	evolution (Ubuntu)	Invalid	Undecided	Unassigned

Ubuntu
evolution package

evolution crashes when using calendar

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuevolution package

evolution crashes when using calendar

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
evolution package