gnome-control-center-Keyboard changes screen0 resolution

Bug #617618 reported by keepitsimpleengr
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gnome-control-center

Opening gnome Control Center and selecting Keyboard, I expected the Keyboard Window to open and to be able to change keyboard preferences. Instead, screen0 changed it's resolution from 2560x1600 to 1280x800, rendering the screen useless until the resolution can be restored using /usr/bin/nvidia-settings.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-control-center 1:2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Aug 13 14:29:00 2010
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gnome-control-center

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

The problem is "gnome-settings-daemon" is not running and would not start.

Found work-around:

start gconf-editor, then open / -> apps -> gnome_settings_daemon -> plugins -> xrandr in it and disable flag "active".

edit xorg.conf adding or setting Option "RandR" to "false" in Section "ServerFlags"

Now gnome-settings-daemon runs and no unpleasant resetting of screen resolutions.

~~~~~~~~:~$ ps -A -f | grep gnome-settings-daemon
~~~~~~~~ 2923 2829 0 16:55 pts/0 00:00:00 grep gnome-settings-daemon

http://www.thinkwiki.org/wiki/Xorg_RandR_1.2

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

you can read the bug you marked as duplicate for details

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Sebastian...

Since you (or somebody) marked the duplicate (https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/612098) as invalid, I resubmitted this.

It is obviously not an invalid bug as it it undesirable behavior (to say the least) and the result of an obscure and unrelated functionality.

The "fixing" of bugs by marking them invalid may improve statistics but does improve the users experience.

Revision history for this message
Sebastien Bacher (seb128) wrote :

> The "fixing" of bugs by marking them invalid may improve statistics but does improve the users experience.

The statistics don't really matter, having a buglist usuable does rather, that's not a bug, that software is meant to be used under GNOME to work correctly

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

I do not understand why you think I don't use GNOME. This is not news, it was revealed previously.

I have four Ubuntu systems and all but one use the GNOME desktop - the fourth is a server and doesn't even use X.

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

In spite of Sebastien Bacher's persistent wrong-headed notion that the system does not use GNOME and thus the bug is invalid, the problem is apparently related to RANDR.

Revision history for this message
Sebastien Bacher (seb128) wrote :

you seem to not understand the bug, those interfaces just write configuration keys but don't have any effect without a daemon running so they start the daemon if it's not running, that's what happens there

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

O.K.
what interface?
what configuration keys?
what daemon?

Suggestion: If you intend to be clear in your explanation, you need to be less abstract and more specific.

For example, from specific to more abstract…
my cat "Kitty"⋯housecat⋯Felis catus⋯Felinae⋯mammal

Specifically, what was starting RANDR, since disabled and problem defeated? (if it's possible to know)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.