Bug 18265 - kcmshell4 kscreen is missing "Unify outputs" section on laptop
Summary: kcmshell4 kscreen is missing "Unify outputs" section on laptop
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-26 03:15 CEST by w unruh
Modified: 2016-11-06 14:14 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description w unruh 2016-04-26 03:15:47 CEST
Description of problem:
I am running MGA5 on a Panasonic S10 laptop. If I go to SystemSettings->Display->Display configuaration, I get a top of the window with Manage and configure monitors and display section, and at the bottom, a "Unify outputs"
section. 

However if I run
kcmshell4 kscreen, I do not get that second part of the window at all. the window hsd only yhr yop half of the that display, the Unify outputs and the space above that, including the Primary display line is missing. 

On two of my desktop machines running MGA5 I do not have that problem. 

Since it is my laptop I use to present talks, and it is my laptop that I most want to "Unify outputs" this bug is annoying. 
(Yes, I could just open SystemSettings and then Display and than DisplayConfiguration, but that is a pain while trying to get ready for a talk. Much easier to just click on one icon on the desktop)

kdebase4-runtime-4.14.3-5.mga5


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


How reproducible:
Always.

Steps to Reproduce:
See above, although as stated it is on my laptop it does not work. On my desktops it does work. Note all machines have Intel onboard video cards.
Marja Van Waes 2016-04-28 20:09:16 CEST

CC: (none) => marja11
Assignee: bugsquad => mageia

Comment 1 w unruh 2016-08-03 00:05:57 CEST
Lets prod this once more. 
The Display item in the SystemSettings allows one to change the resolutions of the various screens attached to the system, to Unify Outputs, and in general to control
the output of the video card. 
One would think tht the kcmshell4 kscreen ( or kcmshell4 kcm_kscreen) would do the same, but all of the resolution control functions are missing. You just get a little picture of the screen/screens and no way of controlling them. This is a 
serious bug in 
kcmshell4 .
Note that the funtionality must be there somewhere since one can do it from SystemSettings. 
I want a single desktop icon to control the screen since I do it so often (using my laptop to give talks) and having to open SystemSettings just to accomplish this little task is a pain when One is floundering around at the front  of an audience impatient to hear one talk. 

Does anyone else have this problem or am I alone?
Samuel Verschelde 2016-08-25 16:22:55 CEST

Assignee: mageia => kde

Comment 2 w unruh 2016-11-01 16:40:36 CET
An additional bit of information:

kcmshell4 kscreen as myself as user does not display the lower half of the screen
However if I run X as root and run kcmshell4 kscreen as root, I get the full screen.

If I run it from the SystemSettings, as user, I get the full screen. That root runs it from the command line, but user does not would suggest a permissions problems. However, that it works in SystemSettings but not from the command line really leaves me mystified.

Any suggestions?
Comment 3 w unruh 2016-11-06 14:14:36 CET
I recently had to kill off my .kde4 home directory and allow kde to install a new one. One of the side effects was that kscmshell4 kscreen suddenly started to work properly again. No idea what, in the old one, was the problem. But I guess this should be closed. 
It would have been nice if this were fixed by tracking down the problem and fixing it, but as a Mageia bug or KDE bug, it seemed impossible to find, and it was fixed by reinstall, so it should be closed.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME


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