If one installs many updates the list of items in the plasmoid window scrolls down. If the last item was downloaded the installation begins, yet the user does not see this because the list remains at the bottom and does not scroll to the beginning to show the packages currently being installed. Expected behaviour: scroll the list to the top if the installation starts and follow the currently installing package down the list. Reproducible: Always
Your backend is broken, it should emit a new package once one of it's taks is finished, ie emit: package k3b downloading progress: downloading 15% progress: downloading 99 % progress: finished 100% now a new package must be emitted: package k3b installing progress: uncompress 10% progress: installing 95% progress: finished 100% That's how all backends behave, from this I believe you use zypp one... In aptcc I even prefres to emit the package before every progress so I get package summaries if I connect to a transaction the was already running.
If I check the list I see that the progress info for the first package is re-used for showing the installation progress. So if that is possible, the applet knows that it is as item1 in the list but still does not scroll to it. I do not see what this has to do with the backend.
Some results when using oxygen style Also qt4 package version 4.8.5-6 (Arch Linux), kdelibs 4.11.97-1
Oups wrong bug ...sorry!! (In reply to comment #3) > Some results when using oxygen style > Also qt4 package version 4.8.5-6 (Arch Linux), kdelibs 4.11.97-1
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!