Description of problem: The application started and immediately after that crashed. Version-Release number of selected component: gnome-calendar-43.0-1.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user/app.slice/dbus-:1.2-org.gnome.Calendar cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: gcal_event_widget_clone executable: /usr/bin/gnome-calendar journald_cursor: s=0ee81072e0464b79a154e0a294e0758b;i=172a72;b=9b7a43aca5e642e390edd0705af19aa5;m=ad287df;t=5e9e37ea8b6f6;x=e41da275c552e55c kernel: 5.19.12-300.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 gcal_event_widget_clone at ../src/gui/gcal-event-widget.c:1000 #1 split_event_widget_at_column at ../src/gui/views/gcal-week-header.c:656 #2 apply_overflow_at_weekday at ../src/gui/views/gcal-week-header.c:772 #4 add_event_to_grid at ../src/gui/views/gcal-week-header.c:815 #5 gcal_week_header_add_event at ../src/gui/views/gcal-week-header.c:1650 #6 add_event_to_subscriber at ../src/core/gcal-timeline.c:205 #7 timeline_source_dispatch at ../src/core/gcal-timeline.c:682 #10 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238 #11 g_main_context_iteration at ../glib/gmain.c:4303 #12 g_application_run at ../gio/gapplication.c:2571 Potential duplicate: bug 1476568
Created attachment 1915248 [details] File: backtrace
Created attachment 1915249 [details] File: core_backtrace
Created attachment 1915250 [details] File: cpuinfo
Created attachment 1915251 [details] File: dso_list
Created attachment 1915252 [details] File: environ
Created attachment 1915253 [details] File: exploitable
Created attachment 1915254 [details] File: limits
Created attachment 1915255 [details] File: maps
Created attachment 1915256 [details] File: mountinfo
Created attachment 1915257 [details] File: open_fds
Created attachment 1915258 [details] File: proc_pid_status
Created attachment 1915259 [details] File: var_log_messages
Proposed as a Blocker for 37-final by Fedora user geraldosimiao using the blocker tracking app because: A crashing calendar seems to no use. I think this could be a problem if really reproducible by others.
Some more context for the bug: Calendar stops crashing when I disable a work calendar where colleagues add their holidays/sick days, so it's a calendar with a really high number of events. Not sure how common such calendars are and thus I'm not sure it should be a blocker bug.
Thanks for the context, it should help for today's blocker review meeting.
Discussed during the 2022-10-03 blocker review meeting: [1] The decision to classify this bug as an RejectedBlocker and AcceptedFreezeException was made: "We don't see a widespread issue with this bug and efforts by frantisekz to reproduce it were not fruitful. We accept it as an FE in case a fix is released." [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-10-03/f37-blocker-review.2022-10-03-16.00.log.txt
There is an upstream bug filled [1]. I added there a reproducer data and steps. It seems the problem is there for more than two years (see the duplicate of it), thus I'd say this is safe to be closed here, in favour of the upstream bug. [1] https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/757
Similar problem has been detected: I think I was just rapidly changing weeks by clicking on days in the left calendar view. reporter: libreport-2.17.4 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: gcal_event_widget_clone executable: /usr/bin/gnome-calendar journald_cursor: s=db3469f91acc4f499dc9cdfd1833e372;i=87933;b=4cf256bb06db4580b1396514dc875060;m=219984e4f;t=5eda79521e113;x=7f356b50396efcee kernel: 6.0.8-300.fc37.x86_64 package: gnome-calendar-43.1-3.fc37 reason: gnome-calendar killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.