I'm not very sure, but I think the update process is not really affected by the bug. The package index might be refreshed before the bug is triggered, so in this case you could update the packages (maybe restart KPackageKit and see if the updates are there).
If this doesn't work, open a terminal and type: sudo apt-get update
This will update the package index manually and after that you should be able to install the updates from KPackageKit, or via command line: sudo apt-get upgrade
Also, you might wanna look at the output of command `sudo apt-get update' and see which sources give errors (for example 404 errors), and disable those sources in KPackageKit -> Settings -> Edit Software Sources. Disabling the source that was giving errors will make KPackageKit work again, even without the bug fix.
I'm not very sure, but I think the update process is not really affected by the bug. The package index might be refreshed before the bug is triggered, so in this case you could update the packages (maybe restart KPackageKit and see if the updates are there).
If this doesn't work, open a terminal and type: sudo apt-get update
This will update the package index manually and after that you should be able to install the updates from KPackageKit, or via command line: sudo apt-get upgrade
Also, you might wanna look at the output of command `sudo apt-get update' and see which sources give errors (for example 404 errors), and disable those sources in KPackageKit -> Settings -> Edit Software Sources. Disabling the source that was giving errors will make KPackageKit work again, even without the bug fix.