Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libical3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions:
Correction: Applying following patch does not solve this assertion
failure:
diff --git a/src/engine-eds.cpp b/src/engine-eds.cpp
index 153a9ea..8e2674f 100644
--- a/src/engine-eds.cpp
+++ b/src/engine-eds.cpp
@@ -879,6 +879,11 @@ private:
if (tzid == nullptr)
return nullptr;
The underlying issue is that
i_cal_timezone_get_builtin_timezone_from_tzid and
i_cal_timezone_get_builtin_timezone included from /usr/include/libical-
glib/i-cal-timezone.h (libical-dev) fail to determine the timezone for
"Etc/Utc" or "Etc/UTC".
** Also affects: libical3 (Ubuntu)
Importance:
Setting as rls-ff-notfixing since from a Desktop Team
perspective/workflow it's our of our active set now and we are not going
to consider it as a blocker. It's just a workflow detail though and
doesn't mean the bug shouldn't be/isn't going to be fixed
** Tags removed: rls-ff-incoming
** Tags
Here is the backtrace:
Thread 1 "indicator-datet" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht
gefunden.
(gdb) bt
#0 0x76eaa3eb in __GI_raise
Could you get a backtrace using gdb?
** Tags added: rls-ee-incoming rls-ff-incoming
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1848969
I am not the only one running into this bug: https://ubuntu-
mate.community/t/clock-indicator-wont-appear-19-10/20424
** Changed in: indicator-datetime (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
7 matches
Mail list logo
