I just tested it, and it worked here, after I mounted the filesystems containing
a windows installation.  The get windows function does not download anything,
it only looks in mounted filesystems for fonts installed in a windows
installation.  I think this bug should be closed as fixed-invalid, as it's
working as intended.

CC: (none) => davidwhodgins

You're right, I mounted my Windows partition, and the function worked fine. Thanks for not adding RTFM! Of course, I had confused the intended function with the facility to "install msttcorefonts" available in most other distros. An error message that said "no Windows file system mounted" or something along those lines would probably have been more informative.

Changing the priority/severity, adding rpm, as I think this is now a valid,
but low prioity bug report requesting a change of the error message from 
"no fonts found", to
"no mounted windows file systems found, to import the fonts from",
or something to that affect.

Priority: Normal => Low
Hardware: i586 => All
Source RPM: (none) => drakxtools-13.49-1.mga1.src.rpm
Severity: normal => minor

Great, thanks.

About half a month ago, the bug was still there in cauldron, so this doesn't seem to be a forgotten resolved bug

CC: (none) => marja11
Source RPM: drakxtools-13.49-1.mga1.src.rpm => drakxtools-13.63-1.mga2.src.rpm

Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.

@ Olivier
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

3 months later, any news on this bug?

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

Still valid. It won't get fixed for Mga2, so only putting (MGA2) on the whiteboard to show this isn't an old cauldron bug that was last seen a year ago

Whiteboard: (none) => (MGA2)

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Sorry, but this bug saw no action since more than 2 yrs ago. 
No cauldron package has stayed the same since then.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

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

This one is still valid, according to me.

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