evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke()

Bug #2012294 reported by Khairul Aizat Kamarudzzaman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
New
Medium
Unassigned

Bug Description

crashed when login to x11 session

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: evolution-data-server 3.47.3-1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 21 00:27:25 2023
Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0
ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify
InstallationDate: Installed on 2020-06-25 (997 days ago)
InstallationMedia:

JournalErrors:
 Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation.
 Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed
ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify
SegvAnalysis:
 Segfault happened at: 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0
 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 ?? ()
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago)
UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo
separator:

Revision history for this message
Khairul Aizat Kamarudzzaman (fenris) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_closure_invoke (closure=0x564dafb6e6d0, return_value=0x0, n_param_values=2, param_values=0x7ffe7baf0340, invocation_hint=0x7ffe7baf02c0) at ../../../gobject/gclosure.c:832
 signal_emit_unlocked_R.isra.0 (node=node@entry=0x564dafa40b80, detail=detail@entry=552, instance=instance@entry=0x564dafac44a0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffe7baf0340) at ../../../gobject/gsignal.c:3802
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffe7baf0500) at ../../../gobject/gsignal.c:3555
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../../../gobject/gsignal.c:3612

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution-data-server (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.