Software Updater window is invisible
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update notifier |
New
|
Undecided
|
Unassigned | ||
update-notifier (Ubuntu) |
Confirmed
|
Critical
|
Unassigned |
Bug Description
The software Updater icon has just appeared in my Launcher (it's probably trying to tell me that there are updates available, but who knows really). However, the window cannot be accessed in any way.
By clicking on the launcher icon, a small arrow appears on the right of it, and the title "Software Updater" appears on the top screen title bar (see screenshot), but no window becomes visible.
By hitting Alt+Tab, Software Updater is not even in the list of the available windows: this is an inconsistency that, no matter whether or not there's a bug in Software Updater itself, reveals a lower level bug in Unity (or whatever system component is responsible for switching windows), as there must ALWAYS be a 1:1 correspondence between open windows listed in Launcher and windows available via Alt+TAB.
I don't know whether this is related to bug #1671529, but there is a difference (I'm almost sure of): in the case of that one the window was available via Alt+TAB, though it wouldn't show up if selected.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: update-manager 1:16.04.5
ProcVersionSign
Uname: Linux 4.4.0-64-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 9 17:07:38 2017
DpkgHistoryLog.txt:
DpkgTerminalLog
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InstallationDate: Installed on 2013-10-11 (1244 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitec
SourcePackage: update-manager
UpgradeStatus: Upgraded to xenial on 2016-12-11 (87 days ago)
affects: | update-manager (Ubuntu) → update-notifier (Ubuntu) |
Changed in update-notifier (Ubuntu): | |
importance: | Undecided → Critical |
description: | updated |
tags: | added: bionic |
What??
#1623856 doesn't look like the same bug at all.