#192 F33: clicking on events in calendar area opens gedit
Closed: Fixed 3 years ago by catanzaro. Opened 3 years ago by catanzaro.

After upgrading to F33, first thing I notice is that the calendar area has been redesigned a little bit, and our odd choice of default calendar is suddenly more important than it was before:

Screenshot_from_2020-09-28_19-17-19.png

If I click on the "Today No Events" box, gedit opens. We should disable this until it integrates with gnome-calendar.


I looked into gedit's desktop file to see if we can remove a MIME type association, but no, it only claims to support text/plain. I guess text/calendar inherits from that.

If I click on the "Today No Events" box, gedit opens. We should disable this until it integrates with gnome-calendar.

Weird, I have a F33 VM and here the "events" section isn't reactive (even when it has events).

I looked into gedit's desktop file to see if we can remove a MIME type association, but no, it only claims to support text/plain. I guess text/calendar inherits from that.

According to the Shell's codebase, it uses GAppInfo.get_recommended_for_type, which shouldn't follow the MIME subclassing. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/master/js/ui/dateMenu.js#L255

@feborges

Weird, I have a F33 VM and here the "events" section isn't reactive (even when it has events).

Same for me on a F32->F33 upgraded laptop.

OK, I had assumed that everybody would be seeing this behavior. @fmuellner, any idea what's up here?

Metadata Update from @chrismurphy:
- Issue untagged with: meeting-request
- Issue tagged with: meeting

3 years ago

This seems to be happening only for me, even though several of us have text editors set as our default calendar (since that is Fedora's default).

Let's treat it as we would any other gnome-shell bug. I'll report this upstream, and we don't need to track it further here.

Metadata Update from @catanzaro:
- Issue close_status updated to: Deferred to upstream
- Issue status updated to: Closed (was: Open)

3 years ago

Metadata Update from @catanzaro:
- Issue untagged with: meeting

3 years ago

what does

gio mime text/calendar

say on your system ?

I get:

$ gio mime text/calendar
Default application for “text/calendar”: org.gnome.Evolution.desktop
Registered applications:
    org.gnome.Evolution.desktop
    org.gnome.gedit.desktop
    com.axosoft.GitKraken.desktop
    com.notepadqq.Notepadqq.desktop
    io.liri.Text.desktop
    org.geany.Geany.desktop
Recommended applications:
    org.gnome.Evolution.desktop

Metadata Update from @mclasen:
- Issue status updated to: Open (was: Closed)
- Issue tagged with: meeting

3 years ago
$ gio mime text/calendar
Default application for “text/calendar”: org.gnome.gedit.desktop
Registered applications:
    org.gnome.TextEditor.Devel.desktop
    libreoffice-writer.desktop
    org.gnome.gedit.desktop
No recommended applications

Default application for “text/calendar”: org.gnome.gedit.desktop

I think that is probably the defining difference

Laptop upgrade from F32W to F33W (libreoffice is not installed)

$ gio mime text/calendar
Default application for “text/calendar”: org.gnome.gedit.desktop
Registered applications:
    org.gnome.gedit.desktop
No recommended applications

Laptop with clean installed F33W:

$ gio mime text/calendar
Default application for “text/calendar”: org.gnome.gedit.desktop
Registered applications:
    libreoffice-writer.desktop
    org.gnome.gedit.desktop
No recommended applications

I tested in a fresh F33 VM, and can confirm the bug does not occur there and my gio mime text/calendar output is identical to Chris's second example. So it must not be related to that at all.

At least it seems to only be happening for me, and not by default.

The output of gio mime is showing what is defined in the mime system.

It is what GDesktopAppInfo uses to figure out what to launch.

Yes, but we see that users with the same gio mime output wind up alternatively (a) launching gedit, or (b) not launching gedit. So we know the gio mime output is not related to this bug.

Metadata Update from @chrismurphy:
- Issue untagged with: meeting

3 years ago

I can no longer reproduce this. I'm confused. Whatever. Closing.

Metadata Update from @catanzaro:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata
Attachments 1