please attach a screenshot

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

that is impossible, it's during installation, there is not system yet.

thierry can tell better but iirc using F1 during install does a screenshot.

really? and where is the screenshot located then? how can it store if there's no system yet? i don't understand? also, this could have been mentioned before testing, this would make some stuff easier, probably. i've been using since Mandrake 6.2 ... and i've never known this?

and also, i'd have to reinstall to do so... which i can't really do right now, because i still need this system for debugging the other bugs?

perhaps someone else can confirm? and possibly take screenshot?

I'll be trying a fresh install in a day or so, and I'll see if I can do it.  I can confirm what you reported, although I didn't find it objectionable at the time.

CC: (none) => ftg

Use F4 key then have a look in /root after reboot to find screenshots

CC: (none) => ennael1

thanks, and well objectionable is a big word, but it was noticably a lot smaller than the rest. i can imagine older people would have a hard time reading it.

(In reply to comment #6)
> Use F4 key then have a look in /root after reboot to find screenshots

Well, I F4'd my little heart out during the Update phase, but there wasn't any screenshot file in /root afterwards.  The only thing even close was drakx/replay_install.img, which is not what I think you mean.

Sorry it may be F2... I cannot remember :p

It's F2 and screenshots will go in /root/DrakX-screenshots after installation.
They got copied here once the "/" of the installed system is mounted in the /mnt of the installer.
You'll got a dialog about this on first screenshot

BTW, in case one cannot install a system at all (which is not the case here), it's seven possible to push them in the cloud. See http://wiki.mandriva.com/en/Development/Howto/MDK_Installer

Created attachment 84 [details]
Screenshot of small font in Updates phase

The F2 key does not appear to be "seen" by Mageia running in VirtualBox in spite of the keyboard being captured, so I took a screenshot of the window from the host system

OK, this is what I though, this is when we run gurpmi2 in the chrooted system

Assignee: bugsquad => thierry.vignaud
Summary: at the end of installation, in updating step, fonts are tiny => chrooted gurpmi uses tiny fonts in updates step

confirmed on upgrading mdv via DVD to mga 1 alpha 2, i'm adding dependency to tracker.

Blocks: (none) => 56

btw: isn't the info supplied now? shouldn't needinfo be removed now?

@ahmad, why are you removing even this one from #56? this happens DURING upgrade in the last step before reboot (the update step), and i still think NEEDINFO should be removed...

(In reply to comment #16)
> @ahmad, why are you removing even this one from #56? this happens DURING
> upgrade in the last step before reboot (the update step), and i still think
> NEEDINFO should be removed...

If it happens in a clean install then it's not an upgrade issue that should be tracked by bug 56.

This bug was for mga 1 alpha 2.

No one reported this bug for mga 1 rc, so I'm closing this bug.

Status: NEW => RESOLVED
CC: (none) => m.van.waes
Resolution: (none) => OLD

bug is still there, iirc

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

@ Thierry

I'm putting OK on the whiteboard  because you assigned this one to yourself. Remove it if you want to be pinged by me here again ;)

Whiteboard: (none) => OK

Things is that we enforce a certain font size for the installer in lang.pm (see %charset2pango_font) and load_font() in install/install2.pm

A way to workaround this could be to dump the bit of gtkrc we generate into a temp file and force run program to use it through the GTK2_RC_FILES environment variable.
Of course this won't work anymore once we switch to gtk+-3...

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

cauldron only

Keywords: NEEDINFO => (none)

Also valid for release notes viewer on very first step.
Which I workarounded long time ago for the HTML content but not for the buttons

The issue is that we set a font size for the installer (charset2pango_font in lang.pm), "DejaVu Sans 12" for most languages.
But this is set for the installer process only, by parsing a gtk style.
Fixed in SVN

Keywords: (none) => USABILITY
Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Summary: chrooted gurpmi uses tiny fonts in updates step => tiny fonts are used for external programs (release notes viewer, chrooted gurpmi in updates step)