Bug 252529 - Progressbar flickering during online update due to bad maths? ([ui] YProgressBar.cc(changeWidget):88 Too big value 9194 for progress bar ( max is 100 ))
Summary: Progressbar flickering during online update due to bad maths? ([ui] YProgress...
Status: RESOLVED DUPLICATE of bug 60867
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Stefan Hundhammer
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-08 10:51 UTC by Ulrich Windl
Modified: 2007-03-08 22:26 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
y2log for today's online update (1.20 MB, text/plain)
2007-03-08 10:54 UTC, Ulrich Windl 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2007-03-08 10:51:52 UTC 
Despite of noticing that the progress bar during online update in ncurses Yast is quite "jumpy", the y2log is filled with messages like the following. I guess there's a programming error somewhere:
[ui] YProgressBar.cc(changeWidget):82 Negative value -2147483648 for progress bar
[ui] YProgressBar.cc(changeWidget):88 Too big value 3043407 for progress bar ( max is 100 )
[ui] YProgressBar.cc(changeWidget):88 Too big value 4588 for progress bar ( max is 100 )
[ui] YProgressBar.cc(changeWidget):88 Too big value 9194 for progress bar ( max is 100 )
[ui] YProgressBar.cc(changeWidget):88 Too big value 13301 for progress bar ( max is 100 )
[...]
Comment 1 Ulrich Windl 2007-03-08 10:54:19 UTC 
Created attachment 123139 [details]
y2log for today's online update

You might want to process the file with something like "grep -i progressbar /tmp/junk | cut -d' ' -f5- | sort -u"
Comment 2 Stefan Hundhammer 2007-03-08 22:26:46 UTC 

*** This bug has been marked as a duplicate of bug 60867 ***