PTT and Dual Head (Separated X screen)

[rafaeljpc]

Hi,

I am quite new at mumble, so I don't if I've done something wrong.

I have 2 video cards, and 1 monitor on each board, I configured to use dual head with separated x screen (Linux version is Ubuntu 10.04).

The problem is, I like to use the chat programs on the screen that I'm not playing and when I move the mouse to the display that I am playing PTT button stop working.

Then when I move the mouse to the display that I openned Mumble it works fine again.

Sorry to bother, and thanks for the help

[rawnar]

Are any of the keyboard or mouse input transferred to the other display? Because I think that the x-servers are not communication with each other. So a signal send on one display is not passed to the other display. I don't know if there is a setting in the xorg.conf to help you. You can always try to setup xinerama or RandR for your dual-head, but maybe you don't want that.

Another option could be that mumble will also start to listen to the other x-server for inputs from the keyboard or mouse. But I don't know if that is implemented or even possible.

[rafaeljpc]

I tried to find something on xorg.conf, but it was in vain.

I can put my xorg.conf here, but first I think it is important to say that some programs, like Mangler (a ventrilo client for linux, that I'm using until my guild decide to change the platform) works fine.

Looking at the Mumble's source, I found where the signal is captured.

...
if (XQueryPointer(display, root, &root_ret, &child_ret, &root_x, &root_y, &win_x, &win_y, &mask[next]) && XQueryKeymap(display, keys[next])) {
...
}
...

 

At Mangler that they use the following line of code:

 

GdkWindow   *rootwin = gdk_get_default_root_window();
...
XQueryKeymap(GDK_WINDOW_XDISPLAY(rootwin), pressed_keys);

 

I looks like that XQueryKeymap of mumble just get the signal of the display that I oppened the Mumble and not from the active window (which is where the pointer is), and Mangler get it from the display of the current rootwin.

A Solution is to update the display variable every time befor call XQueryKeymap.

I'll try to modify and build mumble here then I'll send a patch, if you like.

Thanks for the help

[rawnar]

Just file a bug here and provide the information you just have found. Probably they can still fix it before the next stable release.

[rafaeljpc]

Hi... it's me again.

Well I'm trying to solve this bug, as I have the envirorment for that and want to learn more about Qt programing and the mumble itselft.

But when I did some traces I saw that are two ways that mumble listen the key/button events from X.

1 - When XInput2 is unavailable and a thread is openned that check the modifications at the keymap. (and works fine with 2 screens, I tested)

2 - Using XInput2, which is cleaner and, according to the every source I found, more efficient.

The problem is, when using xinput2 I looks like that the events generated at the screen :0.1 is not passed to the screen :0.0 (where mumble is openned).

I looked at the xfree86.org documentation and I couldn't find a way to link all screens events.

It's strange, by the way, because at one of the structures of XInput2 (the XKeyEvent or XButtonEvent) has a property called same_screen. :shock:

As I waste about 8 hours knocking my head at the keyboard ( :D :oops: ), I decided to call for help.

Did someone know why this problem is happening, and why all screens key events couldn't be passed to mumble.

PS: I Tryed to force the display connection inside the program and it workig perfectly.

[rawnar]

You could provide a patch of your solutions to the tracker. I mean the force display connection inside the program, as long as it does not break the program for other users.

For the XInput2 problem I do not have a answer yet. But on freedesktop.org they have the complete protocol explained, maybe it can help you.

[rafaeljpc]

I'm think on 2 solutions, both are not so good.

1 - Implement a parameter that jump the normal XInput2 part and run as it was not working.

2 - Open more connection, one for each screen, and link de devices and so on.

The first is easy, the second is more cool, but I was wondering if there is any problem with opening more displays.