Jump to content

Bugfix Advisory (MDKA-2003:004): 9.1


aru
 Share

Recommended Posts

MandrakeSoft Bugfix Advisory MDKA-2003:004 : 9.1

 

April 10th, 2003

Updated packages fix various bugs in Mandrake Linux 9.1

 

The following updates provide certain fixes to Mandrake Linux 9.1:

 

It was discovered that the Mandrake Galaxy theme would cause crashes in certain programs such as Downloader4X. It would also cause a crash in languages such as Arabic and Hebrew. This update provides a fix.

 

Two bugs were discovered in the Mandrake Control Center: The first kills "explicitly non-embeddable" processes when killing embedded tools, and the second prevented menudrake from being executed by users other than root and the owner of the X server.

 

All non-latin locales in rfbdrake are completely broken due to bad utf8 handling.

 

A number of printer-related fixes have been made:

 

- Ghostscript now supports PNG again; the Ghostscript shipped with 9.1 was missing PNG support.

 

- Many HP LaserJet printers had two "Duplex" options when used with the "ljet4d" or "Postscript" drivers.

 

- The "PrintoutMode" option of the "pxlmono" driver (PCL 6, most newer non-PostScript laser printers) did not set the resolution.

 

- Problems printing on the HP LaserJet 1000 should be solved now.

 

- The Lexmark Z31 printed only bi-directionally giving very poor quality, now it prints uni-directionally by default (much better quality), and bi-directional printing is an option.

 

- ICC profile support (color correction) for the Minolta MagiColor 2200/2300 DL printers.

 

- All Foomatic printer IDs are clear-text now; no more cryptic numbers when using "foomatic-configure" to set up printers on the command line. Users can now setup printers without looking up the ID number first.

 

- Changes were made so that upgrading from 9.0 and older would not require a regeneration of the Foomatic print queues.

 

A number of fixes were also made to the drakxtools programs, specifically:

 

- In drakfloppy, when attempting to create a boot disk, the configuration works fine but will fail and crash when actually generating the boot floppy.

 

- Some strings were not translated in harddrake.

 

- The harddrake service timeout was only 5 seconds which was too short so it has been changed to a 25s timeout.

 

- In draktermserv, initrd was mistakenly named initrdrd.

 

- Due to unuseable fonts for Arabic, Arabic support has been disabled in the tools.

 

- Fixes were made to xfdrake to work better with some Intel video cards.

 

- A number of bugs were corrected in drakconnect.

 

- Drakboot would crash if any errors occured during lilo or grub regeneration of the mbr; now drakboot will display the error instead of crashing.

 

MandrakeClub users use a special downloading mechanism involving HTTP redirection with authentication. There is a problem in the downloading backend using in 9.1 (the curl program) which prevents the redirection from happening correctly. Under urpmi, users experiencing this problem see the error message "unable to register rpm file. Everything already installed" when trying to install a package (a workaround is to force the use of wget, or use the redirection (the URL beginning with https://) directly). Under rpmdrake, the error message is "The signature of the package is not correct; Could not read lead bytes". There is no workaround in rpmdrake.

 

As well, a UTF8 issue was fixed in grpmi.

 

The provided packages correct all of these problems.

 

 

The released versions of Mandrake GNU/Linux affected are:

  • 9.1

 

[*] 9.1/PPC

Full information about this advisory, including the updated packages, is available at:

www.mandrakesecure.net/en/advisories/advisory.php?name=MDKA-2003:004

 

Posted automatically by aru (mdksec2mub v0.0.5)

Link to comment
Share on other sites

 Share

×
×
  • Create New...