Bug 14942 - the "display" and the "kgamma" arguments give exactly the same gamma screen.
Summary: the "display" and the "kgamma" arguments give exactly the same gamma screen.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-04 05:26 CET by w unruh
Modified: 2018-07-12 12:06 CEST (History)
1 user (show)

See Also:
Source RPM: kdebase4-runtime-4.12.5-1.2.mga4
CVE:
Status comment:


Attachments

Description w unruh 2015-01-04 05:26:14 CET
Description of problem:
kcmshell4 display
is supposed to give the display adjusting function--ie choosing which display to use, choosing the resolution of the display, etc. This was how it workied in the past  (mageia 2 3 and maybe even earlier) Now however it give the same output as 
kcmshell4 kgamma

(Note that the bug does not appear to be in kcmshell4 itself, since if I copy in a version from Mageia 2, it behaves in exactly the same way). It appears to communicate with something via the dbus, but I have no idea what)


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Run kcmshell4 display
2.A window opens with the gamma adjustment tool. It is precisely the same window as
if one runs kcmshell4 kgamma

There does not appear to be any option which will give the diplay adjustment window, which it did before (earlier versions of kcmshell4).


Reproducible: 

Steps to Reproduce:
Comment 1 w unruh 2015-01-04 06:12:44 CET
It appears that Mageia 4.1 installs kscreen and plasma-applet-kscreen which block krandr. When I installed krandr removing kscreen and plasma-applet-kscreen, suddenly kcmshell4 display works again and gives both the display selector and the gamma. Also, in System Settings->Display and Monitor I get a decent option to pick the screens. 

The Mageia 4.1 installation procedure is broken as far as the display option is concerned. I have no idea what kscreen was supposed to do, but it certainly breaks stuff.
Comment 2 James Kerr 2015-01-04 10:45:09 CET
'kcmshell4 kscreen' opens the display configuration window.

This wiki page describes the reasoning for the switch from krandr to kscreen as default:
https://wiki.mageia.org/en/Feature:Kscreen
Comment 3 w unruh 2015-01-04 22:43:32 CET
I agree that this is not the place to argue the relative merits of kscreen vx krandr. However it is still a bug somewhere *kcmshell4?) that 
kcmshell4 display
does not produce the display adjustment facility when kscreen is used, but does when krandr is used, which was my original bug report.
The display option is still a valid option if kscreen is used, and should do something sensible if kscreen is used.

Also 
kcmshell4 --list
does not list kscreen as an option, although running 
kcmshell4 kscreen 
does produce a huge window with the kscreen display (and if the people who wrote 
that wiki page believe it is modern, intuitive and user-friendly interface",
 their notion of those words differs a lot from mine, but that again is irrelevant)
Comment 4 w unruh 2015-08-05 05:56:06 CEST
Still a problem  in Mageia 5.
kscreen not listed as option to kcmshell4 and 
kcmshell4 display gives same effect as kcmscreen4 kgamma

Hardware: i586 => x86_64
Version: 4 => 5

Samuel Verschelde 2016-11-01 11:56:30 CET

Assignee: bugsquad => kde

Comment 5 w unruh 2016-12-22 23:32:47 CET
I guess the main thing would be to have kscreen listed as an option for kcomshell5 and kcmshell 5 (sorry that in the above couple of comments I use kscreen instead of kcmshell.) The kde people refuse to fix this in kde4. I will test in kde5 as well.
Comment 6 Marja Van Waes 2018-07-12 12:06:49 CEST
Closing as OLD, because KDE is entirely different in Mga6 and later.
Mga5 is no longer officially supported.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.