Solid/Projects/ScreenManagement: Difference between revisions

From KDE Community Wiki
Line 18: Line 18:
}}
}}


==How to report a bug==
==Debugging Information==
We can't fix bugs if we don't have the needed information to diagnose the problem, so please provide the following information with your bug report:
We can't fix bugs if we don't have the needed information to diagnose the problem, so please provide the following information with your bug report:
Enable debugging output by opening ~/.config/QtProject/qtlogging.ini and make sure you have the following in it:
[Rules]
kscreen.*=true


The output of:
The output of:
kscreen-console bug
kscreen-console bug
Execute kdebugdialog and enable:
*KSRandr
*kded
*kcmshell
*everything with kscreen on it


If your bug is related to the SystemSettings module, please reproduce the bug while executing in a terminal:
If your bug is related to the SystemSettings module, please reproduce the bug while executing in a terminal:
*kcmshell4 kcm_kscreen
*kcmshell5 kcm_kscreen


If your bug is related to how KScreen reacts to certain events (for example you plug your monitor and nothing happens), execute the following in a terminal and reproduce the bug:
If your bug is related to how KScreen reacts to certain events (for example you plug your monitor and nothing happens), execute the following in a terminal and reproduce the bug:
*kquitapp kded
*kquitapp kded
*kded4
*kded5
 
=== FGLRX users ===
With Catalyst 13.12 we should work just fine.
 
With older, please do:
Please enable the following option before reporting a bug:
amdconfig --set-pcs-u32=DDX,EnableSurfaceResizing,1 available since Catalyst 13.2


The option will be enabled by default in future driver versions.
The current screen configuration is very useful to debug, please attach the files located in ~/.local/share/kscreen/ (these are files with long hashnames that contain information about your screen setup).

Revision as of 19:01, 7 June 2016

How we work

All Solid projects operates in the same way, be sure to read How we work

Description

KScreen is the new screen management software for KDE Plasma Workspaces which tries to be as magic and automatic as possible for users with basic needs and easy to configure for those who want special setups.

The project is composed of a few components:

  • KDED Module: Saving and restoring configurations
  • KCM Module: Freely configure setups for each set of connected/plugged screens.
  • kscreen-console: Debugging tool

Project Status

The first release (0.1-alpha1) has been released and it is considered experimental.

Documentation

Currently we're lacking a good End user documentation, help is needed.

How to collaborate

KScreen is a KDE project, so we use the usual ways to communicate to each other and to work together (reviewboard, mailist, irc)

Project Page

KScreen is currently located in playground/base and libkscreen in playground/libs

Mailing list

We're using the kde-hardware-devel mailing list kde-hardware-devel

Debugging Information

We can't fix bugs if we don't have the needed information to diagnose the problem, so please provide the following information with your bug report:

Enable debugging output by opening ~/.config/QtProject/qtlogging.ini and make sure you have the following in it:

[Rules]
kscreen.*=true

The output of: kscreen-console bug

If your bug is related to the SystemSettings module, please reproduce the bug while executing in a terminal:

  • kcmshell5 kcm_kscreen

If your bug is related to how KScreen reacts to certain events (for example you plug your monitor and nothing happens), execute the following in a terminal and reproduce the bug:

  • kquitapp kded
  • kded5

The current screen configuration is very useful to debug, please attach the files located in ~/.local/share/kscreen/ (these are files with long hashnames that contain information about your screen setup).