Bug 134460 - More than one gnome-session makes for small fonts
Summary: More than one gnome-session makes for small fonts
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Rodrigo Moya
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-18 20:05 UTC by Clint Fairchild
Modified: 2007-08-11 15:36 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Clint Fairchild 2005-11-18 20:05:45 UTC 
When gnome-session is running, if the same user logs in again and starts another session, the second session will have really small fonts.  To reproduce this bug:
   1. Log in and start a gnome session.
   2. Start another session with vnc or NX.
   3. See the small fonts on the remote sessions.
Comment 1 Stanislav Brabec 2005-11-21 10:43:32 UTC 
This is one of side effects of a seven years known problem - logging in more than one session is not supported. In your case, gnome-settings-deamon was not started for the second time.
Comment 2 JP Rosevear 2006-04-13 20:52:06 UTC 
related to bug 150623
Comment 3 JP Rosevear 2007-02-09 21:10:01 UTC 
Rodrigo, is there an upstream bug that covers this?
Comment 4 Rodrigo Moya 2007-02-12 12:40:02 UTC 
AFAIK, this should be fixed since 2.12 or 2.14. Clint, could you please make sure gnome-settings-daemon was started on both logins? (that is, there should be 2 gnome-settings-daemon processes running). Also, did you see any error message on the 2nd login? If g-s-d cannot be started, it tells the user about it, so if that is the problem you should have seen an error message.
Comment 5 Stanislav Brabec 2007-02-14 12:52:49 UTC 
Reported product is "SUSE LINUX 10.0" and 2.12 was not correct in upstream (it was your fix).

So I guess it's fixed now.
Comment 6 Andreas Jaeger 2007-08-11 15:36:04 UTC 
Let's assume it's fixed for 10.2 and newer.