Hi wolfi323,
For the xrandr command - i searched and when i change to HMDI1 - this works from the command line.
I do need to find out why KDE is not working - this is the preferred route - to fix KDE rather than run a script to patch over KDE issues.
Regards,
Shadders.
OK, so your monitor is connected to HDMI1.
Btw, if you just run “xrandr” it should show some information about all interfaces.
I do need to find out why KDE is not working - this is the preferred route - to fix KDE rather than run a script to patch over KDE issues.
I suppose you mean KDE’s gamma settings with “KDE is not working”. 
Actually this is just the package kgamma, which doesn’t seem to be in very active development for quite some time.
Well, as I said, the system-wide saving of the gamma settings only works when there’s an /etc/X11/xorg.conf, so if you create one with “X -configure” f.e., this (system-wide saving of the gamma settings) should work and take effect (even on the login screen already).
For the user-specific settings, they are getting written to ~/.kde4/share/config/kgammarc alright, and read back when entering the settings module, as you noticed. So that part does work.
The problem is, that nothing seems to read those settings on login AFAICT. So of course the settings are never applied, only if you enter the settings module.
I have no idea when was the last time that it worked (I never used that in eleven years of having openSUSE/KDE as my main OS), maybe it isn’t working anymore since KDE3 even?
If you want to have that fixed, you should file a bug report at http://bugs.kde.org/.
Hm, I found a bug report:
https://bugs.kde.org/show_bug.cgi?id=218668
But this was already filed in 2009 against KDE 4.3.4!
So I guess it’s safe to say that nobody cares about kgamma. Better forget about it and use a xrandr script.
OTOH, you would just need to write a script/program that reads the kgammarc file and applies the settings, and run it on login.
Shouldn’t be too hard to do, you could copy all the relevant code from kgamma itself. Or read the values and call xrandr with them accordingly.
I’ll try to come up with something in the next days…
OTOH, Saving system-wide doesn’t work for some reason, even with an xorg.conf. No idea why (haven’t investigated further yet), because calling xf86gammacfg manually does successfully change the xorg.conf and the settings module also just calls this.
If you are trying to get accurate reproduction between images, photos, to screen and to printer, the recommended gamma-correction procedure should be done on the monitor or display hardware itself, not through software gamma controls in the Operating System.
Most Prepress Gamma correction guides will give you this advice.
Hi wolfi323,
I tried the X -configure command and received a server error :
linux-9cy6:/etc # X -configure
(EE)
Fatal server error:
(EE) Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE)
linux-9cy6:/etc #
So the xrandr is probably the best option.
In the sane.d directory - which is the most appropriate value to change - i can see that they are 1.0 or 1.5 even - which takes precedence - would you know ?. Thanks.
ane.d/artec_eplus48u.confption redGamma 1.0
sane.d/artec_eplus48u.confption greenGamma 1.0
sane.d/artec_eplus48u.confption blueGamma 1.0
sane.d/artec_eplus48u.confption masterGamma 1.9
sane.d/plustek.confption redGamma 1.0
sane.d/plustek.confption greenGamma 1.0
sane.d/plustek.confption blueGamma 1.0
sane.d/plustek.confption grayGamma 1.0
sane.d/u12.conf:#option redGamma 1.5
sane.d/u12.conf:#option greenGamma 1.5
sane.d/u12.conf:#option blueGamma 1.5
sane.d/u12.conf:#option grayGamma 1.5
Thanks and regards,
Shadders.
Hi,
Thanks - i am just adjusting the monitor colours - easier with the KDE interface than the monitor itself - more control and less button pressing.
Regards,
Shadders.
That’s because the X server is already running on display :0 and therefore cannot be started.
Either boot to runlevel 3 and run “X -configure”, or tell it to start on another display:
X :1 -configure
But in the meantime I created a new kgamma package which does apply the gamma settings on login. (the user settings from kgammarc, i.e. when “Save settings system wide” is not enabled)
You can find it here:
http://software.opensuse.org/download.html?project=home%3Awolfi323%3Abranches%3AopenSUSE%3A13.1%3AUpdate&package=kgamma
In the sane.d directory - which is the most appropriate value to change - i can see that they are 1.0 or 1.5 even - which takes precedence - would you know ?. Thanks.
Why do you want to change a value in sane.d now? This has absolutely nothing to do with the display. Those are the default gamma values for each scanner driver.
And you shouldn’t change those files anyway, your changes will be lost after an update.
If you do want to change the gamma for scanning, you should be able to do that in the scanning application you’re using. (xsane?)
Hi wolfi323,
Thanks - if i boot to run level 3 i will then have to log into the system at the command line level - so i had better take note of the requirements.
I was searching for the Gamma and this was listed in that directory - i thought that was where the defaults were placed.
Thanks for the script - i will implement later.
Still learning about KDE and how it interfaces to the OS.
Regards,
Shadders.
FYI, I submitted a fix to KDE today.
So kgamma’s user settings should be correctly applied again on login with 4.13.3, to be released on July 15th.
Hmm.
But this way will never give you accurate matching, as the two methods will wind up in arguments over final rendition.