gnome-maps fails to start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Maps |
Fix Released
|
Unknown
|
|||
gnome-maps (Ubuntu) |
Fix Released
|
High
|
fossfreedom | ||
Focal |
Fix Released
|
High
|
fossfreedom |
Bug Description
[Impact]
* GNOME Maps on focal no longer starts.
* From the upstream report this is because the GNOME Maps
data provider no longer provides the satellite data
that the app required.
https:/
Upstream bug report https:/
* GNOME Maps is a component of Ubuntu Budgie packageset. It's a universe package
[Test Plan]
* Simply start the application on Focal. The application will not start.
* Next enable the proposed repository via Update Manager - Settings
* Via a terminal install the application
gnome-maps
* disable the proposed repository again via Update Manager - Settings. This is important so that you dont install any other test packages
* Run gnome-maps via your chosen Desktop Environment - e.g. in Budgie - Menu - Maps
* The application will open displaying a map
[Where problems could occur]
* Confusion on behalf of the user because they may be used to seeing
the Satellite View.
The patched gnome-maps disables Satellite View.
Note - in 21.04 and 21.10 versions of GNOME Maps, Satellite View is also not available. So this is not a regression, but for Focal users its an obvious visual change.
* This fix applies the upstream commit that states that it resolves this matter. No other commits are mentioned on the upstream bug report.
* I suppose the risk is that an additional commit may have been made upstream that upstream silently applied but did not show up in the patch report.
* As such, the user testing this should be fairly familiar with gnome maps previously to confirm no additional regressions for the now working application i.e. previously the app did not run.
[Other Info]
* Please note - on the upstream bug report, the maintainers state that the accepted fixed version of the 3.36 series is 3.36.7.
* Focal is on 3.36.1. From a SRU point of view I would prefer if Focal was to move to the upstream maintainers recommended micro version release.
* However, I don't see any test suite in the application source code. I'm not sure therefore that Ubuntu's SRU process would accept such a microrelease without an OK from a technical board member?
* If such an exception is OK'd I'm happy to run through an uplift - possibly via a separate raised bug report - please advise.
----
I just installed gnome-maps-3.36.1, but when I use "gnome-maps" on the command line I get the
error:
JS WARNING: [resource:
(org.gnome.
_createTileSour
_createCachedSo
createAerialSou
_init@resource:
_init@resource:
_createWindow@
vfunc_activate@
main@resource:
run@resource:
start@resource:
@/usr/bin/
gnome-maps does not open. My OS is Ubuntu 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSign
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 3 03:53:39 2021
InstallCmdLine: BOOT_IMAGE=
InstallationDate: Installed on 2020-12-04 (180 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)
affects: | ubuntu → gnome-maps (Ubuntu) |
Changed in linuxmint: | |
importance: | Unknown → High |
Changed in linuxmint: | |
importance: | High → Unknown |
status: | Unknown → New |
tags: | removed: ubiquity-20.04.15.2 |
Changed in gnome-maps (Ubuntu Focal): | |
assignee: | nobody → fossfreedom (fossfreedom) |
importance: | Undecided → High |
description: | updated |
Changed in gnome-maps (Ubuntu Focal): | |
status: | New → In Progress |
Changed in gnome-maps (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in gnome-maps: | |
status: | Unknown → New |
Changed in gnome-maps: | |
status: | New → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.