[Bug 355560] New: yast2 sw_single displays animated color splash instaed of progress bar
https://bugzilla.novell.com/show_bug.cgi?id=355560 Summary: yast2 sw_single displays animated color splash instaed of progress bar Product: openSUSE 11.0 Version: Alpha 1 Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: jsrain@novell.com CC: sh@novell.com, casualprogrammer@yahoo.com, crrodriguez@novell.com Found By: Beta-Customer When running yast2 sw_single it goes through a sequence of reading and refreshing the repositories registered. On some of the most lengthy operations there is now an animated blue splash instead of a progress bar. As the cursor already shows the busy status, this should definitely show a progress bar, so the user can estimate the required time. If this is a bug, please fix. If it is a new design idea, please scrap and go back to the previous state ( progress bar ) Notebook: Fujitsu Siemens Amilo Si 1520 Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express Monitor: QUANTADISPLAY LCD Monitor 1280x800@60Hz Wireless: Intel PRO/Wireless 3945ABG Network Connection Sound: 82801G (ICH7 Family) High Definition Audio Controller Desktop: gnome2-SuSE-10.3-142 YaST GUI: yast2-qt-2.16.17-6 OS: openSUSE 11.0 (i586) Alpha1 VERSION = 11.0 Kernel: 2.6.24-rc8-git2-3-default rpm -qa | grep yast2 | sort autoyast2-2.16.6-3 autoyast2-installation-2.16.6-3 yast2-2.16.21-3 yast2-add-on-2.16.0-33 yast2-add-on-creator-2.16.3-13 yast2-apparmor-2.1-65 yast2-autofs-2.15.3-9 yast2-backup-2.16.1-14 yast2-bluetooth-2.15.4-46 yast2-bootloader-2.16.3-14 yast2-ca-management-2.16.4-13 yast2-control-center-2.16.0-14 yast2-control-center-gnome-2.13.2-139 yast2-control-center-qt-2.16.0-14 yast2-core-2.16.22-3 yast2-core-devel-2.16.22-3 yast2-country-2.16.5-12 yast2-country-data-2.16.5-12 yast2-devel-doc-2.16.21-3 yast2-devtools-2.16.3-10 yast2-dirinstall-2.16.0-23 yast2-dns-server-2.16.1-13 yast2-fingerprint-reader-2.16.2-13 yast2-firewall-2.15.8-45 yast2-firstboot-2.16.2-26 yast2-ftp-server-2.15.9-65 yast2-gtk-2.16.1-3 yast2-hardware-detection-2.16.0-18 yast2-http-server-2.15.9-14 yast2-inetd-2.15.1-82 yast2-installation-2.16.9-6 yast2-instserver-2.15.4-79 yast2-irda-2.15.1-132 yast2-iscsi-client-2.16.2-19 yast2-iscsi-server-2.14.4-6 yast2-kdump-2.16.9-6 yast2-kerberos-client-2.16.1-13 yast2-kerberos-server-2.16.0-21 yast2-ldap-2.15.1-118 yast2-ldap-client-2.16.5-13 yast2-ldap-server-2.15.5-114 yast2-mail-2.15.24-9 yast2-mail-plugins-2.15.24-9 yast2-mcs-plugin-0.1.0-72 yast2-metapackage-handler-0.7.3-23 yast2-mouse-2.16.0-23 yast2-multipath-2.13.0-123 yast2-ncurses-2.16.10-2 yast2-network-2.16.21-3 yast2-network-devel-doc-2.16.21-3 yast2-nfs-client-2.15.0-62 yast2-nfs-server-2.15.5-8 yast2-nis-client-2.16.0-33 yast2-nis-server-2.16.0-41 yast2-nis-server-devel-doc-2.16.0-41 yast2-ntp-client-2.16.2-19 yast2-online-update-2.16.6-14 yast2-online-update-frontend-2.16.6-14 yast2-packager-2.16.15-3 yast2-pam-2.16.0-34 yast2-perl-bindings-2.16.0-39 yast2-pkg-bindings-2.16.11-3 yast2-pkg-bindings-devel-doc-2.16.11-3 yast2-printer-2.16.6-17 yast2-printer-devel-doc-2.16.6-17 yast2-product-creator-2.16.6-15 yast2-profile-manager-2.16.0-24 yast2-python-bindings-2.16.3-2 yast2-qt-2.16.17-6 yast2-registration-2.16.0-25 yast2-repair-2.16.3-6 yast2-restore-2.16.0-25 yast2-ruby-bindings-0.2.0-38 yast2-runlevel-2.16.0-25 yast2-samba-client-2.16.1-23 yast2-samba-server-2.16.0-37 yast2-scanner-2.15.5-80 yast2-schema-2.15.0-158 yast2-security-2.15.1-62 yast2-slide-show-SuSELinux-2.15.16-2 yast2-slp-2.15.0-69 yast2-slp-server-2.15.0-80 yast2-sound-2.16.2-6 yast2-squid-2.16.1-3 yast2-sshd-2.16.0-19 yast2-storage-2.16.8-6 yast2-storage-devel-2.16.8-6 yast2-storage-evms-2.16.8-6 yast2-storage-lib-2.16.8-6 yast2-sudo-2.15.3-128 yast2-support-2.15.3-52 yast2-sysconfig-2.15.3-95 yast2-tftp-server-2.14.0-142 yast2-theme-openSUSE-2.16.4-7 yast2-trans-de-2.16.1-5 yast2-trans-en_US-2.15.5-24 yast2-transfer-2.16.1-7 yast2-trans-ru-2.16.1-5 yast2-trans-stats-2.15.0-51 yast2-tune-2.15.7-62 yast2-tv-2.16.3-6 yast2-update-2.16.4-3 yast2-update-FACTORY-2.16.4-3 yast2-users-2.16.5-13 yast2-x11-2.15.11-68 yast2-xml-2.16.0-17 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=355560
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=355560
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=355560#c1
--- Comment #1 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=355560
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=355560#c2
--- Comment #2 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=355560
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=355560#c3
Stefan Hundhammer
When running yast2 sw_single it goes through a sequence of reading and refreshing the repositories registered.
On some of the most lengthy operations there is now an animated blue splash instead of a progress bar.
That's not a bug, that's a feature. This is the new "busy animation" for processes that take an unknown amount of time.
As the cursor already shows the busy status
Bug reports show that for many users this is not explicit enough. Also, a busy cursor will always remain there until the application is finished and changes it back to the normal cursor. This new busy animation, however, shows busy state as long as it receives a periodic "keep alive" signal from the lengthy process that is being performed. If it does not receive that signal for a while, it will stop the animation so the user can see that something is obviously wrong. This is different than just a busy cursor.
this should definitely show a progress bar, so the user can estimate the required time.
If we knew how long the operations take, we would do exactly that. But we don't know that, so we can't do that. Thomas, any more comments from you? IMHO this is INVALID. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=355560
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=355560#c4
--- Comment #4 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=355560
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=355560#c5
--- Comment #5 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=355560
User tgoettlicher@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=355560#c6
Thomas Göttlicher
On a second thought:
You may not know how long it takes, but there might be an indication of how many percent of the task is done. I.e. number records read ( written, deleted ) of so many in total that could be passed on to the user as progress bar.
Sometimes whether time nor steps are known. Only in this case the busy indicator is used. In all other cases a progress bar is shown. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=355560
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=355560#c7
--- Comment #7 from Stefan Hundhammer
You may not know how long it takes, but there might be an indication of how many percent of the task is done. I.e. number records read ( written, deleted ) of so many in total that could be passed on to the user as progress bar.
Well, sure. We do that everywhere where we know how many items we will get in total. But this is just what we don't know in those cases where we use that new busy animation. For example, while reading an XML file you'll never know how many items and subitems it has until you are finished reading it. You also get no information as to the current file position such an XML reader is, so we also can't use the total file size and the offset of the record that is currently being read. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com