Linux Questions

2260 readers

14 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 2 years ago

MODERATORS

possiblylinux127@lemmy.zip

Help using KDE Connect + Display Configuration Switcher (lemmy.dbzer0.com)

submitted 1 day ago by riquisimo@lemmy.dbzer0.com to c/linuxquestions@lemmy.zip

12 comments fedilink hide all child comments

Ok, first off KDE Connect is a killer app. It's so slick and convenient. Love it.

My desktop is running Fedora 42 Workstation with Gnome. Since I've got GNOME instead of KDE, I'm using an extension called GSConnect to communicate with KDE connect on my phone. It's working perfectly.

I've also got this extension called "Display Configuration Switcher" that lets me use a keyboard shortcut ( ctrl + ; ) to switch between two display configs:

Standard desktop layout
TV only.

(Fedora 42 is using Wayland, when I was on X11 I could use ARandR to create custom commands but Wayland is... more complicated.)

I want to add a command to KDE Connect/GSConnect to switch my display configuration from "desktop" output to "TV" output. The problem is I don't know what command to invoke to trigger "Display Configuration Switcher" to swap configurations.

There are multiple ways to approach this. The best solution is just to figure out what command is invoked when I press the keyboard shortcut "ctrl + ;", which is the shortcut to switch display configs. I'm not sure how to see what command is run when I press a button or shortcut.

Alternatively, I could find a way to send the ctrl + ; shortcut from the KDE connect app. Sending keyboard shortcuts would be handy regardless, but this is a workaround.

Any help would be appreciated. Thank you in advance!

you are viewing a single comment's thread
view the rest of the comments

[–] riquisimo@lemmy.dbzer0.com 1 points 6 hours ago (1 children)

Ok, wtype looks really promising but I'm having issues building it. I cloned it, installed meson, and when I try "meson build" I get this error:

meson.build:1:0: ERROR: Unknown compiler(s): [['cc'], ['gcc'], ['clang'], ['nvc'], ['pgcc'], ['icc'], ['icx']]
The following exception(s) were encountered:
Running `cc --version` gave "[Errno 2] No such file or directory: 'cc'"
Running `gcc --version` gave "[Errno 2] No such file or directory: 'gcc'"
Running `clang --version` gave "[Errno 2] No such file or directory: 'clang'"
Running `nvc --version` gave "[Errno 2] No such file or directory: 'nvc'"
Running `pgcc --version` gave "[Errno 2] No such file or directory: 'pgcc'"
Running `icc --version` gave "[Errno 2] No such file or directory: 'icc'"
Running `icx --version` gave "[Errno 2] No such file or directory: 'icx'"

And I can't figure out what I need to install to fix that. It looks like on debian based systems there's a "build-essentials" package, but when I "sudo dnf search build-essential" I get nothing. I'll keep searching but if you have any tips please let me know.

[–] riquisimo@lemmy.dbzer0.com 1 points 4 hours ago

Ok, so following the MesonBuild website, I needed to install a compiler toolchain:

sudo dnf install gcc-c++

Then I was still missing some dependencies, so I also dnf installed "cmake," "rust-wayland-client+default-devel," and "rust-xkbcommon+wayland-devel"

And now it builds and I was able to install! However, it doesn't work. I get an error "Compositor does not support the virtual keyboard protocol," which, looking at the issues on github, seems to be a known issue with Fedora and other GNOME desktops.

So wtype is out. I'll try ydotool next!