** Changed in: gnome-clocks (Ubuntu)
Importance: Medium => High
** Changed in: gnome-clocks (Ubuntu)
Status: New => Fix Committed
** Description changed:
+ * Impact
+ The clocks software segfault on some locations
+
+ * Test case
+ - set the timezone ot Ambler (Alaska), clocks shouldn't segfault
+
+ * Regression potential
+ Check that the day start/end value look right
+
+ -----------------
+
after view the world clock
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-clocks 3.36.0-1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed Apr 15 16:37:26 2020
ExecutablePath: /usr/bin/gnome-clocks
ExecutableTimestamp: 1583690450
InstallationDate: Installed on 2020-03-20 (26 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
ProcCmdline: /usr/bin/gnome-clocks --gapplication-service
ProcCwd: /home/fabio
SegvAnalysis:
- Segfault happened at: 0x7f35030f3300 <g_date_time_to_timezone+16>: mov
0x10(%rdi),%esi
- PC (0x7f35030f3300) ok
- source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed
readable region)!
- destination "%esi" ok
+ Segfault happened at: 0x7f35030f3300 <g_date_time_to_timezone+16>: mov
0x10(%rdi),%esi
+ PC (0x7f35030f3300) ok
+ source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed
readable region)!
+ destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-clocks
StacktraceTop:
- g_date_time_to_instant (datetime=0x0) at ../../../glib/gdatetime.c:2709
- g_date_time_to_timezone (datetime=datetime@entry=0x0, tz=0x561a2dbb4220) at
../../../glib/gdatetime.c:2709
- clocks_world_item_calculate_riseset (self=0x561a2d9f6620 [ClocksWorldItem])
at src/25a6634@@gnome-clocks@exe/world.c:1341
- clocks_world_item_real_tick (self=0x561a2d9f6620 [ClocksWorldItem]) at
src/25a6634@@gnome-clocks@exe/world.c:2068
- <emit signal ??? on instance 0x561a2d9f6620 [ClocksWorldItem]>
(instance=instance@entry=0x561a2d9f6620, signal_id=<optimized out>,
detail=detail@entry=0) at ../../../gobject/gsignal.c:3554
+ g_date_time_to_instant (datetime=0x0) at ../../../glib/gdatetime.c:2709
+ g_date_time_to_timezone (datetime=datetime@entry=0x0, tz=0x561a2dbb4220) at
../../../glib/gdatetime.c:2709
+ clocks_world_item_calculate_riseset (self=0x561a2d9f6620 [ClocksWorldItem])
at src/25a6634@@gnome-clocks@exe/world.c:1341
+ clocks_world_item_real_tick (self=0x561a2d9f6620 [ClocksWorldItem]) at
src/25a6634@@gnome-clocks@exe/world.c:2068
+ <emit signal ??? on instance 0x561a2d9f6620 [ClocksWorldItem]>
(instance=instance@entry=0x561a2d9f6620, signal_id=<optimized out>,
detail=detail@entry=0) at ../../../gobject/gsignal.c:3554
Title: gnome-clocks crashed with SIGSEGV in g_date_time_to_instant()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
separator:
** Description changed:
* Impact
The clocks software segfault on some locations
* Test case
- set the timezone ot Ambler (Alaska), clocks shouldn't segfault
+
+ the reports on e.u.c should also stop with the update
+ https://errors.ubuntu.com/problem/cdecc860143394fca4bd7a1eb2650a0865dcc9a2
* Regression potential
Check that the day start/end value look right
-----------------
after view the world clock
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-clocks 3.36.0-1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed Apr 15 16:37:26 2020
ExecutablePath: /usr/bin/gnome-clocks
ExecutableTimestamp: 1583690450
InstallationDate: Installed on 2020-03-20 (26 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
ProcCmdline: /usr/bin/gnome-clocks --gapplication-service
ProcCwd: /home/fabio
SegvAnalysis:
Segfault happened at: 0x7f35030f3300 <g_date_time_to_timezone+16>: mov
0x10(%rdi),%esi
PC (0x7f35030f3300) ok
source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed
readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-clocks
StacktraceTop:
g_date_time_to_instant (datetime=0x0) at ../../../glib/gdatetime.c:2709
g_date_time_to_timezone (datetime=datetime@entry=0x0, tz=0x561a2dbb4220) at
../../../glib/gdatetime.c:2709
clocks_world_item_calculate_riseset (self=0x561a2d9f6620 [ClocksWorldItem])
at src/25a6634@@gnome-clocks@exe/world.c:1341
clocks_world_item_real_tick (self=0x561a2d9f6620 [ClocksWorldItem]) at
src/25a6634@@gnome-clocks@exe/world.c:2068
<emit signal ??? on instance 0x561a2d9f6620 [ClocksWorldItem]>
(instance=instance@entry=0x561a2d9f6620, signal_id=<optimized out>,
detail=detail@entry=0) at ../../../gobject/gsignal.c:3554
Title: gnome-clocks crashed with SIGSEGV in g_date_time_to_instant()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
separator:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873077
Title:
gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-clocks/+bug/1873077/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
