Multiple instances of "Ubuntu XX.YY Upgrade Available" (check-new-release-gtk) dialog

Bug #785296 reported by Daniel Richard G.
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

This concerns update-manager 1:0.142.23 in Ubuntu Maverick.

An "Ubuntu 11.04 Upgrade Available" dialog window pops up. If I'm not around to click it away, then about a half hour later, another one pops up. Some time later, another window.

I come back the next day, and see more than a dozen such windows littering my desktop.

This may have to do with bug #784130, which appears to prevent the "Don't Upgrade" option from sticking.

Revision history for this message
RedSingularity (redsingularity) wrote :

Sorry for the delay. Are you still seeing this with the most recent updates?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Daniel Richard G. (skunk) wrote :

I'm on Natty now, and I'm not currently seeing this behavior. This is likely due to the fact that there is no newer release available yet, however, so check-new-release-gtk is not yet active.

Revision history for this message
RedSingularity (redsingularity) wrote :

Alright. If you get a chance to test it, just report back here with results. I will grab an up-to-date ISO of 10.10 and try it out as well.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in update-manager (Ubuntu):
assignee: nobody → RedSingularity (redsingularity)
Revision history for this message
RedSingularity (redsingularity) wrote :

Well it seems to be fine now. Had the machine running for 2 hours with the dialog box open. No more seemed to open up behind it. Closing report. Thanks for reporting though, and please feel free to do so again with any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in update-manager (Ubuntu):
status: New → Invalid
assignee: RedSingularity (redsingularity) → nobody
Revision history for this message
Daniel Richard G. (skunk) wrote :

RedSingularity, please note that this error (as far as I'm aware) only occurs when the home directory is being served from AFS. This scenario breaks common assumptions held by many programs (that the homedir is always accessible/writable) and is thus more likely than not the ultimate cause of this bug.

You may be able to simulate the effect of expired Kerberos/AFS authentication by logging in, allowing the desktop to load and settle, and then invoking "chmod 000 $HOME". (chown'ing the directory as root may help, too, to prevent user programs from chmod'ing things back.) This only represents a partial simulation, however, as under AFS only some processes may be unable to access a given directory (depending on the process group that they are in). If there are any update-manager processes that do not run in the same process group as the rest of the desktop, yet expect to access the homedir, this may be an issue.

The fix needed here, I suspect, is something that doesn't involve the filesystem at all. For example, setting an X property on the root to ensure that only one instance of the window exists.

Changed in update-manager (Ubuntu):
status: Invalid → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.