Bug 24273 - isodumper shows no progress bar and report window does not show writing unto complete in GTK mode
Summary: isodumper shows no progress bar and report window does not show writing unto ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords: 7beta2
Depends on:
Blocks:
 
Reported: 2019-02-01 03:07 CET by Ben McMonagle
Modified: 2019-02-22 15:55 CET (History)
2 users (show)

See Also:
Source RPM: isodumper 1.05-3.mga7, isodumper-gtk 1.05-3.mga7
CVE:
Status comment:


Attachments

Description Ben McMonagle 2019-02-01 03:07:12 CET
Description of problem: isodumper progress bar does not indicate any progress until complete, likewise the report window indicates no progress until complete


Version-Release number of selected component (if applicable):


How reproducible:everytime


Steps to Reproduce:
1.install isodumper and isodumper-gtk into current Mga7 install
2.write a .iso to usb
3.
Ben McMonagle 2019-02-01 03:07:28 CET

Keywords: (none) => 7beta2

Comment 1 Ben McMonagle 2019-02-01 03:10:52 CET
edit.

if the .iso is very small, ie netinstall
Marja Van Waes 2019-02-03 08:55:12 CET

Assignee: bugsquad => mageiatools
CC: (none) => marja11, yves.brungard_mageia

Comment 2 papoteur 2019-02-05 16:16:25 CET
OK,
Next release  (should be 1.95) will include a different timing to refresh the progress bar. It was 1s, will be 0.2s.
papoteur 2019-02-06 08:36:48 CET

Summary: isodumper shows no progress bar and report window does not show writing unto complete => isodumper shows no progress bar and report window does not show writing unto complete in GTK mode

Comment 3 papoteur 2019-02-06 09:24:26 CET
Correction done in 1.07.
Problem was refreshing in GTK mode. Was OK in default mode (Qt).
Comment 4 papoteur 2019-02-22 15:55:21 CET
Isodumper 1.07 is now released.
Thus closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.