Character encoding issues on TTYs when Nvidia driver is installed

Bug #1083093 reported by Jan Rathmann
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hello,

if the propritary Nvidia driver is installed, the TTYs show some character encoding issues by default.

Steps to reproduce:
- Install Raring.
- Install nvidia-current.
- Restart and access a TTY via e.g. CTRL + ALT + F1
- If I try to enter one of the german umlauts (ä, ö ,ü or ß), non-character signs are displayed instead. This also happens if I execute any program that shows text with those umlauts (e.g. executing sudo dpkg-reconfigure console-setup with a german locale).

Workaround for Raring:
- Using the Nouveau driver.
- Running "sudo dpkg-reconfigure console-setup". I left the default settings unchanged exept setting a smaller font size. Afterwards umlauts are displayed correctly and this is retained after a reboot.

In Quantal the situation is worse: If I try to correct anything with dpkg-reconfigure console-setup, these changes are lost after a reboot. It seems as if they TTYs are completely ignoring the configured console settings and falling back to some basic default values for font, font size etc. where any more sophisticated characters like umlauts are unsupported.

Kind regards,
Jan

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: console-setup 1.70ubuntu6
ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6
Uname: Linux 3.7.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.2-0ubuntu5
Architecture: amd64
Date: Mon Nov 26 10:23:29 2012
InstallationDate: Installed on 2012-11-26 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1083093

tags: added: iso-testing
Revision history for this message
Michael Cordes (elected) wrote :

same problem here.
For me the following works:

sudo apt-get install v86d

then add the module "uvesafb" to /etc/modules.
Then I have framebuffer support and the correct charset.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in console-setup (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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