Bug 426227 - Appearance of windows
Summary: Appearance of windows
Status: RESOLVED DUPLICATE of bug 341391
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2020-09-05 23:13 UTC by K6 de Dijon
Modified: 2020-10-05 05:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description K6 de Dijon 2020-09-05 23:13:58 UTC
SUMMARY Appearance of windows


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
Distribution Debian 10 Buster
Processor: 4xintel core I5-6400 CPU 2.70 GHz
Physical memory: 7.69 Gio
Exchange memory: 15.26 Gio


Bonjour,
First French, second translation auto in English

Je ne suis pas informaticien, il se peut que vous considériez que les problèmes exposés soient à répartir dans plusieurs catégories pour des spécialistes. 

J’ai récemment installé Debian10 Buster et la version de KDE plasma qui est proposée avec (voir ci-dessus).

Je découvre que cette version de KDE est moins paramétrable que les précédentes.
1) Notamment, ayant un écran de 3840x2160 soit de résolution environ 125 px/inches, j’ai besoin d’adapter la largeur des barres de défilement. La largeur par défaut est trop fine et j’ai du mal à atteindre le curseur. La largeur actuelle, mesurée sur une capture d’écran, est de 5px. Je souhaiterais passer vers 15 à 20px.

2) La fenêtre KDM ou ce qui fait office d’écran de démarrage est écrite en très petit comme si les paramètres de configurations n’étaient pas pris en compte. Pour mémoire, j’ai réglé les polices Noto sans à 16 points pour mon écran 4K. Pour information, 16 points est un peu petit pour moi, mais à 17 points l’affichage est incomplet ou trop chevauchant avec la ligne du dessus.
De plus, dans cette fenêtre, la largeur de saisie du mot de passe est un peu juste pour pouvoir suivre si les touches sont bien prises en compte. Mon mot de passe fait 13 caractères. J’ai constaté que parfois la saisie d’un caractère engendrait de 3 à 5 points ! (répétition involontaire) C’est pourquoi, il me paraît nécessaire de pouvoir visualiser les retours d’action sur les touches.

3) Dans le panneau de configuration du système (systemsettings5), je ne trouve pas où installer les écrans de sauvegarde.
J’ai tenté une installation séparée, mais le démon prend trop de ressources et finit par ralentir l’ensemble du système. Autrefois on trouvait cela soit dans "Comportement de l'espace de travail" soit dans "Gestion de l’énergie". Pour ma part, cette fonction étant plus proche de la gestion de l’énergie que de l’espace de travail normal, il me semble plus logique de gérer les économiseurs d’écran dans cette section. D’autant plus que les différents temps de veille sont dans cette section.


Voici donc trois préoccupations qui doivent concerner d’autres utilisateurs et que je souhaiterai voir réglées dans une prochaine mise à jour.

Cassis

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Hello,
I am not a computer scientist, you may consider that the problems exposed should be divided into several categories for specialists.

I recently installed Debian10 Buster and the version of KDE Plasma which is proposed with (see above).

I discover that this version of KDE is less customizable than the previous ones.
1) In particular, having a screen of 3840x2160 or resolution about 125 px/inches, I need to adjust the width of the scroll bars. The default width is too thin and I have trouble reaching the cursor. The current width, measured on a screenshot, is 5px. I would like to move to 15 to 20px.

2) The KDM window or what acts as a start screen is written in very small as if configuration settings were not taken into account. For the record, I set the Noto fonts without 16 points for my 4K screen. For the record, 16 points is a bit small for me, but at 17 points the display is incomplete or too overlapping with the top line.
Also, in this window, the password input width is a little fair to be able to track if the keys are properly taken into account. My password is 13 characters. I found that sometimes the seizure of a character resulted in 3 to 5 points! (involuntary repetition) That's why I think it's necessary to be able to visualize the feedback on the keys.

3) In the system configuration panel (systemsettings5), I can't find where to install the backup screens.
I tried a separate installation, but the demon takes too many resources and ends up slowing down the whole system. In the past, this used to be found either in "Workspace Behavior" or in "Energy Management. For my part, this function being closer to energy management than to normal workspace, it seems to me more logical to manage the screen savers in this section. Especially since the different waking times are in this section.

So here are three concerns that should concern other users and that I would like to see resolved in a future update.

Cassis
Comment 1 K6 de Dijon 2020-09-05 23:24:28 UTC
screen 4K
Comment 2 Christoph Feck 2020-09-06 03:44:23 UTC
Please report one ticket per issue.

1) is a duplicate of bug 396747, which is fixed in Plasma 5.18 or later.

2) is about the display manager, which is probably SDDM. If unsure, please ask in a forum of your distribution which display manager you are using, and report the issue there. KDE's Plasma doesn't currently have its own implementation of a display manager.

3) I have never heard the term "installing backup screens". Graphical screen savers have been removed from Plasma, because they waste energy, and don't save anything. If you want to save power, use actual screen energy saving modes.

Please clarify what exact functionality is missing there.

For more information about bug reporting, please see https://community.kde.org/Get_Involved/Issue_Reporting
Comment 3 K6 de Dijon 2020-09-07 15:06:35 UTC
Hello Christophe,
Thank you for your response.

For point 1 regarding the width of the scroll bars, I must be nunuche because I can not find the solution of the bug 396747.
In my version 5.14 the bug is not corrected according to your message and I am related to what Debian wants to publish, because I do not know how to compile.
However, I'm looking and I found the file /usr/share/themes/Breeze/gtk-3.20/gtk.cs in which I spent 5 min-width and min-height settings at a value of 14px in the "scrollbar" section. It's a little low, but it's much better than the values that ranged from 4 to 8px.
I am aware that I should change this when updating this point.

For point 2, it is actually SSDM, I loaded a theme that has a wider dialogue box.

For point 3, I have not been paying attention to the English translation, this is screensaver.
I am aware that screensaver does not save energy. However, it preserves the screen so that it is not marked by an extended fixed display.
Being in an environment where I am often interrupted, I got used to this solution so I didn't have to close or hide the application while working.

In the hope that we will keep a highly customizable and graphically customizable KDE

Cassis
Comment 4 Bug Janitor Service 2020-09-22 04:33:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 K6 de Dijon 2020-09-22 17:20:25 UTC
Hello

For point 1 
regarding the width of the scroll bars, I found two files:
/usr/share/themes/Breeze/gtk-3.20/gtk.css
and
/usr/share/themes/Breeze-Dark/gtk-3.20/gtk.css
in which I changed the values of the srollbar section
min-width
And
min-height
which are now at 14px.

This doesn't work with all applications (or software).
For example, the vertical scroll bar on the KDE menu remains thin.
But this suits me for now, many applications have been influenced by my changes.

=====
For point 2
I chose another connection window that has a wider input space.

=====
For point 3
screensaver.
I persist, I am aware that the screensaver does not spare energy. However, it preserves the screen so that it is not marked by an extended fixed display.
Being in an environment where I am often interrupted, I got used to this solution so I didn't have to close or hide the application while working.

If you need more information, I will try to share it with you.
Well cordially,
Cassis
Comment 6 Christoph Feck 2020-09-23 22:51:25 UTC
> it preserves the screen so that it is not marked by an extended fixed display.

I don't understand (maybe use your native language), but graphical screen savers are not coming back. You can configure the lock screen to automatically appear and use animated wallpapers there if you like to watch the computer wasting energy.

*** This bug has been marked as a duplicate of bug 341391 ***
Comment 7 Christoph Feck 2020-09-23 22:57:54 UTC
I just noticed you originally described the issue in french.

Please clarify why the screen locker provided by Plasma is insufficient for your use case to hide your current work screen when idle.
Comment 8 K6 de Dijon 2020-10-05 05:20:47 UTC
Good morning
Following your suggestion to use 
Workspace - Workspace Behavior - Screen Locking
and choosing a screen in the Appearance tab

I do have the sleep function that activates, but the display is FIXE. There is therefore a risk of marking the screen.

When I am interrupted, it lasts from a few minutes to more than an hour.
So I got into the habit of putting the screen on the screensaver after 5 minutes and triggering the screen cut after 45 minutes.
The most frequent interruptions range from 20 to 35 minutes. So I don't have to wait for the time of awakening to resume the current task.

I'm not looking for a complicated screensaver since ASCIIquarium suits me.

Waiting to read you.
Cassis
PS : Yes I'm french, this is an automatic translation