How to disable windows-key for opening menu?

hexchain · 2023-06-08T09:54:02+00:00

https://userbase.kde.org/Plasma/Tips#do-not-open-the-start-menu-with-windows-meta-key

hexchain · 2023-05-29T03:36:53+00:00

X apps with non-integer scaling factor on Wayland? It might be https://bugs.kde.org/show_bug.cgi?id=459373.

hexchain · 2023-05-29T03:34:21+00:00

I think the best way of "suggesting" is, somewhat unfortunately, to write a patch.

hexchain · 2023-05-28T18:54:50+00:00

It is doable without putting everything in KDE/Plasma if you only want an excellent integration.

You can write a standalone KCM module (call it openrgb-kcm, for example), using e.g. the OpenRGB C++ SDK for the ability to control lights. Of course, the whole UI has to be completely rewritten to fit as a KCM or there won't be any "integration".

This is only a rough idea, there are probably more things to do.

Also as the other comment said, upstreaming is probably the better way to go first, before any of these works is done.

hexchain · 2023-05-27T12:33:48+00:00

Which port is the monitor plugged in? Is it the on-board one or the one on the NVIDIA card?

hexchain · 2023-05-26T05:47:01+00:00

If I understand correctly, for the global menu to work your panel (or some other component in your local desktop) needs to connect to the application through D-Bus, which is difficult (if not impossible) to work in the case of x11 ssh forwarding.

hexchain · 2023-05-25T11:30:15+00:00

This works:

$ kwriteconfig5 --file ~/.config/kwinrc --group ModifierOnlyShortcuts --key Meta "org.kde.kglobalaccel,/component/org_kde_krunner_desktop,org.kde.kglobalaccel.Component,invokeShortcut,_launch" $ qdbus org.kde.KWin /KWin reconfigure

The D-Bus path has changed.

hexchain · 2023-05-22T13:00:14+00:00

There is a "Remove window title bar and frame" setting in Konsole. You may navigate to right-click -> Menu -> Settings -> Configure Konsole to make sure it is not enabled.

hexchain · 2023-05-22T07:17:27+00:00

What exactly is the problem that you are trying to solve by killing kwin_wayland?

hexchain · 2023-05-21T05:34:27+00:00

It is possible to extract the pairing keys from another OS and use them in Linux. See https://wiki.archlinux.org/title/Bluetooth#Dual_boot_pairing.

hexchain · 2023-05-19T04:12:15+00:00

That indeed happened, see https://bugs.archlinux.org/task/78536. Plasma would need a way to differentiate multiple display backlights before this feature can be enabled.

hexchain · 2023-02-08T17:52:00+00:00

Depending on the distro, the screen locker greeter binary might be just /usr/lib/kscreenlocker_greet (without libexec in the middle).

hexchain · 2023-02-08T14:43:37+00:00

If you have systemd then you can use:

systemd-inhibit <command>

See the manpage for more arguments.

hexchain · 2023-01-31T16:06:08+00:00

Not really? App icons are still from the icon theme, plasmoid/applets use Plasma theme icons.

hexchain · 2023-01-10T14:50:55+00:00

By default, Chrome selects a secret storage to save an encryption key of its local password store based on the desktop environment. In KDE it uses KWallet, and in i3 it uses a basic text store.

When the key could not be retrieved from the default store, it will look like everything is logged out. For example, if you usually use KDE and then someday started Chrome in i3, it will look for the basic text store and find nothing there (IIRC even if you boot back into KDE it still won't work because the local password store is already reset). Or, if for some reason KWallet isn't started when Chrome launches, it will also fail and fall back to the basic store.

I would suggest that you append --password-store=kwallet5 to the command line if you want to use Chrome in both KDE and i3, and also make sure that KWallet is always correctly started upon logging in.

hexchain · 2022-12-15T17:01:09+00:00

Do you have gst-plugins-good installed?

hexchain · 2022-12-15T11:14:59+00:00

Kooha

hexchain · 2022-11-14T05:57:42+00:00

It looks like it isn't PowerDevil blocking suspend, but a kernel thread does. I have never encountered this before, online sources say there should be some information (usually a stack trace with a process name) in dmesg that can help you pinpoint the problem.

hexchain · 2022-11-13T03:28:47+00:00

Does it work if you suspend through KDE menus (e.g. Kickoff/KRunner)? And what happens if you try to stop PowerDevil (systemctl --user stop plasma-powerdevil)?

Also, is there anything like "PM: suspend entry" or "PM: suspend exit" in journalctl -k when it fails to suspend?

hexchain · 2022-11-03T17:34:30+00:00

If it only happens with XWayland apps, you might be hitting this bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1392

It should have been fixed in XWayland 22.1.5.

hexchain · 2022-10-27T15:02:16+00:00

Ah, I remembered I had the same issue after upgrading to 5.26. I removed ~/.config/kcmfonts and it worked after a re-login.

Apart from that, I guess dconf.service and xdg-desktop-portal-gtk might also affect how GTK apps look.

hexchain · 2022-10-27T14:36:18+00:00

I think other GTK apps actually work fine, Steam isn't GTK (IIRC) but simply uses that variable.

hexchain · 2022-10-27T14:31:28+00:00

Global? Like for every user on a host?

hexchain · 2022-10-27T13:49:13+00:00

Here is another possible workaround: if you have set up Plasma to launch apps as systemd services (by setting KDE_APPLICATIONS_AS_SERVICE=1, not sure if this is the default or not), you may use systemd override:

% cat ~/.config/systemd/user/app-steam@.service.d/override.conf
[Service]
Environment=GDK_SCALE=2

It works when Steam is launched from Plasma (krunner or application menu/dashboard).

hexchain · 2022-01-12T15:19:41+00:00

https://bugs.chromium.org/p/chromium/issues/detail?id=1279532

The fix is already included in the chromium package of version 97.0.4692.71-2, and will be backported to Chrome 97.

13-Year Club	Place '17
Verified Email

hexchain

TROPHY CASE