#540 closed defect (fixed)

Fix the Dom0's update button

Reported by: joanna Owned by: marmarek
Priority: major Milestone: Release 1
Component: core Keywords:
Cc: aga

Description

It currently does nothing... (even if it really does soemthing, it looks to the user as if it was doing nothing).

Change History (18)

comment:2 Changed 13 months ago by joanna

  • Resolution fixed deleted
  • Status changed from closed to reopened

There is still a long delay between the time the button is pressed, and when the gpk-viewer window is presented to the user. Such delay suggests to the user that nothing happens, and then when the gpk-viewer window suddenly appears 30 secs later, the user already forgot that he or she initiated the update process, and is now only confused where this window came out.

In other words, we need some progress bar window in between.

comment:3 Changed 13 months ago by joanna

And, BTW, the check-for-udpdate in the manager for Dom0 doesn't go away after I checked the updates and got information that there were no updates available.

comment:4 Changed 13 months ago by joanna

The same applies to other VMs -- if no updates are ready, the check-for-updates icon will persist...

comment:5 Changed 13 months ago by joanna

And, BTW, it still doesn't really work -- it always seems to show that there are no updates available, even though I just uploaded some updates, and qubes-dom0-updates picks them up correctly.

comment:7 Changed 13 months ago by joanna

  • Resolution set to fixed
  • Status changed from reopened to closed

Seems to be working fine now.

comment:8 Changed 12 months ago by joanna

  • Resolution fixed deleted
  • Status changed from closed to reopened

1-click updates for Dom0 still don't work -- the packages offered in gpk-viewer is only a SUBSET of all the available packages as displayed by qubes-dom0-update. Perhaps there is a missing yum clean call somewhere?

comment:9 Changed 12 months ago by joanna

core-dom0 2.0.23, manager 1.2.17

comment:10 Changed 12 months ago by marmarek

gpk-update-viewer groups updates (so eg xen-* is listed as one update). Perhaps this is the source of difference? You can always expand updates tree.

comment:11 Changed 12 months ago by joanna

No, I just uploaded new manager package, and gpk-viewer didn't display it -- it only displayed the kernel-qubes-vm 3.3.5 (that I removed from my system). So, it seems like it doesn't notice just-uploaded-very-recently packages...

comment:12 Changed 12 months ago by marmarek

  • Component changed from graphical-manager to core
  • Owner changed from joanna to marmarek
  • Status changed from reopened to assigned

comment:13 Changed 12 months ago by marmarek

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:14 Changed 11 months ago by joanna

  • Resolution fixed deleted
  • Status changed from closed to reopened

As of core-dom0 2.0.27 and manager 1.2.20, this still doesn't work. Again, I just uploaded new rpms into the repos, then clicked on the Dom0 update button, and then got an empty gpk-viewer window telling me there were no updates available. So, I then typed qubes-dom0-update in the command line, and it immediately correctly found the updates. I suspect the update procedure via the manager doesn't do proper 'yum clean all'...

comment:15 Changed 11 months ago by marmarek

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:16 Changed 11 months ago by joanna

  • Resolution fixed deleted
  • Status changed from closed to reopened

As of qubes-manager 1.2.22 this still doesn't work -- again gpk-viewer shows no updates, while qubes-dom0-updates correctly shows some new updates.

comment:17 Changed 11 months ago by marmarek

  • Status changed from reopened to accepted

comment:18 Changed 11 months ago by marmarek

  • Resolution set to fixed
  • Status changed from accepted to closed

Another try:
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=ad7d6957b133b6a52e58e3ce2a5730d3bf46109b

Calling "yum clean all" as normal user doesn't return any error, but looks like also doesn't clean the cache...

Note: See TracTickets for help on using tickets.