32-bit rar archiver with libc6-i386 cannot convert filenames to utf8
rar archiver is distributed as 32-bit binary. Under debian-amd64 it is possible to run it with libc6-i386 libraries. Unfortunately, there is a problem described below. Usually rar stores filenames in an archive as is (in the current locale encoding) as well as in utf8 encoding. Filenames in utf8 encoding are particularly useful when the archive is supposed to be processed under other OS (e.g., MS Windows) with different locale. If for some reason rar cannot convert filenames into utf8, it creates an archive only with filenames in the current locale encoding. And that exactly what happens with rar using libc6-i386 libraries. Under my debian-amd64 it creates archives only with filenames in koi8-r encoding (as my locale is ru_RU.KOI8-R) that are unreadable under MS Windows. What can possible prevent rar from converting filenames from koi8-r to utf8 (locale ru_RU.UTF-8 is also in my system)? Under (similarly configured) debian-i386 system rar creates filenames in utf8 as expected. Thanks, Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 32-bit rar archiver with libc6-i386 cannot convert filenames to utf8
Max Alekseyev [EMAIL PROTECTED] writes: If for some reason rar cannot convert filenames into utf8, it creates an archive only with filenames in the current locale encoding. And that exactly what happens with rar using libc6-i386 libraries. Under my debian-amd64 it creates archives only with filenames in koi8-r encoding (as my locale is ru_RU.KOI8-R) that are unreadable under MS Windows. What can possible prevent rar from converting filenames from koi8-r to utf8 (locale ru_RU.UTF-8 is also in my system)? Perhaps it's looking for the gconv modules in the wrong place. (You can confirm this via strace.) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems starting X in a new Athlon 3800+ system
Hi. I've been using the latest unstable with a Pentium III for quite a whille now with no problems at all. I decided to upgrade my h/w to an Athlon 3800+ and I thought I could just install the disks from the old system to the new h/w and work from there. The new system, as I said, is an Athlon 3800+ with an ATI Radeon 9200 (from Sapphire). Everything worked just fine until gdm started up. It looks like X will start, but when the screen blanks it just stays that way and I cannot break X or reboot the system with ctrl-alt-del. My old system was running an ATI 128 Rage Pro, but what I did was boot the new system into single user mode and reconfigured 'xserver-xorg' accepting sensible options. The configuration recognized the card and the monitor, etc. But X just doesn't work. At this point, I decided to reinstall using the Debian 4.0 netinst cd thinking that the reinstallation would default to a useful value, but the re-installation has the same problem with X. Does anyone have any suggestions I might follow to get my system back up? Everything works fine in the text console; it's just X that seems to be having problems. BTW, I've tried running a livecd (centos 4.3) and everything works just fine (gdm starts up, etc.). I'd appreciate any help. Thanks -Jose -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems starting X in a new Athlon 3800+ system
[EMAIL PROTECTED] wrote: Hi. I've been using the latest unstable with a Pentium III for quite a whille now with no problems at all. I decided to upgrade my h/w to an Athlon 3800+ and I thought I could just install the disks from the old system to the new h/w and work from there. The new system, as I said, is an Athlon 3800+ with an ATI Radeon 9200 (from Sapphire). Everything worked just fine until gdm started up. It looks like X will start, but when the screen blanks it just stays that way and I cannot break X or reboot the system with ctrl-alt-del. My old system was running an ATI 128 Rage Pro, but what I did was boot the new system into single user mode and reconfigured 'xserver-xorg' accepting sensible options. The configuration recognized the card and the monitor, etc. But X just doesn't work. At this point, I decided to reinstall using the Debian 4.0 netinst cd thinking that the reinstallation would default to a useful value, but the re-installation has the same problem with X. Does anyone have any suggestions I might follow to get my system back up? Everything works fine in the text console; it's just X that seems to be having problems. BTW, I've tried running a livecd (centos 4.3) and everything works just fine (gdm starts up, etc.). I'd appreciate any help. Thanks -Jose Isn't there a log file -- something like /var/log/Xorg.0.log? Whenever I screw up an X config or something screws it up for me, I usually can get the answer in that log file. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
