Hu.

Somewhere the list must have fallen of the e-mail-train. Putting the
list back on. Sorry!

Regards
  Andre

On 02.09.2014 14:18, David Sorkovsky wrote:
>
> Hi Andre,
>
> When I was playing with it I added a keyboard command something like the
> following (can't remember exact syntax for sure) ...
>
>               awful.key({ modkey,           }, "i",
>       
> function (c)
>       
> naughty.notify({ text=screen })
>       
> end),

Hi again.

I tried this:

awful.key({ modkey, "Shift"   }, "i", function ()
naughty.notify({text=mouse.screen}) end),

and it worked as expected. I.e. it shows the correct  screen the mouse
is currently on as a number in the top right of my primary screen.


However, I looked a little bit deeper into the issue. Correct me if I am
wrong, but for the "start-terminal" (and probably all others) case the
final function called is spawn(...) in the file spawn.c!?

If this is the case, then awesome must be doing some unusual stuff.

I wrote the attached very simple test program.
Compilable with

gcc spawner.c -o spawner $(pkg-config --cflags --libs glib-2.0)

This program opens a terminal on the screen the mouse is currently on
(it does this so by itself by calling g_spawn_async, no thanks to me) in
the same way (I think!) as awesome does.

This works for fluxbox, gnome, kde and xfce on all my three screens.
in awesome it works on the center and the left screen but not on the
right screen. I infer from this, that the problem has nothing (or
something very weird) to do with my setup.

I don't know what to do without diving into the code of glib, which I'd
like to avoid.

Any ideas?

Regards
  Andre

>
>
> -----Original Message-----
> From: Andre Naujoks [mailto:[email protected]]
> Sent: Tuesday, 2 September 2014 9:51 PM
> To: David Sorkovsky
> Subject: Re: Windows opening on wrong screen
>
> On 02.09.2014 11:07, David Sorkovsky wrote:
>>
>> I think this is what you'd use, but I'm not sure how the different 'Y'
>> resolutions will work. Note: This is my entire xorg.conf - None of the
>> other stuff seems to be necessary
>>
>
> I gave that config a shot. I had to replace the "LeftOf" and "RightOf"
> options with absolute "Position" options and readded my mouse settings.
>
> The config works (and I will keep using it, thanks!), but the issue on the
> right screen persists.
>
> I will try and debug this tonight. I don't see very big chances of me
> finding something, but I'll give it a shot.
>
> Any hints on where to start looking would be greatly appreciated. The
first
> thing for me would be to check if the functions, which determine the
current
> screen behave correctly.
>
> Regards
>   Andre
>
>>
>> Section "Monitor"
>>      Identifier   "DisplayPort-0"
>>      VendorName   "DEL"
>>      ModelName    "DELL U2711"
>>      Option          "PreferredMode" "2560x1440"
>>      Option          "LeftOf" "HDMI-0"
>> EndSection
>>
>> Section "Monitor"
>>      Identifier  "HDMI-0"
>>      VendorName  "GSM"
>>      ModelName   "W2452"
>>      Option          "PreferredMode" "1920x1200"
>>      Option          "LeftOf" "DVI-0"
>> EndSection
>>
>> Section "Monitor"
>>      Identifier  "DVI-0"
>>      VendorName  "PHL"
>>      ModelName   "Philips 241SL"
>>      Option          "PreferredMode" "1920x1080"
>>      Option          "RightOf" "HDMI-0"
>> EndSection
>>
>> Section "Device"
>>      Identifier  "Card0"
>>      Driver      "radeon"
>> EndSection
>>
>> Section "Screen"
>>      Identifier              "Screen"
>>      Device                  "Card0"
>>      Monitor                 "DisplayPort-0"
>>      DefaultDepth     24
>>       SubSection "Display"
>>              Viewport        0 0
>>              Depth           24
>>              Modes           "2560x1440" "1920x1200" "1920x1080"
>>              Virtual         6400 1440
>>      EndSubSection
>> EndSection
>>
>> -----Original Message-----
>> From: Andre Naujoks [mailto:[email protected]]
>> Sent: Tuesday, 2 September 2014 5:18 PM
>> To: David Palacio; [email protected]
>> Subject: Re: Windows opening on wrong screen
>>
>> On 02.09.2014 03:23, David Palacio wrote:
>>> El Lun 01 Sep 2014 11:15:36 Andre Naujoks escribió:
>>>> Hi.
>>>>
>>>> I am just giving awesome a try and like it so far. I am on a debian
>>>> sid with awesome version 3.4.15-1+b1.
>>>>
>>>> It has one quirk, where I think it is a bug.
>>>>
>>>> When I open a window (say a terminal with Mod4 + Return, but the
>>>> application does not matter.), the window should apear on the
>>>> current active screen. This works for two of my three screens, but
>>>> not for the third. The same happens when I open a window via the
>>>> right-mouse-click menu from the desktop, or when I use the top left
>>>> button to bring up the menu.
>>>>
>>>> - I select the screen by either moving the mouse into it, or
>> Mod4+Ctrl+j/k.
>>>> - I start an application on my right-most screen and the window
>>>> opens on my primary/center screen.
>>>>
>>>> I attached a screenshot of my layout, so you get an idea of what I
>>>> am talking about. (the black stripes above the left and right screen
>>>> are unused, i.e. the monitors end where the menu-bar is)
>>>>
>>>> As mentioned it works for the left and the center screen, but not
>>>> for the right one.
>>>>
>>>> Am I doing something wrong or is this a bug? I am not familiar
>>>> enough with lua or window managers at all to try my hand at this,
>>>> but I can test and try patches.
>>>>
>>>> Regards
>>>>   Andre
>>> Hi Andre,
>>>
>>> As you mention three screens I suspect you may be using two separated
>>> GPUs at the same time in the same X screen. That is not well
>>> supported in
>> Awesome 3.4.
>>> I used to use three screens on a PC with a NVidia and integrated
>>> Intel GPUs and ran into many problems with it. To improve my setup I
>>> made some modifications to Awesome. You can check and compile it at:
>>>
>>>     https://github.com/dpalacio/awesome-randr-zaphod
>>>
>>> It works in Zaphod mode and with video drivers that support RandR
>> extension.
>>> It does not support Xinerama.
>>>
>>
>> Hi David,
>>
>> Hm. I am not using two GPUs. Just one Radeon HD 6870 with four
>> outputs, of which three are used. My other E-Mail in reply to Elv1313
>> contains my xorg.conf and an xrandr output. Maybe there is something
>> borked there, but I didn't have such problems before.
>>
>> Regards
>>   Andre
>>
>> --
>> To unsubscribe, send mail to [email protected].
>>
>
>



spawner.c

#include <glib.h>
#include <unistd.h>

static void
spawn_callback(gpointer user_data)
{
    setsid();
}

int main()
{
        char *argv[2];
        GPid pid;
        GError *error = NULL;
        argv[0] = "x-terminal-emulator";
        argv[1] = NULL;

        g_spawn_async(NULL, argv, NULL, G_SPAWN_SEARCH_PATH, spawn_callback,
NULL, &pid, &error);

        sleep(1);
        return 0;
}


#include <glib.h>
#include <unistd.h>

static void
spawn_callback(gpointer user_data)
{
    setsid();
}

int main()
{
	char *argv[2];
	GPid pid;
	GError *error = NULL;
	argv[0] = "x-terminal-emulator";
	argv[1] = NULL;

	g_spawn_async(NULL, argv, NULL, G_SPAWN_SEARCH_PATH, spawn_callback, NULL, &pid, &error);

	sleep(1);
	return 0;
}

Reply via email to