Description of problem: when using urpmi, if "konsole" window is too small, urpmi reports the % downloaded increasing in single incrementing lines. If the window is made larger, urpmi reports the % downloaded as a single line, with the % just increasing plasma desktop Version-Release number of selected component (if applicable): How reproducible: every time Steps to Reproduce: 1.invoke konsole, stretch to full width of screen, and initiate urpmi [--auto-update maybe] 2.note how the downloaded % of a packages is reported 3.change the width of the konsole window to about 1/3 width of screen. 4. note the change in the way downloaded % reported
Keywords: (none) => 6RC
Created attachment 8326 [details] how urpmi should report downloaded packages
Created attachment 8327 [details] example of how urpmi reports downloaded % of package if konsole window is too small
(In reply to ben mcmonagle from comment #2) > Created attachment 8327 [details] > example of how urpmi reports downloaded % of package if konsole window is > too small You don't get that when you start urpmi in a small konsole window, but only when you make it smaller after starting urpmi, correct? If the latter, then to me that doesn't count as a bug.... or was this different in Mga 1-5 ?
Keywords: (none) => NEEDINFOPriority: Normal => LowCC: (none) => mageia, marja11, thierry.vignaudSeverity: normal => minor
(In reply to Marja van Waes from comment #3) > only > when you make it smaller after starting urpmi, correct? yes > was this > different in Mga 1-5 ? same in M5
Thx for the feedback, Ben. Changing Severity to Enhancement
Keywords: NEEDINFO => (none)Severity: minor => enhancement
Guessing that *if* this can be enhanced at all, that it should happen on konsole side, so assigning to neoclust, who'll happily reassign if needed, or tell it can't be done if that's the case.
Assignee: bugsquad => mageiaSource RPM: (none) => konsole, urpmi
Assignee: mageia => kde
is it still valid on current cauldron ?
(In reply to Nicolas Lécureuil from comment #7) > is it still valid on current cauldron ? Over half a year later, no reply. Assuming this got fixed.
Status: NEW => RESOLVEDResolution: (none) => FIXED