|
Bugzilla – Full Text Bug Listing |
| Summary: | X fonts too large using SaX2 settings in VMWare environment | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Kirk Coombs <kcoombs> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_1GBkbCnI0A |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
xorg generated by SaX2
xorg generated by vmware-config-tools.pl YaST logs Example KDM login screen |
||
|
Description
Kirk Coombs
2006-10-31 14:44:15 UTC
Created attachment 103171 [details]
xorg generated by SaX2
Created attachment 103172 [details]
xorg generated by vmware-config-tools.pl
Created attachment 103173 [details]
YaST logs
DisplaySize 16 16 is the problem here. It would be great if you can test the current sax2 version which should fix the problem. You can find the packages here: http://ftp.opensuse.org/pub/opensuse/repositories/SaX2/SL10.2/i586/ Thanks Created attachment 103174 [details]
Example KDM login screen
DisplaySize 16 16 is the problem here. It would be great if you can test the current sax2 version which should fix the problem. You can find the packages here: http://ftp.opensuse.org/pub/opensuse/repositories/SaX2/SL10.2/i586/ Thanks New SaX2 rpms fixed the problem. This bug is resolved as far as I am concerned. great thanks for testing *** Bug 216090 has been marked as a duplicate of this bug. *** With Beta 2 I have a similar bahaviour as with beta 1. I still see "DisplaySize 16 16" or "32 16" either initially after installation or after running sax2 afterwards. I tried sax2 from the above mentioned repository, too, but without success. Which information do you need? next version should fix it. See bug #219801 *** This bug has been marked as a duplicate of bug 219801 *** |