https://bugzilla.redhat.com/show_bug.cgi?id=2196063
Bug ID: 2196063 Summary: [abrt] gnome-calendar: on_calendar_monitor_completed_cb(): gnome-calendar killed by SIGABRT Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:774e75e519e48b0b8e6e9562ea89da0b5fc6e38a;VAR IANT_ID=workstation; Component: gnome-calendar Assignee: gnome-sig@lists.fedoraproject.org Reporter: ice_qub3@protonmail.com QA Contact: extras-qa@fedoraproject.org CC: epel-packagers-sig@lists.fedoraproject.org, gnome-sig@lists.fedoraproject.org, igor.raits@gmail.com, klember@redhat.com Target Milestone: --- Classification: Fedora
Description of problem: I tried adding a protonmail calander share link into the calander app, but it crashed
Version-Release number of selected component: gnome-calendar-44.1-1.fc38
Additional info: reporter: libreport-2.17.9 type: CCpp reason: gnome-calendar killed by SIGABRT journald_cursor: s=5f6cdd2ccacb47d980c17e321cba366e;i=4dce;b=9328860e87ea40dda685ecb062e5f865;m=80eac649;t=5fb1c8f41e320;x=1d48fa4e450888e5 executable: /usr/bin/gnome-calendar cmdline: /usr/bin/gnome-calendar --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-org.gnome.Calendar@0.service rootdir: / uid: 1000 kernel: 6.2.14-300.fc38.x86_64 package: gnome-calendar-44.1-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-calendar gnome-calendar-44.1-1.fc38.x86_64 (Fedora Project) 1683470020 backtrace_rating: 4 crash_function: on_calendar_monitor_completed_cb comment: I tried adding a protonmail calander share link into the calander app, but it crashed
Truncated backtrace: Thread no. 1 (9 frames) #6 on_calendar_monitor_completed_cb at ../src/core/gcal-timeline.c:579 #8 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3812 #12 g_object_notify_by_spec_internal at ../gobject/gobject.c:1552 #13 g_object_notify_by_pspec at ../gobject/gobject.c:1658 #14 set_complete at ../src/core/gcal-calendar-monitor.c:1044 #15 complete_in_idle_cb at ../src/core/gcal-calendar-monitor.c:1167 #19 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #20 g_main_context_iteration at ../glib/gmain.c:4343 #21 g_application_run at ../gio/gapplication.c:2573
Potential duplicate: bug 1883681
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #1 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963079 --> https://bugzilla.redhat.com/attachment.cgi?id=1963079&action=edit File: proc_pid_status
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #2 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963080 --> https://bugzilla.redhat.com/attachment.cgi?id=1963080&action=edit File: maps
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #3 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963081 --> https://bugzilla.redhat.com/attachment.cgi?id=1963081&action=edit File: limits
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #4 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963082 --> https://bugzilla.redhat.com/attachment.cgi?id=1963082&action=edit File: environ
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #5 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963083 --> https://bugzilla.redhat.com/attachment.cgi?id=1963083&action=edit File: open_fds
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #6 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963084 --> https://bugzilla.redhat.com/attachment.cgi?id=1963084&action=edit File: mountinfo
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #7 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963085 --> https://bugzilla.redhat.com/attachment.cgi?id=1963085&action=edit File: os_info
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #8 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963086 --> https://bugzilla.redhat.com/attachment.cgi?id=1963086&action=edit File: cpuinfo
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #9 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963087 --> https://bugzilla.redhat.com/attachment.cgi?id=1963087&action=edit File: core_backtrace
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #10 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963088 --> https://bugzilla.redhat.com/attachment.cgi?id=1963088&action=edit File: var_log_messages
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #11 from Yuval Sivan ice_qub3@protonmail.com --- Created attachment 1963089 --> https://bugzilla.redhat.com/attachment.cgi?id=1963089&action=edit File: backtrace
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #12 from Yaroslav Pronin proninyaroslav@mail.ru --- Trying to sync Google calendar after turning it off and on in the Account Settings.
reporter: libreport-2.17.9 runlevel: N 5 cmdline: /usr/bin/gnome-calendar --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-dbus\x2d:1.2\x2dorg.gnome.Calendar.slice/dbus-:1.2-org.gnome.Calendar@0.service rootdir: / package: gnome-calendar-44.1-1.fc38 crash_function: on_calendar_monitor_completed_cb type: CCpp uid: 1000 journald_cursor: s=f85c0808722542538e1175850923ccc7;i=65f8;b=a26e13581ed04fb68d0e8bedce387b87;m=2b58e4351;t=5fb8235c0a218;x=3d52349d0c9e63ac reason: gnome-calendar killed by SIGABRT comment: Trying to sync Google calendar after turning it off and on in the Account Settings. kernel: 6.2.14-300.fc38.x86_64 executable: /usr/bin/gnome-calendar backtrace_rating: 4
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #13 from plumf@open-plug.eu --- No specific context for this bug ..
reporter: libreport-2.17.10 type: CCpp reason: gnome-calendar killed by SIGABRT journald_cursor: s=53cef9b2678e407e8430d05e3184f31d;i=1979b;b=ad644d6cb9034ac7a3b0caaeef1fec62;m=495f38ab8;t=5fd35ca49b1be;x=5de319e6357b1513 executable: /usr/bin/gnome-calendar cmdline: /usr/bin/gnome-calendar --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-org.gnome.Calendar@0.service rootdir: / uid: 1000 kernel: 6.3.4-201.fc38.x86_64 package: gnome-calendar-44.1-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: on_calendar_monitor_completed_cb comment: No specific context for this bug ..
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #14 from Jan Vlug jan.public@famvlug.nl --- I tried to setup a Nextcloud online GNOME account. Probably related to: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2613
reporter: libreport-2.17.11 type: CCpp reason: gnome-calendar killed by SIGABRT journald_cursor: s=42f341ee091748d7bd499b947194d15e;i=ad167b;b=d39a6ae4010b4a3dbbb702d84d006d5f;m=2615feae8a;t=6037468b7562f;x=bcbb6271126ac5b2 executable: /usr/bin/gnome-calendar cmdline: /usr/bin/gnome-calendar --gapplication-service rootdir: / uid: 1000 kernel: 6.4.10-200.fc38.x86_64 package: gnome-calendar-44.1-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: on_calendar_monitor_completed_cb
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
--- Comment #15 from Sergiu sergiu@spruteanu.com --- it happened after I removed a local calendar from the `Manage calendars`
reporter: libreport-2.17.11 type: CCpp reason: gnome-calendar killed by SIGABRT journald_cursor: s=9c1fee4d5c71424481f24d8310d4f46d;i=75ce;b=6cbab18587e843c1b77a9aefca8f47a0;m=16df3181a;t=607afa5eff124;x=65d0cb8e23385f84 executable: /usr/bin/gnome-calendar cmdline: /usr/bin/gnome-calendar --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-org.gnome.Calendar@0.service rootdir: / uid: 1000 kernel: 6.5.6-200.fc38.x86_64 package: gnome-calendar-44.1-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-calendar gnome-calendar-44.1-1.fc38.x86_64 (Fedora Project) 1697283397 comment: it happened after I removed a local calendar from the `Manage calendars` backtrace_rating: 4 crash_function: on_calendar_monitor_completed_cb
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
Aoife Moloney amoloney@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |EOL Status|NEW |CLOSED Last Closed| |2024-05-21 14:57:25
--- Comment #16 from Aoife Moloney amoloney@redhat.com --- Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.
Fedora Linux 38 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.
epel-packagers-sig@lists.fedoraproject.org