[1.1.x] Linux: Capture always uses secondary monitor.

Bug #1704237 reported by Alex Vadeboncoeur
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SikuliX
In Progress
Medium
RaiMan

Bug Description

1.1.1(2017-03-29_10:41)/Linux3.10.0-514.26.2.el7.x86_64/Java8(64)1.8.0_131-b12

$ uname -a
Linux abcrndlni1... 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

print getNumberScreens()
print Screen(0).getBounds()
print Screen(1).getBounds()
print Screen(0).selectRegion()
print Screen(1).selectRegion()

2
java.awt.Rectangle[x=0,y=0,width=1920,height=1200]
java.awt.Rectangle[x=1920,y=0,width=1920,height=1200]

R[2279,429 313x161]@S(1) E:Y, T:3.0
R[2442,387 280x195]@S(1) E:Y, T:3.0

This was on a clean install today. Rebooting did not help. Rearranging monitors did not help. The selectRegion only used the secondary monitor for the selection.

Thank you
Alex

Revision history for this message
RaiMan (raimund-hocke) wrote :

what Linux with what windows manager?

summary: - Capture always uses secondary monitor.
+ [1.1.x] Linux: Capture always uses secondary monitor.
Changed in sikuli:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.1.2
Revision history for this message
Alex Vadeboncoeur (avadeboncoeur) wrote :

I am running gnome 3.14.0 on CentOS Linux 7 (Core)

Revision history for this message
RaiMan (raimund-hocke) wrote :

What about that?

print Screen(0).getCenter()
Screen(0).hover()
print Mouse.at()
print Screen(1).getCenter()
Screen(1).hover()
print Mouse.at()

Revision history for this message
Alex Vadeboncoeur (avadeboncoeur) wrote : Re: [Bug 1704237] Re: [1.1.x] Linux: Capture always uses secondary monitor.

As requested:

L(960,600)@S(0)[0,0 1920x1200]

L(960,600)@S(0)[0,0 1920x1200]
L(2880,600)@S(1)[1920,0 1920x1200]
L(2880,600)@S(1)[1920,0 1920x1200]

Alex

On 07/14/2017 09:06 AM, RaiMan wrote:
> What about that?
>
> print Screen(0).getCenter()
> Screen(0).hover()
> print Mouse.at()
> print Screen(1).getCenter()
> Screen(1).hover()
> print Mouse.at()
>

Revision history for this message
Alex Vadeboncoeur (avadeboncoeur) wrote :

I ran the older version 1.0.1 to use it for capturing, and it is also
now only capturing on screen 1.
I'm now suspecting a gnome / centos / hardware issue rather than a
sikuli issue.

On 07/14/2017 09:06 AM, RaiMan wrote:
> print getNumberScreens()
> print Screen(0).getBounds()
> print Screen(1).getBounds()
> print Screen(0).selectRegion()
> print Screen(1).selectRegion()

Revision history for this message
RaiMan (raimund-hocke) wrote :

Since I cannot test on Linux real machines and even not with more than one monitor, I wanted to be sure about the screen setup as Java sees it.

Now I agree with your idea about the wind manager.

There is another bug that goes into a similar direction:
https://bugs.launchpad.net/sikuli/+bug/1704302

What you now can test is, whether the problem is only with the "interactive capture" or with the screenshot feature (based on Java Robot - see other bug) as such:

print capture(Screen(0))
print capture(Screen(1))

and inspect the images, that are stored somewhere in temp

Revision history for this message
Alex Vadeboncoeur (avadeboncoeur) wrote :

That worked as it should:

/tmp/Sikulix_957080237/sikuliximage-1500048317820.png
/tmp/Sikulix_957080237/sikuliximage-1500048318663.png

20 is the left monitor and 63 is the right monitor.

Revision history for this message
RaiMan (raimund-hocke) wrote :

ok, thanks for testing.

Then the problem is with the overlay window, that is displayed to show the capture area interactively.

This seems to have problems with the graphics/GUI setup.

... but I do not have a solution for you, due to my already mentioned very restricted testing possibilities on Linux. Sorry.

RaiMan (raimund-hocke)
Changed in sikuli:
milestone: 1.1.2 → 1.1.3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.