Created attachment 1717640 [details]
File: backtrace

Created attachment 1717641 [details]
File: core_backtrace

Created attachment 1717642 [details]
File: cpuinfo

Created attachment 1717643 [details]
File: dso_list

Created attachment 1717644 [details]
File: environ

Created attachment 1717645 [details]
File: limits

Created attachment 1717646 [details]
File: maps

Created attachment 1717647 [details]
File: mountinfo

Created attachment 1717648 [details]
File: open_fds

Created attachment 1717649 [details]
File: proc_pid_status

Created attachment 1717650 [details]
File: var_log_messages

Similar problem has been detected:

This happens every second time I launch Gnome Calendar, so I'd guess the application service might be the problem:

1. Start Calendar.  It opens fine.
2. Wait a moment, then close the window.
3. Start Calendar again.  This time, the window appears briefly and disappears.
(goto step 1)

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Calendar
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: on_calendar_monitor_completed_cb
executable:     /usr/bin/gnome-calendar
journald_cursor: s=318e52e318de4dc78121695534b4194a;i=6619;b=c4b07725d8c14d5896a14ccfd5d58948;m=3c37c20;t=5b13565343b62;x=43de285df90f2ccf
kernel:         5.8.13-300.fc33.x86_64
package:        gnome-calendar-3.38.1-1.fc33
reason:         gnome-calendar killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Proposed as a Blocker for 33-final by Fedora user psimonyi using the blocker tracking app because:

 "All applications that can be launched using the standard graphical mechanism after a default installation of Fedora Workstation on the x86_64 architecture must start successfully and withstand a basic functionality test."

Crashing every second time you launch it seems like failing a basic functionality test.  Plus, since Calendar replaced Evolution in the default favourites list, it's a pretty prominent app.

Similar problem has been detected:

Trying to reproduce bug 1883681. Started gnome-calendar twice, the second time it immediately crashed.

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Calendar
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: on_calendar_monitor_completed_cb
executable:     /usr/bin/gnome-calendar
journald_cursor: s=ddad73e6f4e2402aaffe791469682569;i=2ee47f;b=7c261537394f4d169971a59cd1761dfe;m=26be36c3;t=5b13bf2a59f09;x=7d194b7afddf4e5b
kernel:         5.8.14-300.fc33.x86_64
package:        gnome-calendar-3.38.1-1.fc33
reason:         gnome-calendar killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:

Hm, I also get the same crash switching years (e.g. try to show next January) so perhaps this is related to upstream's https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/149 and https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/647

We have +4 blocker in the ticket, marking accepted.

(In reply to Adam Williamson from comment #16)
> We have +4 blocker in the ticket, marking accepted.

Ticket link:
https://pagure.io/fedora-qa/blocker-review/issue/156

*** Bug 1887340 has been marked as a duplicate of this bug. ***

Peter: backtrace here is indeed the same as the one in https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/149 , yeah. Good spot. Setting POST as there's a PR, though there is a possible issue with it so we probably can't just blindly backport it: "Decrementing the completed calendars counter was introduced by 78cb11c6 to fix #625, so you'd have to make sure it doesn't regress that bug."

*** Bug 1882876 has been marked as a duplicate of this bug. ***

I'll take this.

FEDORA-2020-b973a3525f has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b973a3525f

*** Bug 1887983 has been marked as a duplicate of this bug. ***

Thanks, Michael.  That seems to fix it.

FEDORA-2020-b973a3525f has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b973a3525f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b973a3525f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-b973a3525f has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

I tried the update several times and experienced one crash, on the second try.

Boricua, have you rebooted after applying that update?

(In reply to Kamil Páral from comment #28)
> Boricua, have you rebooted after applying that update?

No. I did several logouts and have being launching the app without further crashes. I followed your suggestion and made a reboot. So far, no further issues.

Then I assume the crash you encountered shortly after the update was still the old process running. (Next time, it's recommended to fully reboot after testing any update, in order to get fully reliable results).

Understood; thanks for the tip. I have been opening the app to the point of abuse, with no crash so far.

Seems to have fixed all problems with initial report. Thanks for the quick work guys!

(In reply to Kamil Páral from comment #30)
> Then I assume the crash you encountered shortly after the update was still
> the old process running. (Next time, it's recommended to fully reboot after
> testing any update, in order to get fully reliable results).

I think logout should be enough to kill gnome-calendar. My guess is it was probably just some different crash. Anyway, feel free to get a backtrace (either with ABRT or coredumpctl) and post for analysis.

*** Bug 1898706 has been marked as a duplicate of this bug. ***

*** Bug 1913334 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Removed a source file from $HOME/.config/evolution/sources because everything was duplicated.

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Calendar
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: on_calendar_monitor_completed_cb
executable:     /usr/bin/gnome-calendar
journald_cursor: s=ce495bd557d944e69dc649bc66d0e654;i=4a85;b=d02db40b60be4e7a80515be4fc044177;m=3c4fee809d;t=5bef99cf06643;x=3ff8a35a22402761
kernel:         5.11.10-200.fc33.x86_64
package:        gnome-calendar-3.38.2-1.fc33
reason:         gnome-calendar killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000