Standreas

It's still to grey out under Wayland. It's possible to use external agents to show an OSD at volume changes by keyboard: 1) https://github.com/heyjuvi/avizo * Add `avizo-service` to autostart *...

Not really, see the main discussion https://github.com/lxqt/lxqt-globalkeys/issues/282

Don't overestimate users... they see an option which doesn't work and will be frightened by such commands ;) It's not about changing volume from keyboard which works out of the...

Oops, I was sure the tooltip was shown with that setting and not a regular notification. But using by default the qdbus shortcut isn't feasible - as soon users change...

> I don't remember X11 — extra things can be done under it — but _that setting_ is about notifications and works like a charm on Wayland. "Notify volume changes...

I see, then the setting is respected. But telling users to find out their correct path to use it is the same as telling them to use avizo. It's a...

To get the paths easier using `qdbus6 org.kde.StatusNotifierWatcher` then to navigate the GUI. Anyway I was thinking of a way that works always (volume|volume2|volumeX): ``` #!/bin/sh # actions: up|down|mute(=toggle mute)...

I think the only "clean" way if solving this is shipping a sort of `lxqt-qdbus` script in `lxqt-wayland-session` with the above code and other code for * open fancy menu...

It does look more complicated. Just changing the translation in a `*.ts` file did work:  Updating the translations the `*.ts` files have the items now untranslated but either in...

Using Clang this isn't shown but many of the following both for mainmenu and fancymenu: ``` [ 37%] Generating mainmenu_zh_CN.qm Updating '/tmp/makepkg/lxqt-panel-git/src/build/plugin-mainmenu/mainmenu_zh_CN.qm'... Generated 31 translation(s) (31 finished and 0 unfinished)...