Your message dated Mon, 10 Nov 2025 00:29:26 -0500
with message-id
<CAAajCMZodSzHOcWNBJbVA1uqsyo=djgxc1ruxjf_rco37uk...@mail.gmail.com>
and subject line closing old evolution bugs
has caused the Debian Bug report #804778,
regarding evolution-dbg seems not working
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
804778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804778
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: evolution-dbg
Version: 3.18.1-1
Severity: important
I opened a bug upstream, and I am asked about providing information on
an evolution SIGSEGV, so I installed all evolution*-dbg packages and
run evolution via gdb.
The problem is that gdb command "bt full" does not correctly show files
and line numbers.
More information is available at
https://bugzilla.gnome.org/show_bug.cgi?id=757789
Thanks,
Giuseppe
P.S. Should I reassign this bug report against evolution source
package?
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
