Ubuntu
update-manager package

no notification about incorrect password

Bug #673979 reported by mlg7 on 2010-11-11

This bug report is a duplicate of: Bug #298217: no second attempt and no feedback when wrong password entered. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: update-manager

1. Start update manager
2. Press [check] or [install] buttons
3. enter an incorrect password (variation: enter password in wrong keyboard layout, e.g. password is in English while the current layout is Russian/Chinese/Hebrew/etc.)

Actual: something happens, but nothing is really done, no indication of incorrect password.

Expected: a message like "incorrect password, please check the CAPS key and the keyboard layout. Currently: CAPS ON, Layout=Russian"

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: update-manager 1:0.134.11
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic-pae 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic-pae i686
Architecture: i386
Date: Thu Nov 11 14:46:47 2010
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: update-manager

Tags:

Revision history for this message

mlg7 (mlg7) wrote on 2010-11-11:

Dependencies.txt Edit (5.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (34.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (767 bytes, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-02-15:

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 #578688, 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.