Description of problem: Evolution is connected to an Exchange server. When I switch to Calendar view, the calendar is grey instead of showing white columns. When the mouse pointer passes over the calendar, Evolution crash. Just updated from Fedora 20 to 21. Version-Release number of selected component: evolution-3.12.7-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/evolution crash_function: e_day_view_convert_position_in_main_canvas executable: /usr/bin/evolution kernel: 3.17.2-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (8 frames) #0 e_day_view_convert_position_in_main_canvas at e-day-view.c:8158 #1 e_day_view_on_main_canvas_motion at e-day-view.c:4770 #2 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85 #7 gtk_widget_event_internal at gtkwidget.c:7773 #8 propagate_event_up at gtkmain.c:2414 #9 propagate_event at gtkmain.c:2516 #10 gtk_main_do_event at gtkmain.c:1748 #16 gtk_main at gtkmain.c:1207
Created attachment 954970 [details] File: backtrace
Created attachment 954971 [details] File: cgroup
Created attachment 954972 [details] File: core_backtrace
Created attachment 954973 [details] File: dso_list
Created attachment 954974 [details] File: environ
Created attachment 954975 [details] File: limits
Created attachment 954976 [details] File: maps
Created attachment 954977 [details] File: open_fds
Created attachment 954978 [details] File: proc_pid_status
Created attachment 954979 [details] File: var_log_messages
Thanks for a bug report. I tried to reproduce this, I have also evolution-3.12.7 installed, but no luck. The difference might be that I installed Fedora 21 into a fresh place, while you updated from Fedora 20. I'm afraid there left something from Fedora 20 which causes trouble, but it's quite unlikely too. Could you run evolution from a command line and check whether there's shown anything before the crash, please? Maybe there will be a runtime warning related to the crash itself, the same as for the gray area instead of columns. By the way, some gray is correct, it's for the non-working days and hours. Also, could you try to switch to a Month view and then back to the Day view? You can do that with mouse on the tool bar, just be careful and do not move the mouse over the "calendar" area.
Here is the output from the console. The last line says "floating point exception". $ evolution (evolution:12221): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version. (evolution:12221): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (evolution:12221): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version. (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed No bp log location saved, using default. [000:000] Cpu: 6.45.7, x4, 3000Mhz, 7908MB [000:000] Computer model: Not available [000:000] Browser XEmbed support present: 1 [000:000] Browser toolkit is Gtk2. [000:007] Using Gtk2 toolkit No bp log location saved, using default. [000:000] Cpu: 6.45.7, x4, 3000Mhz, 7908MB [000:000] Computer model: Not available openjdk version "1.8.0_25" OpenJDK Runtime Environment (build 1.8.0_25-b18) OpenJDK 64-Bit Server VM (build 25.25-b02, mixed mode) (evolution:12221): GLib-GObject-WARNING **: The property GtkCellRendererPixbuf:stock-id is deprecated and shouldn't be used anymore. It will be removed in a future version. (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed (evolution:12221): GLib-GObject-WARNING **: The property GtkSettings:gtk-toolbar-style is deprecated and shouldn't be used anymore. It will be removed in a future version. (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion 'location != NULL' failed Undtagelsestilfælde ved flydende taloperation (smed kerne)
It is possible to switch to month and week view, but the work-week and day view are all grey and cause the crash on mouse-over.
Thanks for the update. Knowing it's only the Day view (the Work Week view is also implemented with the Day view widget) makes this easier to focus on something. > (evolution:12221): libecal-CRITICAL **: e_cal_util_get_system_timezone: > assertion 'location != NULL' failed This means that evolution failed to detect your system timezone. There can be various reasons for it. Would change anything if you go to Edit->Preferences->Calendar and Tasks->General tab and change there the "Use system timezone" (uncheck it) and select a particular timezone on your own? I tried to cheat a bit here, but I didn't manage to reproduce it when I had the same runtime warning. I also guess you do not use a gnome-shell desktop environment, could I ask which one you use, please? I'm wondering whether it has any influence. Another thing can be with accessibility. Do you have anything like that enabled? Maybe it's unrelated, but there was added a fix for it for evolution 3.12.8, which is available as an update here: https://admin.fedoraproject.org/updates/evolution-mapi-3.12.8-1.fc21,evolution-ews-3.12.8-1.fc21,evolution-3.12.8-1.fc21,evolution-data-server-3.12.8-1.fc21
Yes I am using KDE desktop, both now in Fedora 21 and before in '20 where this problem did not appear. I have not turned on any accessibility. I will try what happens with the time zone setting and also try to start Evolution from the Gnome shell when I get back to work tomorrow.
I can reproduce the crash under KDE too. There seems to be something odd with the oxygen theme, because if I change the GTK+ Appearance widget style from oxygen to for example Simple, then evolution works as expected. I found out that when the KDE uses the oxygen-gtk theme, then the widget doesn't receive "style-updated" signal, thus it doesn't calculate necessary values for a proper drawing and everything breaks. As other themes cause this signal emission, I suppose it's an issue with oxygen-gtk as such, thus I'm reassigning it there. I can workaround this issue in the Day view, but there are too many other widgets which rely on the signal receive, including the Week/Month view, thus I believe the only real fix should be done in the oxygen-gtk theme.
I can confirm your findings! Just tried Evolution from Gnome, it works. Changed time zone setting, still crash. Changed GTK+ Appearance setting to style "simple", it works. Thank you.
Reporter(s), can you give: rpm -q oxygen-gtk3 ? In particular, if you don't have, https://admin.fedoraproject.org/updates/FEDORA-2014-13526/oxygen-gtk3-1.4.1-1.fc21 yet, please update, and retest. Thanks.
Nevermind, looks like that went to stable updates over a week ago, I'll send this upstream.
Reported, https://bugs.kde.org/show_bug.cgi?id=340887
Confirm that: # rpm -q oxygen-gtk3 oxygen-gtk3-1.4.1-1.fc21.x86_64
I see this with $ rpm -q oxygen-gtk3 oxygen-gtk3-1.4.1-3.fc21.i686 (I actually see evolution crash when oxygen-gtk is enabled, https://bugzilla.redhat.com/show_bug.cgi?id=1170667 tells me it's this bug).
*** Bug 1177806 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.