| Summary: | Display settings not visible in fedora 19 | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Sayantan Datta <kenzo.zombie> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | hbock, kde, sitter |
| Priority: | NOR | ||
| Version: | 4.10.5 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| URL: | https://docs.google.com/file/d/0B8TIVvkuwqrEMjdyeHJiYUE1SzA/edit?usp=sharing | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Can someone verify whether this patch fixes the issue? | ||
|
Description
Sayantan Datta
2013-08-19 04:22:50 UTC
Fedora 19 seems to ship kscreen to replace the unmaintained krandr. Run "kcmshell4 --list | grep randr" to see whether kcm_randr is present in your system. But I'm confused by the screeshot. Created attachment 84243 [details]
Can someone verify whether this patch fixes the issue?
from display.cpp:
addTab( "randr", i18n( "Size && Orientation" ) );
addTab( "nvidiadisplay", i18n( "Graphics Adaptor" ) );
addTab( "nvidia3d", i18n( "3D Options" ) );
addTab( "kgamma", i18n( "Monitor Gamma" ) );
if ( QApplication::desktop()->isVirtualDesktop() )
addTab( "xinerama", i18n( "Multiple Monitors" ) );
addTab( "energy", i18n( "Power Control" ) );
so apparently kcm_display is a meta-kcm containing other KCMs, which in itself seems like a jolly bad idea (compared to systemsettings categories which work at runtime....).
the problem essentially is that (supposedly) neither of those KCMs is installed by fedora and kubuntu anymore (previously only krandr was and that is no replaced by kscreen). I think that pretty much proofs my point that the entire KCM is wrong.
regardless, the appropriate fix here is to add kscreen to the list of *possibley* KCMs to list.
p.s.: please also note that I absolutely did not manage to get this KCM to show up anywhere, so short of kcmshell4 display or krunner->display there appaers to be no way to actually access this thing.
p.p.s.: in the future please attach screenshots to the bug report directly (see the attachments box towards the bottom of the report page).
fortunately changes to the way the sub-kcm names come to be tab names will cause at the very least fuzzy strings in the l10n which is not desired for stable changes I presume. therfore I do not see how to solve this issue for 4.11 (short of replacing randr with kscreen which from an upstream POV is wrong)... best suggestion I have for distributions who use kscreen by default is to swap it in for randr in a distro patch against kcontrol/hardware/display.cpp. not perfectly covering all bases but at least works by default. upstream I'd rather like the kcm to go away for plasma workspaces 2. moving bug to general component. Arjun Ak, please note that while your patch would fix the symptom at a high level it does not qualify for inclusion since the display KCM is not replaced by kscreen, krandr is, and since display is a meta-kcm for krandr&friends making it start *only* kscreen instead would make the KCM pointless. Patch for interested distributions: http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/kde-workspace/view/head:/debian/patches/kubuntu_kcm_display_add_kscreen.diff So this was fixed with 4.11 ? |