GlobalShortcut_unix: evdev mode should not fall back to XInput2 when no keyboard device nodes area available

[mkrautz]

Via #3243 (comment)

Evdev mode should not fall back to XInput2 when no keyboard device nodes are available:

However, there is a bit of a misbehavior right now, where Mumble will fall back to XInput2 when no keyboards can be opened via evdev. This behavior is from back when evdev was our default.
Now, it makes more sense for Mumble to keep using evdev if it is enabled, and warn the user if no keyboard device nodes are available.

Instead, we should just warn the user, and keep on chugging along, allowing users to use evdev mode to allow global shortcuts for mice, for example.

[mkrautz]

Perhaps we should warn for each of

• Keyboard
• Mouse
• Joystick

...?

[the-sane]

Yes, since the user has to specifically enable evdev, mumble should assume they know what they're doing and not prevent them from doing it.

In my case, this prevents me from assigning PTT to a joystick button because mumble falls back to XInput.
I assume there's no way for me to force evdev until this is resolved?

[Krzmbrzl]

I assume there's no way for me to force evdev until this is resolved?

I don't think so 🤔
@davidebeatrici might know more though

[davidebeatrici]

I confirm that unfortunately there is no way to force evdev:

mumble/src/mumble/GlobalShortcut_unix.cpp

Lines 67 to 86 in 919f1f7

	#ifdef Q_OS_LINUX
	if (g.s.bEnableEvdev) {
	QString dir = QLatin1String("/dev/input");
	QFileSystemWatcher *fsw = new QFileSystemWatcher(QStringList(dir), this);
	connect(fsw, SIGNAL(directoryChanged(const QString &)), this, SLOT(directoryChanged(const QString &)));
	directoryChanged(dir);
	if (qsKeyboards.isEmpty()) {
	foreach (QFile *f, qmInputDevices)
	delete f;
	qmInputDevices.clear();
	delete fsw;
	qWarning(
	"GlobalShortcutX: Unable to open any keyboard input devices under /dev/input, falling back to XInput");
	} else {
	return;
	}
	}
	#endif

I will take care of it.