Bugzilla – Bug 371343
sax2 creates no xorg.conf
Last modified: 2008-03-15 14:11:42 UTC
Having to recover from experiments with the xorg.conf driver, I want to start from scratch. xorg.conf{,.md5} are deleted. sax2 -r starts up, I click on "change settings" (there is always something wrong). The keyboard is set to a Microsoft natural something pro for Afghanistan. I change that to generic 104 key USA layout to match what is actually connected. I change the monitor mode from 1024x768@60 to @75. Clicking ok, then "save" causes sax2 to exit but does not create a new xorg.conf, there is still no such file now. Clicking ok, then "test" (the modelines are always slightly wrong for me) just causes sax2 to exit without doing anything else. All effort to create a xorg.xonf is wasted so far. Hardware is a PII-450 with i740 graphics card and 17" *very* old monitor. Hardware works under oS 10.3.
Created attachment 202243 [details] SaX.log On sax2 startup, there are 7 attempts to read this file: ISaX: could not import file: /var/cache/sax/files/config The file exists. It has text strings and a lot of 0x00 and some binary characters in between. The file is recreated when deleting it before running sax2.
Running sax2 without options, making above changes, and clicking ok, then save still doesn't create an xorg.conf. Running sax2, then clicking ok instead of make changes, does create an xorg.conf, and sax2 asks whether to exit after clicking save. Running sax2 to get my changes done, making them, and clicking save causes sax2 to exit quickly without asking whether to exit and without writing to xorg.conf. Looks like it's crashing on some of the changes?
Changing the keyboard to generic-104key USA layout is something sax2 kills itself over. Making no change creates Option "XkbLayout" "us" Option "XkbModel" "microsoftpro" The kayboard handling is somehow faulty (glad the Afghanistan setting has no effect...). This is a current (a few days ago) factory system, I upgraded sax2 to sax2-8.1-376 Btw on initial installation of alpha2 CD the mouse was not setup properly, neither middle button nor scroll wheel are working.
*** This bug has been marked as a duplicate of bug 370948 ***