opening gnome-keyboard-properties changes screen resolution

[keepitsimpleengr]

Binary package hint: gnome-control-center

~# lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
~# apt-cache policy gnome
gnome:
  Installed: (none)
  Candidate: 1:2.28+1ubuntu3
  Version table:
     1:2.28+1ubuntu3 0
        500 http://mirrors.us.kernel.org/ubuntu/ lucid/universe Packages
====
~# which gnome-keyboard-properties
/usr/bin/gnome-ke~# dpkg -S /usr/bin/gnome-keyboard-properties
dpkg -S /usr/bin/gnome-keyboard-properties
gnome-control-center: /usr/bin/gnome-keyboard-properties
====
Opened gnome-keyboard-properties using menu. When opening the resolution of screen 0 changes from 2560x1600 to 1280x800. It can be reset using nvidia-settings. screen 1 resolution is unchanged.
====
Very similar to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/598677

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-control-center 1:2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Jul 31 10:17:12 2010
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gnome-control-center

[Sebastien Bacher (seb128)]

Thank you for your bug report. Do you use GNOME? Is gnome-settings-daemon running before you open the capplet?

[keepitsimpleengr (keepitsimpleengineer)]

I'm not sure what a capplet is. gnome-keyboard-properties was opened from the ubuntu menu System>Preferences>Keyboard.

Version: 2.30.2 Distributor: Ubuntu Build Date: 06/25/2010

~# ps -e | grep 'gnome'
 2070 ? 00:00:00 gnome-session
 2127 ? 00:00:00 gnome-keyring-d
 2131 ? 00:00:00 gnome-panel
 2150 ? 00:00:00 polkit-gnome-au
 2159 ? 00:00:00 gnome-power-man
 2386 ? 00:00:00 gnome-dictionar
 2763 ? 00:00:00 gnome-terminal
 2765 ? 00:00:00 gnome-pty-helpe
~# ps -e | grep 'compiz'
 2155 ? 00:00:06 compiz
~# ps -e | grep 'gdm'
 1084 ? 00:00:00 gdm-binary
 1174 ? 00:00:00 gdm-simple-slav
 1702 ? 00:00:00 gdm-session-wor
~# ps aux | grep 'X'
root 1206 3.5 1.5 156652 64860 tty7 Ss+ 10:52 0:23 /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-8kaF0G/database -nolisten tcp vt7
root 2915 0.0 0.0 7624 904 pts/0 S+ 11:02 0:00 grep X

[keepitsimpleengr (keepitsimpleengineer)]

I retried "System>Preferences>Keyboard" and ubuntu crashed (no screen, no consoles).

I restarted and reset nvidia settings, xorg.conf attached.

[Sebastien Bacher (seb128)]

could you try if you get the same issue when running the gnome-settings-daemon?

[keepitsimpleengr (keepitsimpleengineer)]

running "gnome-settings-daemon" from Alt-F2 I got the same result, ubuntu crashed (no screen, no consoles).

[keepitsimpleengr (keepitsimpleengineer)]

With the xorg.conf file previously attached, invoking gnome-keyboard-properties causes the system to crash (no screen, no consoles)

After changing xorg.conf using nvidia-settings, setting resolutions to "auto" vice 2560x1600 for screen0 and 1440x900 for screen1, the system no longer crashes and the resolution reset using nvidia-settings. However there are changes in the desktop including different icons on panel, changed backgrounds on panel items, different menu color and some window colors.

Redone xorg.conf attached here.

[Sebastien Bacher (seb128)]

seems simply that gnome-settings-daemon is applying the configuration defined with the GNOME xrandr capplet

[keepitsimpleengr (keepitsimpleengineer)]

I added the following to xor.cong:

Section "ServerFlags"
    ⋯
    Option "RandR" "false"
    ⋯
EndSection

and now when "System>Preferences>Keyboard" is invoked, the resolution does not change (hooray) but there are still changes in the desktop including different icons on panel, changed backgrounds on panel items, different menu color and some window colors.

I can reset the colors (mostly) using "System>Preferences>Appearances:Theme:Customize…:Controls:Clearlooks", However the background of some panel items do not change.

If I open panel properties, and change some property (i.e. show hide buttons), the the icon backgrounds will revert to the original, desired panel color.

[Sebastien Bacher (seb128)]

it's not a bug, the GNOME settings daemon just set the GNOME configurations

[keepitsimpleengr (keepitsimpleengineer)]

I would say when you open the key board setting and have the resolution, and theme change, it's kind of like have the shower turn on and commode flush when you turn on the bathroom light, and that would bug me.

[Sebastien Bacher (seb128)]

the keyboard configuration utility is a GNOME one and supposed to be used under GNOME where the settings daemon is running, without it your changes are not applied to the session so it would be useless

[keepitsimpleengr (keepitsimpleengineer)]

ok.
so why would the GNOME settings daemon make changes to the session without input from the user other than opening a GUI to access it? And why would it make changes to things other than the GUI was designed to do? And why would it make changes that it cannot change back?

A potpourri of unwanted and unintended consequences will eventually deter even the the most fervent advocate.

I refer you to http://library.gnome.org/devel/hig-book/stable/index.html.en

[Sebastien Bacher (seb128)]

the configuration dialog you use is made to work under GNOME, it doesn't apply settings but just writte configurations than gnome-settings-daemon apply, under a GNOME environement that's transparent to the user. Now for some reason gnome-settings-daemon is not running for you, option would be to display a "that configuration can't work out of GNOME" or to run the settings daemon which it's doing now

[keepitsimpleengr (keepitsimpleengineer)]

I run GNOME with UBUNTU and have since 8.04.

So I compared GNOME processes running (ps aux | grep gnome) for my system (10.04 dist-upgraded) to a clean install on the same hardware, and "/usr/lib/gnome-settings-daemon/gnome-settings-daemon" is running on the clean install but not on the upgrade.

Furthermore there is a process "gnome-system-monitor" running on the upgrade that is not running on the clean install.

So if the problems I am having are due to the lack of a running "gnome-settings-daemon" and possibly a running "gnome-system-monitor" which shouldn't be…

Then is the bug properly "10.04 dist-upgrade fails to start gnome-settings-daemon properly"?

[keepitsimpleengr (keepitsimpleengineer)]

Forget gnome-system-monitor, my oversight.

[keepitsimpleengr (keepitsimpleengineer)]

So I tried starting gnome-settings-daemon with:
/usr/lib/gnome-settings-daemon/gnome-settings-daemon

I got a message that randr was not found.

So I commented out the randr false in serverflags in xorg.conf (#10 above), and tried to start gnome-settings-daemon again.

~# /usr/lib/gnome-settings-daemon/gnome-settings-daemon

** (gnome-settings-daemon:2805): WARNING **: Failed to acquire org.gnome.SettingsDaemon

** (gnome-settings-daemon:2805): WARNING **: Could not acquire name

From: http://www.listware.net/201006/freebsd-gnome/113809-workspace-switcher-cannot-add-workspaces.html

gnome-settings-daemon is not running and will not start. Manually attempting to start results in these errors:
failed to acquire org.gnome.SettingsDaemon
could not acquire name
This lead me to realize my /etc/hosts did not reference my domain name. I modified it like so:
::1 localhost localhost.toyon.corp
127.0.0.1 localhost localhost.toyon.corp
gnome-settings-daemon still will not start with these errors:
failed to acquire org.gnome.SettingsDaemon
could not acquire name
Q1: Why can't gnome-settings-daemon "acquire org.gnome.SettingsDaemon"?
Q2: Why can't gnome-settings-daemon "acquire name"?
Thank you,
Chris
Re: Workspace Switcher: cannot add workspaces
by Kevin Obermanon 2010-06-30T18:40:41+00:00.

This is the sort of issue I was having on one of my systems before I
blew away ~/.gnome2, ~/.local, and ~/.config. (I would think ~/.gnome2
most likely for this one.)
Try getting out of Gnome, moving ~/.gnome2 to something like
~/.gnome2.save and start Gnome back up. Once I did that (and I did all
three directories as I was hitting a bunch of weirdness), things started
to behave normally, although I did have to re-create my custom menus and
reset a bunch of stuff.
I had probably upgraded gnome from 2.22 through all even version to the
present and I know a number of things have changed in the schema over
that time. I guess they finally caught up with me. :-(
=======