Questions about Manjaro, monitor and kernel settings

Support KDE Plasma
1

Hello, friends. Forgive me, perhaps I’m using the forum search poorly. But I would like to ask a few questions. They may have already been asked, but I don’t know how to formulate a search query to find the topic I’m looking for.

  1. In the KDE Plasma settings, before recent updates, it was possible to easily and simply select a kernel. This made Mnajaro one of the distributions where it was fast and convenient, without the need for command line knowledge. Will this setting return to the KDE Plasma settings menu?
  2. Explain why many hotkeys were reassigned and made the way they are configured in Windows? For example, previously I pressed F10 in Dolphin and could create a folder. Now this is done using Ctrl+Shift+N (Windows style). If the settings were the same for years, and then they were changed, is this convenient for existing users?
  3. I have a bug report about the widget for switching the monitor and adjusting the brightness of monitors. I don’t know where to direct them, maybe someone will notice them here. When switching monitors, the switch buttons change places according to their logic. If I press the monitor on/off on the right several times, then the next time I press the same power button as before, it is located on the left. Although, previously it was located on the right, as specified in the KDE Plasma settings. That is, the same button, without changing any settings at all, turns on the monitor differently. And shutdown also happens differently. If I, for example, turn off the monitor on the right, then after a while, pressing the same button, the monitor on the left turns off. You have to press another button (which, in theory, turns off the left monitor).
    I have two identical Manjaro installed on different SSDs.
    Adjusting screen brightness for the Philips 246E monitor only works on one of them. On the second it is either there or not. On the second OS, before the latest major updates, the brightness was adjusted on both monitors (Samsung and Philips), on the second OS - only on Philips. With the same system settings, the brightness on the taskbar is either there or not. Also in the monitor settings in the KDE settings. Brightness adjustment is there or not.
  4. The most pressing issue for me is turning off the monitor over time. Previously, before changing the video card from nVidia to AMD, my Philips 246e monitor turned off according to the time set in the KDE settings without problems. However, after changing the video card, it stopped turning off. If you leave only the old Samsung 223BW monitor, it turns off. But I need two monitors. Philips turns off, a message appears that it is in standby mode, but immediately turns on. I tried installing different Unix-based OSes: Debian, Ubuntu, Fedora and a few more. Disables only on Ubuntu.
    I tried to look for non-standard solutions, I turned to the GPT chat, but all these solutions are not suitable.
    At the same time, the new MSI monitor also does not turn off over time (I tested its connection).
    Other devices (mouse, keyboard) have nothing to do with it, I tried turning them off.

Operating System: Manjaro Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.8.12-3-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-9100F CPU @ 3.60GHz
Memory: 15,6 GiB of RAM
Graphics Processor: AMD Radeon RX 470 Graphics

2
  1. the kcm applet is incompatible with Plasma 6
    • use the application directly Manjaro Settings Manager
  2. Plasma default
  3. Be sure your widgets are compatible with Plasma 6
  4. Be sure to cleanup your old configurations - they may be incompatible with Plasma 6

A helper script for cleaning up the plasma settings

Your kernel 6.8 is EOL - see https://kernel.org and the latest stable announcement - comment number 2

2 Likes
3
  1. Yes, it is possible that the settings were reset due to the deletion of the .cache folder, due to which the interface did not work.
  2. This problem existed before the plasma update.
4

The module you are referring to — a kcm, in technical jargon — was written using qt5 and is not compatible with qt6.

I do not know whether there are any plans of rewriting it for qt6, but you can either way still get the same functionality by looking for the Manjaro Settings Manager in your application launcher menu. It’s the exact same thing as before, but as a standalone tool.

Plasma 5 had two mechanisms for defining shortcuts, kglobalaccel and khotkeys. For Plasma 6, khotkeys was dropped and everything in that regard is now handled through kglobalaccel.

As a result, some (but not all) of your old keyboard shortcuts have been reassigned to kglobalaccel, but with default values, many of which may mimic the behavior of Microsoft Windows, because the KDE developers assume the vantage that new users will almost invariably come from the Microsoft ecosystem, and that catering to their Windows habits will make them feel more at home in GNU/Linux.

Personally, I do not share that vantage, because I believe that if GNU/Linux caters to Windows habits too much, then the newcomer will also quickly start assuming that the whole system behaves like Microsoft Windows, or — as is already the case among some of our newbies — that GNU/Linux would be a Windows-like system.

Furthermore, when the differences between GNU/Linux as a UNIX-family operating system and Microsoft Windows then finally come to the surface, then all one gets is an exacerbated and delayed culture shock. So I personally believe that it would actually benefit the newbies if they are confronted with the differences from up front, right in the moment they first start using GNU/Linux (or any other UNIX-style operating system). And it’s also more honest.

But then again, I’m not a developer, and none of the graphical user interfaces offered in Manjaro are being developed by us. Plasma is developed by KDE, GNOME is developed over at RedHat, Cinnamon is developed by the people behind Linux Mint, and so on.

If you are certain that it is indeed a bug and not a feature — I do not know, because I only have one monitor — then the best course of action would be to consult the KDE Bug Tracker for whether this bug has already been reported, and file it yourself if it hasn’t.

Another venue where you can contact the KDE developers — although I’m uncertain whether this would be the correct avenue for submitting bug reports — would be the KDE Discuss forum, which is powered by Discourse, just as the Manjaro forum here, and which will thus feel quite familiar to you.

Same thing here as in the point above. :man_shrugging:

2 Likes
5

Thank you. I fully support your opinion about allowing new users of Unix-like systems to get used to the new realities for themselves, without using anything related to Windows or Mac.
Since I am a video blogger, and I also have videos in which I encourage using Manjaro Linux, I would like to use it myself with pleasure, and not with a constant search for solutions, with new updates.
I am very grateful to the Manajro team.
Thank you for the links you provided. I will try to find time to study the issue and file appropriate bug reports.
I have not heard of Manjaro Settings Manager before. Already updated the kernel. Thank you.

1 Like
6

Emphasis mine… :point_down:

Actually, here’s the fun fact: macOS is actually a UNIX. It’s based upon a modified FreeBSD and it has been certified with the UNIX® trademark by the Open Group since OS X 10.5 “Leopard”. :wink:

Windows on the other hand is… um… a really, really bad operating system design… :innocent: :face_with_hand_over_mouth:

2 Likes
7

Still caught it. I initially didn’t want to write it, but I thought about it and decided to add it, although I understood that it was also from UNIX)

1 Like
8

I don’t know how, but when the second monitor (DVI) was turned off, the first monitor began to turn off at a specified time

9

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.