gnome-shell is explicitly launching evolution there. We are getting the calendar information that is displayed in the popup from evolution, so it only makes sense to launch evolution, imo. korganizer will likely not show the same information, which would only be confusing.

Korganizer is able to provide same information about upcoming appointments and tasks. The only inconsistency case is when user configure different calendars in Evolution then in Korganizer. But users using two calendar applications is very rare case.

User can change default application for calendar files to Korganizer, it makes sense to be consistent and 1) provide calendar information from Korganizer in popup 2) Launch Korganizer.

I don't think it's possible to provide information from KOrganizer (or rather Akonadi) in gnome-shell without either native Akonadi GLib client libraries or a Akonadi-EDS bridge (which both represent a large amount of work).

On the other hand, if user configured KOrganizer as a default calendaring application, I too would expect gnome-shell to obey user's configuration.

(In reply to Matthias Clasen from comment #1)
> gnome-shell is explicitly launching evolution there.

We used to do that in the past, but haven't in a while (3.4?). However, *what* we pick has changed recently - we used to pick the first application as returned by g_app_info_get_default_for_type ("text/calendar", FALSE), but that was changed (accidentally?) to g_app_info_get_recommended_for_type ("text/calendar") in the 3.10 cycle.


> We are getting the calendar information that is displayed in the popup 
> from evolution, so it only makes sense to launch evolution, imo. korganizer
> will likely not show the same information, which would only be confusing.

That's a fair point. It's even a bit more confusing - if there are no event sources (e.g. calendars in Evolution), then both events pane and "Open Calendar" item will be hidden, so users who really only use some other calendar application will only get the item when the events are bound to differ. (It's unlikely that those users would set up calendars manually in Evolution, but they might get ownCloud/Google calendars via online-accounts). However I don't think it's something we can get completely right for non-eds calendars, and the current behavior is correct for alternative eds frontends like gnome-calendar.

(In reply to Florian Müllner from comment #4)
> [...] but that was changed (accidentally?) [...]

My bad, on re-reading the original upstream bug it turns out that the change was intentional. Still, we can do better, I filed https://bugzilla.gnome.org/show_bug.cgi?id=722333 upstream.

too late for 7.0

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0535.html