changes manually set resolution
Bug #93643 reported by
Martin Pitt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
restricted-manager (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
Binary package hint: restricted-manager
I manually configured xserver-xorg to use non-detected resolutions. After installing nvidia with r-m it reverts back to autodetected resolutions.
Related branches
Changed in restricted-manager: | |
assignee: | nobody → pitti |
importance: | Undecided → High |
status: | Unconfirmed → In Progress |
Changed in restricted-manager: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
restricted-manager (0.11) feisty; urgency=low er/xorg_ driver. py: Do not autodetect mouse and monitor when er/nvidia. py: Enable NoLogo by default. (LP: #93306) er/nvidia. py: Enable AddARGBVisuals to make Beryl work. er/xorg_ driver. py: Do not mangle xorg.conf if package installation was aborted. (LP: #92573) er/nvidia. py: Fix passing of driver package name, so that er/{xorg_ driver, nvidia, fglrx}. py: Do not assume that the er/modalias. override: Add NV44A [GeForce 6200] (not covered er/core. py: When loading default or special handlers, check
.
* RestrictedManag
reconfiguring xserver-xorg for a new driver. This avoids clobbering
manually added undetected resolutions. (LP: #93643)
* po/de.po: Synchronize with Rosetta.
* RestrictedManag
* RestrictedManag
(LP: #93262)
* RestrictedManag
download/
* RestrictedManag
the legacy driver actually installs nvidia-glx-legacy. (LP: #92849, part
one)
* RestrictedManag
kernel module name always matches the X.org driver module name
(nvidia_legacy vs. nvidia), but instead pass the X.org driver name as a
separate attribute. ((LP: #92849, part two)
* RestrictedManag
by nvidia_supported). (LP: #93209)
* RestrictedManag
that there is actually a kernel module behind. Otherwise we will display
handlers with overrides on platforms which do not actually provide those
modules. (LP: #93368)