http://qa.mandrakesoft.com/show_bug.cgi?id=1356
------- Additional Comments From [EMAIL PROTECTED] 2003-03-07 03:05 ------- This still happens in tonight's cooker. I left the install running and it has finished by the time I checked an hour later, but this really sucks. (1) NOBODY is going to believe that this is working as it should (2) You have some sort of exponential performance problem here having to do with the number of fonts. If you aren't going to fix it, then you need to provide some sort of progress indicator that shows that useful work is being done, however slowly. I suppose that this isn't a must-fix (provided you do something to convince the user that the machine hasn't just locked up) because it only needs to be done once, but I can't help thinking that it would be easier to fix the performance problem than to do all of the GUI work needed to show that the install isn't hung. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I have collected all of my Windows fonts onto a CD (about 300 fonts, 80-90 MB) and use the CD to install these fonts on my Mandrake systems. When the install starts, the "Initial Tests" progress bar hangs about 1/3 of the way through for about 20-30 minutes with CPU pinned at 100% on a 2.4GHz P4. I waited it out, and it eventually finished successfully, but any consumer-grade user is going to think that it's either hung or gone into a loop. Whatever's being done with these fonts, I think you need a popup display in front of the drakfont four-bar progress display which displays the fontname being processed and a progress bar specific to that font and whatever is being done to it in that particular phase (Initial Tests, etc.). At least that will display some activity to indicate to the user that *something* productive is going on. I understand that you are calling another package under the covers, so if you can't do a progress bar, then at least an activity indicator combined with a popup saying that this may take a VERY long time would be appropriate. Since the activity is so CPU-bound, it should be possible to come up with a prediction based on the number of fonts, and at least display the amount of time (based on bogoflops or whatever) that you expect it to take.
