Bug 82258 - Wrong sysfont when shutting down
Summary: Wrong sysfont when shutting down
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks: 79579 CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2003-01-20 16:42 UTC by Mattias Dahlberg
Modified: 2014-03-17 02:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-29 20:35:40 UTC


Attachments (Terms of Use)

Description Mattias Dahlberg 2003-01-20 16:42:33 UTC
Description of problem:

When shutting down the correct sysfont doesn't get set until portmapper is run. 
It would be nice if the sysfont could get set at the beginning of the shutdown.

This is very similar to bug 75535 (thanks for fixing) but concerns shutdown 
instead of bootup.


How reproducible:
Always

Steps to Reproduce:
1. Use another language than English
2. Shutdown
3. Check out the strange UTF8 characters

Comment 1 Bill Nottingham 2003-01-20 20:37:40 UTC
This shouldn't make any difference; it should have already been set correctly on
boot. How are you shutting down?

Comment 2 Mattias Dahlberg 2003-01-21 09:40:00 UTC
Try restarting the computer from gdm.

In fact, I just discovered that the sysfont is wrong only when you _restart_ 
the computer, not when you shut down, although the strings are the same.


Comment 3 Mattias Dahlberg 2003-01-24 10:00:46 UTC
I have to add that this doesn't happen everytime. I'm desperately trying to 
find a pattern to when it happens, but no success so far.

Most of the times the sysfont is correct, which makes it harder to debug, but 
also makes the bug less serious. :)

Comment 4 Bill Nottingham 2005-09-29 20:35:40 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

I suspect this has to do with GDM running on a terminal that hasn't been
properly initialized.

This should be fixed post-FC4.


Note You need to log in before you can comment on or make changes to this bug.