Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot assign keybinds #3816

Closed
derekagraham78 opened this issue Sep 28, 2019 · 14 comments
Closed

Cannot assign keybinds #3816

derekagraham78 opened this issue Sep 28, 2019 · 14 comments
Labels
bug A bug (error) in the software client

Comments

@derekagraham78
Copy link

derekagraham78 commented Sep 28, 2019

I tried to assign a keybind for push to talk and no matter what keys I hit it doesn't recognize any input when I click the shortcut assign a key.
OS: Fedora Workstation 31
Desktop: GNOME
Flatpak install

@BenDrysdale
Copy link

I'm also having the same issue on MacOS Mojave and Mumble 1.3.0.

@davidebeatrici
Copy link
Member

@BenDrysdale Have you given Mumble accessibility permissions?

@froggr
Copy link

froggr commented Dec 4, 2019

I have the same issue. Mojave and mumble 1.3.0.

@froggr
Copy link

froggr commented Dec 4, 2019

On Mojave and Mumble 1.3.0, this issue occurred on first install. Im assuming accessibility perms were granted after the app started. Issue was solved for my by simply restarting the app.

@Krzmbrzl Krzmbrzl added bug A bug (error) in the software client labels Jan 15, 2020
@pferreir
Copy link

pferreir commented May 15, 2020

Same here on Fedora 31!

@Krzmbrzl
Copy link
Member

@pferreir if you start Mumble from the console, does anything related seem to show up in the logs there?

@pferreir
Copy link

This is all I get:

$ mumble          
QSocketNotifier: Can only be used with threads started with QThread
<W>2020-05-18 15:06:08.812 CELT bitstream 8000000b from /usr/lib64/mumble/libcelt0.so.0.7.0
<W>2020-05-18 15:06:08.815 Theme: "Mumble"
<W>2020-05-18 15:06:08.815 Style: "Lite"
<W>2020-05-18 15:06:08.815 --> qss: ":themes/Mumble/Lite.qss"
<W>2020-05-18 15:06:08.816 Locale is "en_US" (System: "en_US")
<W>2020-05-18 15:06:08.860 Database SQLite: "3.30.0"
<W>2020-05-18 15:06:08.862 Overlay: Listening on "/run/user/1000/MumbleOverlayPipe"
<W>2020-05-18 15:06:08.882 GlobalShortcutX: Using XI2 2.3
<W>2020-05-18 15:06:08.882 QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
<W>2020-05-18 15:06:08.981 Wayland does not support QWindow::requestActivate()
<W>2020-05-18 15:06:08.987 AudioInput: Opus encoder set for VOIP
<W>2020-05-18 15:06:08.987 AudioInput: 40000 bits/s, 48000 hz, 480 sample
<W>2020-05-18 15:06:08.987 PulseAudio: Starting input alsa_input.pci-0000_00_1f.3.analog-stereo
<W>2020-05-18 15:06:08.987 PulseAudio: Starting output: alsa_output.pci-0000_00_1f.3.analog-stereo
<W>2020-05-18 15:06:08.992 AudioOutput: Initialized 2 channel 48000 hz mixer
<W>2020-05-18 15:06:08.995 AudioInput: Initialized mixer for 1 channel 44100 hz mic and 0 channel 48000 hz echo
<W>2020-05-18 15:06:08.999 Updating application palette
warning: The VAD has been replaced by a hack pending a complete rewrite
<W>2020-05-18 15:06:43.974 OverlayConfig failed to grab desktop image, trying desktop widget...
<W>2020-05-18 15:06:43.974 QPixmap::grabWidget is deprecated, use QWidget::grab() instead

@Krzmbrzl
Copy link
Member

Wayland does not support QWindow::requestActivate()

Ah so you're using Wayland? Please have a look at #4073 and #3243 and see if that helps you :)

@pferreir
Copy link

Oh, thanks! So I take it the fix will be on 1.4? I'm using Wayland because it's the default in Fedora 31.

@Krzmbrzl
Copy link
Member

As I understood it, the fix should already be in 1.3.0 but you'll have to use DBus to send the PTT events to mumble. See #3675

@moedn
Copy link

moedn commented Jul 1, 2020

Same issue here on

  • Fedora 32 (Workstation),
  • dnf install (as suggested in the wiki);
  • mumble version 1.3.0

I found the Mumble.config in ~/.config/Mumble with the section [shortcuts] in line 30.

Anyone knows if and how one can define shortcuts there? → would be a great workaround :)


It worked for me on Fedora 31 a few days ago (I did the upgrade yesterday night). There may be a conflicting package in F31 and F32 as it is not working for @derekagraham78 as well

@Krzmbrzl
Copy link
Member

Krzmbrzl commented Jul 2, 2020

Anyone knows if and how one can define shortcuts there? → would be a great workaround :)

It should be possible but the format is more or less binary-ish, so I guess it's not easy. Additionally the shortcuts are platform dependent so you can't really copy it from elsewhere.

Furthermore you probably can't assign shortcuts, because the global shortcut engine is not working on your system (for some reason). That means that even if you were able to set the shortcuts via the settings, you wouldn't be able to trigger them.

@TheNyneR
Copy link

TheNyneR commented Sep 5, 2021

I'm having the same issue on Gentoo with Sway.
When creating a bindI can assign the function but not the input keys to the bind itself.

@Krzmbrzl
Copy link
Member

Krzmbrzl commented Sep 7, 2021

Closing this issue in favor of #5257

@Krzmbrzl Krzmbrzl closed this as completed Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug (error) in the software client
Projects
None yet
Development

No branches or pull requests

8 participants