broken console localization with usplash enabled

Bug #26213 reported by Drolyk
30
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I`m trying to setup russian console in kubuntu breezy with usplash enabled, but I`ve got no success
with it. My steps in detail:

1)edit /etc/console-tools/config, add following string:
SCREEN_FONT=Cyr_a8x16
APP_CHARSET_MAP=koi8-r
APP_CHARSET_MAP_vc2=user
APP_CHARSET_MAP_vc3=user
APP_CHARSET_MAP_vc4=user
APP_CHARSET_MAP_vc5=user
APP_CHARSET_MAP_vc6=user
APP_CHARSET_MAP_vc12=user
2) run dpkg-reconfigure locales, and select ru_RU.KOI8-R as default locale
3) run dpkg-reconfigure console-data and select "pc / qwerty / Russian / Standard / KOI8-R (105
Keys)" from the list

Then if I boot kernel without "splash" bootparam I`ve got localized console (all russian chars are
correct on display and I able to type them), but if I pass "splash" option to kernel all russain
chars look like crappy stuff :)

Revision history for this message
Adam Conrad (adconrad) wrote :

I have a feeling we only got around to fixing this in ubuntu, but not kubuntu.
Since they use different display managers (gdm versus kdm), and the fix had to
be done for each, we probably missed kdm. Can you try putting the following in
/etc/init.d/kdm right before the bit where kdm starts?

# if usplash is runing, make sure to stop it now
if pidof usplash > /dev/null; then
    /etc/init.d/usplash stop
fi

And let me know if that magically makes things better?

Revision history for this message
Drolyk (drolyk) wrote :

(In reply to comment #1)
> I have a feeling we only got around to fixing this in ubuntu, but not kubuntu.
> Since they use different display managers (gdm versus kdm), and the fix had to
> be done for each, we probably missed kdm. Can you try putting the following in
> /etc/init.d/kdm right before the bit where kdm starts?
>
> # if usplash is runing, make sure to stop it now
> if pidof usplash > /dev/null; then
> /etc/init.d/usplash stop
> fi
>
> And let me know if that magically makes things better?
>

Hmm... I don`t think that kdm is a problem.
I`ve got a bunch of problems with usplash and broken localization is one of them.
On my system usplash disappears before kdm starts on FS mounting
Here is my fstab
/dev/hda1 /boot ext2 defaults 0 0
/dev/hda2 none swap sw 0 0
/dev/hda5 / reiserfs defaults 0 1
/dev/hda6 /var reiserfs defaults 0 0
/dev/hda7 /home reiserfs defaults 0 0
/dev/hda8 /mnt/share1 reiserfs defaults 0 0
/dev/hdb1 /mnt/share2 reiserfs defaults 0 0
/dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
proc /proc proc defaults 0 0

However, when I change kdm init script as you advise

[snip]
case "$1" in
  start)
    if pidof usplash > /dev/null; then
        /etc/init.d/usplash stop
    fi
    if [ -e $DEFAULT_DISPLAY_MANAGER_FILE ] &&
       [ "$HEED_DEFAULT_DISPLAY_MANAGER" = "true" ] &&
       [ "$(cat $DEFAULT_DISPLAY_MANAGER_FILE)" != "$DAEMON" ]; then
      echo "Not starting K Display Manager (kdm); it is not the default display manager."
 [snip]

I don`t have any effect

Revision history for this message
Carthik Sharma (carthik) wrote :

Confirmed as there appears to be a duplicate. Please let us know if this problem has been fixed in Dapper Beta for you, in the off chance that it has been addressed.

Thank you for reporting this issue.

Changed in usplash:
status: Unconfirmed → Confirmed
Revision history for this message
Matthew Garrett (mjg59) wrote :

This has been fixed for a while.

Changed in usplash:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.