adept notifier runs during adept-instigated dist-upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier-kde (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: adept
During a distribution upgrade, started through Adept Manager via the --version-upgrade switch, adept_notifier continues to run. This can be confusing to users because it is not apparent that the dist-upgrade process and adept_notifier are referring to the same set of updates. Users may believe that, even though they're in the middle of a major upgrade, there are already updates available for it. A friend of mine who decided to install Kubuntu (Dapper Drake) after seeing it on my system, did so three or four days before Feisty Fawn came out. When Feisty came out, he was notified of its availability, and started the upgrade process. Shortly thereafter he called me up wondering why he was installing 900 or so packages _and_ there were already 900 or so updates available.
Because the Adept Distribution Upgrade guides the user through the process so cleanly and keeps the user so well informed on its progress, it's redundant and confusing to have adept_notifier running at the same time. Something as simple as 'kill `pidof adept_notifier`' during the "Preparing the upgrade" phase of the Adept-driven Distribution Upgrade would clear up this confusion.
This is how its been for a while, and I don't really know what the ideal fix should look like. I'm thinking that instead of not showing adept_notifier, it should show some form of icon to indicate that adept is busy. I think it should do that pretty much anytime that adept is open.
Thoughts?