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 awesome-unsubscr...@naquadah.org.
RE: Windows opening on wrong screen
Hi Andre, I also had a lot of trouble getting my system just right. I did lots of playing with xorg.conf and with two screens from the built in graphics controller of my CPU and this is my final config (two monitors but just one screen)... Section Monitor Identifier HDMI1 VendorName Samsung ModelName ? Option PreferredMode 1920x1080 Option RightOf HDMI2 EndSection Section Monitor Identifier HDMI2 VendorName BenQ ModelName ? Option PreferredMode 1920x1080 Option LeftOf HDMI1 EndSection Section Device Identifier MotherboardVideo Driver intel VendorName Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) EndSection Section Screen Identifier Screen Device MotherboardVideo Monitor HDMI2 DefaultDepth24 SubSection Display Viewport0 0 Depth 24 Modes 1920x1080 1920x1080 Virtual 3840 1080 EndSubSection EndSection I got the identifiers from the xrandr info, so looking at yours, you'd probably have DisplayPort-0, HDMI-0 and DVI-0 where I have HDMI1 and HDMI2 Nice things was no Xinerama which seems to be the preferred way! -Original Message- From: Andre Naujoks [mailto:nauts...@gmail.com] Sent: Tuesday, 2 September 2014 5:18 PM To: David Palacio; awesome@naquadah.org 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 awesome-unsubscr...@naquadah.org. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Windows opening on wrong screen
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:nauts...@gmail.com]
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
ModelNameDELL 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
Viewport0 0
Depth 24
Modes 2560x1440 1920x1200 1920x1080
Virtual 6400 1440
EndSubSection
EndSection
-Original Message-
From: Andre Naujoks [mailto:nauts...@gmail.com]
Sent: Tuesday, 2 September 2014 5:18 PM
To: David Palacio; awesome@naquadah.org
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
Re: Windows opening on wrong screen
Maybe one if the XCB request move it somewhere else. I am not sure
of that as I can't reproduce the issue (I have 5 screens, but with
Xineramma). You can try with Tyrannical (
https://github.com/Elv13/tyrannical ) as it disable some of those, I
am not sure. You can use the sample rc.lua to test using the Awesome
-c option. Some of the x property request are handled in strange
way. It may be while you have this bug. Without further debugging, I
can't tell. Tyrannical try to turn off some of those size/tag/position
request and replace them with its own, this is why there is a slim
chance it will bypass the bug.
On 2 September 2014 18:54, Andre Naujoks nauts...@gmail.com wrote:
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:nauts...@gmail.com]
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
ModelNameDELL 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
Viewport0 0
Depth 24
Modes 2560x1440 1920x1200 1920x1080
Virtual 6400 1440
EndSubSection
EndSection
-Original Message-
From: Andre Naujoks [mailto:nauts...@gmail.com]
Sent: Tuesday, 2 September 2014 5:18 PM
To: David Palacio; awesome@naquadah.org
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,
[awesome bugs] #1252 - Use a single icon for maximized (both vertical and horizontal)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1252 - Use a single icon for maximized (both vertical and horizontal) User who did this - Daniel Hahler (blueyed) -- I have now used ⨣ (http://codepoints.net/U+2A23). This might add a bit of confusion, because a + icon gets used in the taskbar to make a client sticky, while a square (▪) is used to indicate sticky clients in the tasklist. The PR is at https://github.com/awesomeWM/awesome/pull/44 A better codepoint might be found when searching for cross: http://codepoints.net/search?q=na=cross -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1252#comment4125 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1252 - Use a single icon for maximized (both vertical and horizontal)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1252 - Use a single icon for maximized (both vertical and horizontal)
User who did this - Daniel Hahler (blueyed)
--
This looks better: http://codepoints.net/U+1F542 (I've amended the PR).
(when submitting the comment with the symbol in it, flyspray crashed: Query
{INSERT INTO `flyspray_comments` (task_id, date_added, last_edited_time,
user_id, comment_text) VALUES ( ?, ?, ?, ?, ? )} with params
{1252,1409689584,1409689584,494,This looks better: [THEUNICODECHAR]
http://codepoints.net/U+1F542 (I've amended the PR).} Failed! (Incorrect string
value: '\xF0\x9F\x95\x82 h...' for column 'comment_text' at row 1))
--
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1252#comment4126
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
