THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
Use it for a few days and keep an eye on system memory usage. I noticed
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Jiachen Yang (farseerfc)
--
I have checked the latest version of zaphod-mode-support, and it worked great!
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Jiachen Yang (farseerfc)
--
Some thing I found strange is that, when dragging a window by mouse (both left
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
Ok, with that patch it fixes Ctrl+Mod4+j/k, and now the mouse gets
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
Oh here's a weird one... If I do Ctrl+Mod4+j/k it cycles focus between
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
When i add that to rc.lua, it warps the mouse to that point on the same
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
That one didn't fix it. :/
--
More information can be found at
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
Yep, that fixed it. Starting programs with key binds and from the Run:
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
If I do Mod4+Enter to get a terminal, it always shows up on the upper-left
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Jiachen Yang (farseerfc)
--
I am checking on this thread and willing to test on my 4 heads setup.
I am using
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
Yes, some other branch. And no, it should work without starting two instances.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
Odd, I never got that e-mail, but i did get the ones from this bug
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
Well, it runs, and lights up on all 3 displays, but there's still
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
I forgot to mention, this was all using the default rc.lua that came
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - David Olsen (lude)
--
I'm also bitten by this bug and willing to test.
--
More information can be
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
How tricky would it be to put the 3.4 hack back in?
Meh, this question got me
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
I get e-mail notifications for this and have a box with 3 Zaphod
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Joel Crisp (cydergoth)
--
Would it be possible to get a status update or version ETA on this fix? Awesome
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
Status: Doesn't work
ETA: When someone shows up and does the work
Also, please
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Joel Crisp (cydergoth)
--
Thanks for the update. Unfortunately as various other people and I have pointed
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
Most of that make the C code less ugly happened in August 2010 (wow, it's
been
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Joel Crisp (cydergoth)
--
Is it possible to get one instance of Awesome running across :0.1, :0.2 :0.3?
I
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
So known issues: Input focus needs to be handled better, keyboard combinations
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Romain D. (Artefact2)
--
Same problem is also happening for me. I have to use zaphod mode because I have
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Julien Danjou (jd)
--
What's the problem with running several awesome instances?
--
More
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
Wow, Xephyr can do zaphod mode: Xephyr -screen 800x600 -screen 800x600 :1
So
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
I just switched back to 3.5 to test some of this on the real X server.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Julien Danjou (jd)
--
There might be some bug, indeed, there's no reason that things get launched on
0.0.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
Added? This is a feature that existed in awesome 3.4 and worked
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
Ignore my tag problem, it was a stale rc.lua which only created a single tag.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Julien Danjou (jd)
--
This could be fixed by checking the mouse position. This problem is only likely
to
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Paul Ignatenko (ignatp)
--
I'm currently running on Catalyst 11.12 -- I have a 6950 with all 3 monitors
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Paul Ignatenko (ignatp)
--
My example working xorg.conf on Arch.
http://pastebin.com/Y6BjxeWW
--
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Abort Retry Fail (abortretryfail)
--
Zaphod mode is the *only* way to have multiple displays across
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - John Doe (johndoe)
--
Oh its in the queue for 3.5.1?! Thank you so much and happy new year! ;)
--
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - John Doe (johndoe)
--
well:
- i got a small monitor at far right of my desk and a big widescreen at the far
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - John Doe (johndoe)
Attached to Project - awesome
Summary - awesome = 3.5 does only recognize 1 screen with xinerama off
Task Type - Bug Report
Category - Core
Status -
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - John Doe (johndoe)
--
Sorry for the missing description. Didnt know how to report the bug and clicked
too
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Till Matthiesen (entropy)
--
3.5 just hit Arch stable and I can confirm this
behaviour running two screens
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Uli Schlachter (psychon)
--
This was not by accident. This was me removing something which I can't test,
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Till Matthiesen (entropy)
--
Hi Uli,
'one' reason simply is that there are a still certain graphics
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1069 - awesome = 3.5 does only recognize 1 screen with xinerama off
User who did this - Till Matthiesen (entropy)
--
Well, the 'reason' I gave is invalid and only applies to the maximum texture
42 matches
Mail list logo
