gnome-keyring problem effects power manager

Bug #1193595 reported by markling on 2013-06-22
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

I'm reporting this as further info for this gnome-keyring error: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877

(Couldn'd add this report to that bug because Launchpad couldn't find any gnome keyring errors when I asked it to check. I presume it was only prepared to look for xfce4-power-manager bugs. This is neverthless a report of further failures related to this keyring problem.)

This happened:

Machine idle without much ado for some minutes after startup.
Clicked icon to permit software updates.
Entered PASSWORD.
Pressed install.
Left computer. Came back.
Keyring PASSWORD request window was active.
Software Updater had left an ERROR MESSAGE: update failed.
Yet the Software Updater icon indicated 'restart required'.
Entered PASSWORD for the keyring form.
Pressed the Software Updater's restart icon.
The reboot then asked for a PASSWORD as well.
The PASSWORD request came with an ERROR MESSAGE: "System policy prevents reboot when other users are logged in".
Paused just a few moments while contemplating my distrust of all this PASSWORD gubbins and now this business of other users being logged in. (for further distrust and dismay over the keyring problem, see bug #575877).
The reboot form was impatient. It disappeared.
Another ERROR MESSAGE appeared: "Reboot failed. Failed to request reboot. Please shutdown manually".

The authentication log had this to say about it: see attached. (It's now 11.18am. I've been doing this report for about half an hour. You can see that CRON has meanwhile been opening and closing a root session like it was doing the can-can.)

"Is this bug a security vulnerability?"

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xfce4-power-manager 1.2.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Uname: Linux 3.8.0-25-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sat Jun 22 10:47:23 2013
InstallationDate: Installed on 2012-11-28 (205 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: xfce4-power-manager
UpgradeStatus: Upgraded to raring on 2013-05-14 (38 days ago)

markling (markling) wrote :
Lionel Le Folgoc (mrpouit) wrote :

That's a known ubuntu bug, unrelated to gnome-keyring and xfce4-power-manager, see <http://askubuntu.com/questions/1190/how-can-i-make-shutdown-not-require-admin-password> for instance.

affects: xfce4-power-manager (Ubuntu) → ubuntu
markling (markling) wrote :

Thank you Lionel. From a user's perspective, it seems to be related to the keyring problem because it has arisen simultaneously and is characterised by an unwanted request for a password.

The link you've provided is a little worrying because I was the only person logged into my computer when this happened. In other words, as far as I was aware, I was the only person logged in.

The problem has not repeated in the short time since I reported it.

It is however a bug, dutifuly reported! Do you happen to know what it's related to if not xfce4-power-manager or gnome keyring? These were the processes that were running when the power manager asked me to give up my gnome keyring.

It's not yet inconvenienced me enough to make me look on the forums for a workaround.

But it is most worrying as a potential security issue. Is this bug (please see in relation to bug #575877) a security issue?

My machine just asked for my password to unlock the keyring again. I have presumed this is an error, since it is new, eratic, without sense or reason, and full of foreboding.

Quinn Balazs (qbalazs) on 2013-08-14
affects: ubuntu → gnome-keyring (Ubuntu)
affects: gnome-keyring (Ubuntu) → ubuntu
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers