Ubuntu
libtimezonemap package

Installer crashes after clicking on a time zone

Bug #2012116 reported by spicemines on 2023-03-18

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	libtimezonemap (Ubuntu)	Fix Released	High	Marco Trevisan (Treviño)	Ubuntu ubuntu-23.04-beta
	Lunar	Fix Released	High	Marco Trevisan (Treviño)	Ubuntu ubuntu-23.04-beta

Bug Description

When I reach the "Where are you?" screen, my time zone is not correctly selected. Clicking the map to select my time zone causes the installer to crash without an error message or the option to report an issue. Relaunching the installer from the desktop will fail at the same point, but this time, I get the error message, "ubi-partman failed with exit code 10."

If I go through the installer and DO NOT change the time zone, the installation completes successfully.

I am performing this install with two different Virtual Machine platforms: Virtual Box and Gnome Boxes.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: ubiquity 23.04.4
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.480
CurrentDesktop: XFCE
Date: Sat Mar 18 03:36:03 2023
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

spicemines (spicemines) wrote on 2023-03-18:

Syslog and partman combined Edit (328.5 KiB, text/plain)
Casper.txt Edit (1.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (8.8 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
UbiquityDebug.txt Edit (2.8 KiB, text/plain; charset="utf-8")
UbiquityDm.txt Edit (2.4 KiB, text/plain; charset="utf-8")
UbiquityPartman.txt Edit (140.2 KiB, text/plain; charset="utf-8")
UbiquitySyslog.txt Edit (186.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-03-19:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status:	New → Confirmed

Revision history for this message

Aaron Rainbolt (arraybolt3) wrote on 2023-03-19:

Seeing mostly the same symptoms on Ubuntu MATE Lunar over here, so this problem is not restricted to a single flavor.

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2023-03-19:

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2012116

tags:

added: iso-testing

Revision history for this message

fossfreedom (fossfreedom) wrote on 2023-03-21:

hmm - might be this in the syslog

2023-03-18T02:56:26.750971+00:00 xubuntu kernel: [ 75.529512] traps: ubiquity[1575] general protection fault ip:7f4eca874d91 sp:7ffffdf8f480 error:0 in libtimezonemap.so.1.0.0[7f4eca870000+6000]

Sebastien Bacher (seb128) on 2023-03-21

tags:	added: rls-ll-incoming
affects:	ubiquity (Ubuntu) → libtimezonemap (Ubuntu)
Changed in libtimezonemap (Ubuntu):
importance:	Undecided → High

Revision history for this message

Erich Eickmeyer (eeickmeyer) wrote on 2023-03-21:

Confirmed on Edubuntu.

Changed in libtimezonemap (Ubuntu):
milestone:	none → ubuntu-23.04-beta
importance:	High → Critical
importance:	Critical → High

Revision history for this message

Sebastien Bacher (seb128) wrote on 2023-03-21:

It's a bug in libtimezonemap, it's easier to trigger by using this in the ubiquity source

$ ./plugin-viewer-gtk.py ubi-timezone

it's probably another bug which existed but got more visible with https://gitlab.gnome.org/GNOME/glib/-/issues/2937

==124819== Invalid free() / delete / delete[] / realloc()
==124819== at 0x484620F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==124819== by 0x650B13B: g_slice_free_chain_with_offset (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7600.0)
==124819== by 0x1119CDB7: get_loc_for_xy (cc-timezone-map.c:942)
==124819== by 0x1119D66C: button_press_event (cc-timezone-map.c:961)
==124819== by 0x7C9B916: _gtk_marshal_BOOLEAN__BOXED (gtkmarshalers.c:84)
==124819== by 0x65EA00F: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.0)

reassigning the report to the library

Revision history for this message

Aaron Rainbolt (arraybolt3) wrote on 2023-03-21 (last edit on 2023-03-21):

I see the same segmentation fault that fossfreedom points out also happening in my Ubuntu MATE logs (which are in https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2012159 which is a dupe of this). My very first guess is that this is that GLib update messing us up again with the removed slice allocator.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-03-22:

This bug was fixed in the package libtimezonemap - 0.4.6-3ubuntu1

---------------
libtimezonemap (0.4.6-3ubuntu1) lunar; urgency=medium

  * debian/{control,gbp.conf}: Update with ubuntu references
  * debian/patches: Fix builds with non-/usr prefixes
  * debian/patches: Fix crashes when running in GLib 2.76.
    Do not try to access to a free'd list element. (LP: #2012116)

-- Marco Trevisan (Treviño) <email address hidden> Tue, 21 Mar 2023 23:42:58 +0100

Changed in libtimezonemap (Ubuntu Lunar):
status:	Confirmed → Fix Released

Marco Trevisan (Treviño) (3v1n0) on 2023-03-22

Changed in libtimezonemap (Ubuntu Lunar):
assignee:	nobody → Marco Trevisan (Treviño) (3v1n0)

Revision history for this message

spicemines (spicemines) wrote on 2023-03-23:

#10

This bug appears to be fixed in the latest daily build. I was able to choose my time zone and continue with the installation. The installation finished successfully.

Revision history for this message

spicemines (spicemines) wrote on 2023-03-23:

#11

Do I need to change the title to include a "[Fixed]" tag to indicate this bug has been fixed?

Revision history for this message

Erich Eickmeyer (eeickmeyer) wrote on 2023-03-23:

#12

spicemines,

No, the "Fix Released" status is all that is needed. Furthermore, the comment by Launchpad Janitor was all the confirmation that was needed. Thank you!