Ubuntu
update-manager package

check-new-release-gtk "Ask me later" button doesn't work

Bug #878157 reported by iGadget on 2011-10-19

This bug report is a duplicate of: Bug #873424: ask me later fails. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	update-manager (Ubuntu)	New	Undecided	Unassigned

Bug Description

When clicking on the button named "Ask Me Later" in the Ubuntu 11.10 Upgrade notification window (presumably check-new-release-gtk), nothing happens. See the attached video.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.150.3
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
Date: Wed Oct 19 14:30:01 2011
EcryptfsInUse: Yes
GConfNonDefault:
/apps/update-manager/check_new_release_ignore=
/apps/update-manager/first_run=false
/apps/update-manager/show_details=true
/apps/update-manager/window_size=(637,713)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en
LANG=nl_NL.utf8
LC_MESSAGES=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

iGadget (igadget) wrote on 2011-10-19:

20111019 - Oneiric upgrade window doesn't respond to %22Ask me later%22-button.ogv Edit (1.4 MiB, video/ogg)
CurrentDmesg.txt.txt Edit (245.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.6 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt.txt Edit (1.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt.txt Edit (26.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-10-19:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #873424, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.