search

philou76 / linux-track

Automatically exported from code.google.com/p/linux-track
0 stars 0 forks source link

Mickey does not work on multiple screens #79

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install linux-track with mickey
2. Attach & configure a second screen

What is the expected output? What do you see instead?
Expected was the ability to use mickey on all screens, instead the cursor stops 
at the border of the primary screen and does not move further (only jitters).

What version of the product are you using? On what operating system?

linux-track revision 894, built from SVN trunk.
Arch Linux x64, 3.17, DE/WM: xfce4

Please provide any additional information below.

I guess mickey does only take the primary screen size into accordance. If I can 
be of help with debugging, please let me know.

Original issue reported on code.google.com by puck...@gmail.com on 28 Nov 2014 at 7:56

GoogleCodeExporter commented 8 years ago 
Forgot to mention: It works in relative mode, but not in absolute mode of 
mickey (which I would prefer since head movements feel unnatural for relative 
mode).

Original comment by puck...@gmail.com on 28 Nov 2014 at 9:12

GoogleCodeExporter commented 8 years ago 
Hello,
as much as I hate this sentence, I can't reproduce this problem.
That is on Ubuntu 14.04, XFCE and both modes work as expected. Can you provide 
me more info on your setup? (do you have a desktop spaning both screens, or is 
each screen a different X display?)

Also are you using the universal package, or do you build it yourself?

Kind regards,

Michal

Original comment by f.jo...@email.cz on 29 Nov 2014 at 10:55

GoogleCodeExporter commented 8 years ago 
Hello Michal,

no Problem. I am glad if I can help you reproduce this problem.
I am using a Intel HD 4000 integrated graphics and do have one desktop over 
both screens configured like this: https://clbin.com/0ln1m

As for the package, I am building from SVN source revision 894 and have the 
packaging done by routines from the Arch Linux User Repository (short AUR).
You can see my PKGBUILD (build script) here: https://clbin.com/wy7zC

Many thanks & Kind regards,
Fabian

Original comment by puck...@gmail.com on 1 Dec 2014 at 5:15

GoogleCodeExporter commented 8 years ago 
Hello Fabian,
I did some more tests, but I still can't reproduce the problem...
I'm going to try and setup the xorg.conf like yours and see if that helps to 
break it.

In the meantime, could you post here what 'randr --current' writes out?

And when you run mickey, can you find its PID (using 'ps uxw') and check in the 
/proc/PID/maps to see if there is libXrandr mentioned anywhere?

Kind regards,

Michal

Original comment by f.jo...@email.cz on 1 Dec 2014 at 9:12

GoogleCodeExporter commented 8 years ago 
Hello Michal,

Sorry to hear you have problems reproducing.
I guess the problem has to do with Mickey not taking the VirtualScreen into 
account, but I maybe wrong on this part.

Output of xrandr --current:
[fabian@ArchLinux ~]$ xrandr --current
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
HDMI1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm 
x 336mm
   2560x1440     54.93*+
   1920x1080     60.00 +  60.00    50.00    50.00    59.94  
   1920x1080i    60.00    50.00    59.94  
   1600x1200     60.00  
   1680x1050     59.88  
   1280x1024     75.02    60.02  
   1440x900      59.90  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1440x576i     50.00  
   1024x768      75.08    60.00  
   1440x480i     60.00    59.94  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       75.00    60.00    59.94  
   720x400       70.08  
HDMI2 disconnected (normal left inverted right x axis y axis)
VGA1 connected 1280x1024+2560+184 (normal left inverted right x axis y axis) 
376mm x 301mm
   2560x1440     54.93 +
   1280x1024     60.02*+  76.00    75.02    72.05  
   1152x864      75.00  
   1024x768      75.08    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32  
   640x480       75.00    72.81    66.67    60.00  
   720x400       70.08  
   640x350       70.07  
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

You can see mickeys /proc/PID/maps here: https://clbin.com/68vRM
However, there are multiple instances of libXrandr in there:
7fa160f1f000-7fa160f28000 r-xp 00000000 fe:04 3690816                    
/usr/lib/libXrandr.so.2.2.0
7fa160f28000-7fa161127000 ---p 00009000 fe:04 3690816                    
/usr/lib/libXrandr.so.2.2.0
7fa161127000-7fa161128000 r--p 00008000 fe:04 3690816                    
/usr/lib/libXrandr.so.2.2.0
7fa161128000-7fa161129000 rw-p 00009000 fe:04 3690816                    
/usr/lib/libXrandr.so.2.2.0

Hope I could help.

Kind regards,
Fabian

Original comment by puck...@gmail.com on 3 Dec 2014 at 12:24

GoogleCodeExporter commented 8 years ago 
Hello,
the thing is, that I already had an issue reported with mickey not working on 
dualscreen, however it was resolved by a change in code and it worked for the 
guy reporting it and for me too... Mickey doesn't handle that directly, it asks 
Qt for the information and so far it reported the right thing...

From the listings you posted it seems that randr knows what is going on and the 
Qt does load it, so it should be aware of the full desktop resolution...

I'll try few more things and if nothing helps, I'll try to setup and Arch 
partition to see if that helps in reproducing the problem... But I'm afraid I 
won't be able to do that sooner than next weekend.

Kind regards,

Michal

Original comment by f.jo...@email.cz on 3 Dec 2014 at 6:26

GoogleCodeExporter commented 8 years ago 
I did few more tests (I'm not able to get the desired configuration playing 
with xorg.conf; fortunately xrandr works), but I didn't encounter any problems 
with mickey. I tried both screens the same resolution, different resolutions, 
smaller to the left or right, positioning the smaller to nonzero y (that one 
looked the most suspicious).

One more thing that might be interesting to try - you wrote that the cursor 
stays only on the primary screen... What happens, if you start mickey, drag its 
window to the secondary screen, close it down and start it again (so it opens 
up on the secondary screen)?

Right now, I'm afraid right now it seems that the issue is somehow Arch 
specific; as soon as I have some more free time (probably next weekend, but I 
can't promise), I'll try to set it up and see if I can make it fool mickey...

Kind regards,

Michal

Original comment by f.jo...@email.cz on 3 Dec 2014 at 8:31

GoogleCodeExporter commented 8 years ago 
Hello,

thanks for your effort. I did not see the previous bug before.
I suppose it could be due to some (more or less recent) upstream code change - 
it can happen to a rolling-release distro from time to time. Arch is quite 
different from Ubuntu when it comes to package currentness.

I tried your suggestion to start up mickey on my secondary screen and the 
cursor did one giant leap to the left (being out of control for a moment) 
before returning to the described behaviour. So it seems it is not dependent on 
the screen it is started up on.

If I can be of any help with setting up Arch or further testing, don't hesitate 
to mail me.

Kind regards,
Fabian

Original comment by puck...@gmail.com on 6 Dec 2014 at 12:15

GoogleCodeExporter commented 8 years ago 
Hello,
I finally managed to try it out on Arch, but I was not able to reproduce what 
you see - I set the big virtual desktop, I have XFCE4 installed, using your 
PKGBUILD...

The only thing that comes to mind - when you run mickey, what version number do 
you see in its caption?

Kind regards,

Michal

Original comment by f.jo...@email.cz on 13 Dec 2014 at 11:48

GoogleCodeExporter commented 8 years ago 
Hello,

sorry for the delay. I was on holiday, away from a proper internet connection 
for a while. I really appreciate your great effort in reproducing my issue.

I wonder what the difference may be that triggers the issue for me, but not for 
you. I am using integrated Intel HD4000 graphics for both monitors.

If I run mickey it shows "v0.99.12" in its window caption. As I understand, I 
should be building and using the latest SVN r894.

Kind regards,
Fabian

Original comment by puck...@gmail.com on 4 Jan 2015 at 2:47

GoogleCodeExporter commented 8 years ago 
Hello,

No problem, my children kept me occupied ;) 

If the time permits, on the weekend I can try to play with it a bit more - 
maybe I'll be able to find something out...

I'll keep you posted,

Michal

Original comment by f.jo...@email.cz on 7 Jan 2015 at 6:28