Restricted Driver manager changes keyboard layout and screen resolution

Some value are better like video card name and monitor name but some are wrong like the resolution, the remove of nologo (contract with nvidia ?)

Option NoLogo has actually been made a default on a recent update - see Bug #93306 for details. No contract it seems :)

This bug is probably related to bug #94365

Here are my xorg.conf before and after use of restricted manager with nvidia card

This tool is simply unusable for a desktop user. After the keyboard is wrong and resolution is bad.

These sections in xorg.conf simply should not be changed

Oh, my mistakes!
Contrary of what I said in
https://launchpad.net/ubuntu/+source/restricted-manager/+bug/94549/comments/1
values about name of video card and monitor were good BEFORE usage of restricted manager, so like you I go from "real names" to "generic names" :/

Same problem here, before using the tool I had a screen resolution of 1280x800 and a British keyboard layout. After I had 1024x768 and Us layout. I wasn't able to change the screen resolution from the Preferrences, I had to edit the xorg.conf manually.

I cannot reproduce this. r-m preserves the setting for me.

Can you please do the following to help me debug this:

1. disable the restricted driver with r-m
2. sudo rm /var/log/restricted-manager.log
3. sudo dpkg-reconfigure xserver-xorg
    Here you need to restore your proper settings wrt. keyboard layout, resolution, etc.
4. Enable restricted driver with r-m
5. Now keyboard layout/resolutions should be wrong again in xorg.conf. Please attach /var/log/restricted-manager.log and your xorg.conf.
6. Use 'sudo dpkg-reconfigure xserver-xorg' to repair keyboard/resolutions once more after breaking it with r-m.

Thank you!

I tried following your steps, but with those I was also unable to reproduce the problem. However, during step 1 (using r-m to disable the the driver), r-m told me it would not alter my xorg.conf since I had manually modified it. I used the command it gave to reset the file (dpkg-reconfigure -phigh xserver-xorg), and that changed the keyboard layout to us. (It prompts for video driver and resolution, and accepts those, but perhaps something similar is being called from within r-m?)

I continued with the steps, setting the xorg.conf up properly then using r-m to enable the driver, but the problem did not occur this time. I have tried doing everything several more times, but both r-m and dpkg-reconfigure seem to behave themselves now, and I am now unable to reproduce the problem at all.

I have easily reproduced this issue on my Thinkpad T41p. It has a resolution of 1400x1050 which is fine after the install (correct resolution). But after enabling the fglrx driver with the "Restricted Device Manger" app. The higest res I can get is 1024x768. A quick look at the xorg.conf shows that it is replacing the xorg.conf that was fine and had the correct resolutions for my screen. Which some default one, that while has fglrx set as the driver, does not have all the proper resolutions from my screen.

Jerone, please attach /var/log/restricted-manager.log, and then do the steps in https://beta.launchpad.net/ubuntu/+source/restricted-manager/+bug/94549/comments/9 to verify that you cannot reproduce it any more after that. Thank you!

Martin your link is for the beta version of launchpad ;)

I confirm that restricted-manager change my keyboard layout too when installing fglrx on my notebook, or when installing nvidia on my PC.

@Martin:

I've got a NVIDIA Geforce 7900GS and experienced the same problems (resolution, refresh rate and keyboard layout changed) after activating the restricted driver so i did the steps in comment #9 (and rebooted after steps 1, 3 and 4).

After step 4 (+ reboot), the resolution and keyboard layout were still the same as after step 3 (so r-m hadn't messed up xorg.conf this time), but the refresh rate had changed.

After installing Feisty: 60/75 Hz (which are the two modes supported by my screen)
after using r-m the first time: 50/54 Hz + keyboard layout and resolution messed up
after doing step 3: 60 Hz only
after doing step 4: 50/54 Hz again (which is not the correct setting for my screen), but keyboard layout and resolution still O.K.

Fixed in -xorgconf branch.

 restricted-manager (0.15) feisty; urgency=low
 .
   * debian/control: Use XS-Python-Version 'all' instead of 'current', since
     the latter seems to break quite often on upgrades. (see #93795)
   * applications/restricted-manager.desktop.in: Do not show for non-admins.
     (LP: #97163)
   * Add RestrictedManager/xorgconfig.py (stolen from kdeguidance):
     Parser/writer for X.org configuration files. Add author and copyright to
     debian/copyright.
   * RestrictedManager/xorgconfig.py: Change formatting a bit to make it more
     similar to what dexconf produces.
   * RestrictedManager/xorg_driver.py:
     - Use xorgconfig.py to mangle /etc/X11/xorg.conf directly instead of
       relying on consistent debconf values and using dexconf. This makes r-m
       work with custom configurations (including install scripts from
       nvidia/fglrx upstream packages) and avoids changing unrelated settings
       like keyboard/screen resolution/BusID etc. (LP: #92836, LP: #94549,
       LP: #93075)
     - Back up the entire original config before enabling a driver. If it
       exists when disabling again, restore it entirely. (LP: #96474)
     - is_enabled(): Do not check for installed GLX library package any more
       (such as nvidia-glx), since they could be installed directly from
       upstream. Now only check the xorg.conf configuration. (LP: #94626)
     - Add {enable,disable}_config_hook() for nonstandard modifications to the
       X.org configuration.
   * RestrictedManager/fglrx.py: Use above *_config_hook() to add/remove the
     'Extensions' section and disable Composite. In previous versions, dexconf
     did that for us.
   * restricted-manager: Drop check for readability of debconf database, since
     we do not need it any more.
   * Some small UI improvements, thanks to izi!
     - Remove the redundant 'Enable' button, we already have the check boxes.
     - Display stock yes/no/reload icons in addition to the textual status.
     - Add window icon.
     - Do not update the tree model when cancelling enabling/disabling.
     - Make modal dialogs transient.
   * RestrictedManager/core.py: Add a global variable
     package_install_idle_function which, if set to a function, is executed
     repeatedly while waiting for synaptic to finish. This avoids GTK specific
     code in the backend.
   * restricted-manager: Set core.package_install_idle_function to a default
     GTK event processing loop. (LP: #97399)
   * restricted-manager: Determine main window xid and pass it to synaptic as
     parent window, so that it becomes transient.

Just wanted to confirm that with the latest restricted manager, I do not have this bug anymore :-)
Thank you for the quick solution!