can't install linuxtrack size missmatch error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use new key 
2.add repositories (copied from ubuntu instructions)
3.refresh synaptic and try to install linuxtrack and linuxtrack-dev with all 
dependantcies
4. i get an error

What is the expected output? What do you see instead?
expected to install linuxtrack, i see this error when downloading

W: Failed to fetch 
http://www.linuxtrack.eu/repositories/ubuntu/pool/main/l/linuxtrack/liblinuxtrac
k0_0.0~svn120511-precise1_amd64.deb
  Size mismatch

W: Failed to fetch 
http://www.linuxtrack.eu/repositories/ubuntu/pool/main/l/linuxtrack/linuxtrack-d
ata_0.0~svn120511-precise1_all.deb
  Size mismatch

W: Failed to fetch 
http://www.linuxtrack.eu/repositories/ubuntu/pool/main/l/linuxtrack/linuxtrack-g
ui_0.0~svn120511-precise1_amd64.deb
  Size mismatch

W: Failed to fetch 
http://www.linuxtrack.eu/repositories/ubuntu/pool/main/l/linuxtrack/linuxtrack_0
.0~svn120511-precise1_all.deb
  Size mismatch

What version of the product are you using? On what operating system?
latest version of linuxtrack, and ubuntu 12.04.1

Please provide any additional information below.
it's on a lenovo thinkpad w701

Original issue reported on code.google.com by billstre...@gmail.com on 18 Oct 2012 at 3:30

[GoogleCodeExporter]

Hello Bill,
looking into the logs, for some reason there is a problem reading from and 
writing to the device...

That is strange, since there should be no problem - the device is opened, 
captured, and so on...  Can you please try the command

LIBUSB_DEBUG=3 /opt/linuxtrack/bin/ltr_gui

Hopefully it will log more informations concerning the actual problem...
After that, could you send me these logs again, so I can take a peek?

One more thing - can you tell me, if the command

lsusb -v -d 131d:0106

produce a warning like "libusbx: error [op_open] libusbx couldn't open USB 
device /dev/bus/usb/002/003: Permission denied.
libusbx: error [op_open] libusbx requires write access to USB device nodes.
Couldn't open device, some information will be missing"

Thank you,

Michal

Original comment by f.jo...@email.cz on 23 Nov 2012 at 8:34

[GoogleCodeExporter]

no error with the lsusb command, here is the log, same name as last

Original comment by billstre...@gmail.com on 23 Nov 2012 at 9:07

Attachments:

• logs.tar.gz

[GoogleCodeExporter]

Hello Bill,
there were some more detailed errors in the log, which indicate error "no such 
file or directory"...
I'm on track now I think - I was communicating through bad endpoint numbers...
I'll send you a new package as soon as I have it corrected.
Kind regards,

Michal

Original comment by f.jo...@email.cz on 23 Nov 2012 at 9:46

[GoogleCodeExporter]

ok, thanks

Original comment by billstre...@gmail.com on 23 Nov 2012 at 9:50

[GoogleCodeExporter]

Hello Bill,
here is the new package - just replace the contents of /opt/linuxtrack with 
contents of this package and try the ltr_gui again...
Hopefully now it is going to work...
Thank you for your patience,

Michal

Original comment by f.jo...@email.cz on 23 Nov 2012 at 11:36

Attachments:

• linuxtrack121123.zip

[GoogleCodeExporter]

That worked

Original comment by billstre...@gmail.com on 24 Nov 2012 at 12:15

[GoogleCodeExporter]

That is a great news!
I'm heading to bed now, I'll let you know as soon as I have the mouse mover 
ready...
Thank you for your help,

Michal

Original comment by f.jo...@email.cz on 24 Nov 2012 at 12:24

[GoogleCodeExporter]

ok

Original comment by billstre...@gmail.com on 24 Nov 2012 at 12:32

[GoogleCodeExporter]

Hello Bill,
just to let you know about the progress...
I have a way to detect a press of a key regardless the current focus - so I'll 
be able to start/stop the tracking.

I also have a way to emulate mouse - moving and clicking...

So now it should be mostly question of putting it all together...
Will keep you posted.
Kind regards,

Michal

Original comment by f.jo...@email.cz on 25 Nov 2012 at 10:17

[GoogleCodeExporter]

COOL!

Original comment by billstre...@gmail.com on 26 Nov 2012 at 3:28

[GoogleCodeExporter]

Hello Bill,
in order to speed things up, I'd like to ask you a few questions...
The thing is, that I can feel the featuritis comming up (very bad disease, that 
many programmers suffer, making them cluttering their programs with loads of 
useless features ;) )...

So, in order simplify some things a bit, I'd like to ask you this:

 - which key to use to toggle tracking on/off?
 - which key to use to center tracking?
 - which key to use to toggle precision mode?
 - do you use absolute (moving head controlls directly the cursor) or relative mode (moving head controls cursor speed - like touch point)?
 - would it be ok to do the centering in such a way, that you press the key, and it waits until a button is pressed (S/P switch) to record the center position?
 - are there any other features that you'd like to have implemented?

At this point I want to concentrate on getting you going as fast as possible; 
when the basics work, then I'm going to add other features, like keyboard 
shortcut customization, possibly things like additional filtration, sensitivity 
curves (you can see featuritis kicking in again)...

Thank you for your understanding,

Michal

Original comment by f.jo...@email.cz on 26 Nov 2012 at 8:22

[GoogleCodeExporter]

the only feature i use is the tracking on/off. I have it mapped to f9, and f9 
always overrides programs so it toggles tracking no matter what app is open. i 
use relative in   the smartnav program, not absolute. that's all i need to get 
going. The featuritis joke is hilarious! 

Original comment by billstre...@gmail.com on 26 Nov 2012 at 2:18

[GoogleCodeExporter]

Hello Bill,
just to let you know about the progress - the tracking itself is pretty much 
working, although I want to work on it a little bit more; right now it feels 
more like juggling - I'll try to find such a settings that will be precise 
enough to allow you to get the cursor exactly where you want it, while allowing 
you to get the cursor from one side of the monitor to the other quickly... 
Probably some nonlinearity is the key to this problem. In parallel I'm working 
on a small and simple GUI that would allow you to tweak sensitivity and 
deadzone.

The progress is a bit slower, since I'm using parts of code, that weren't used 
much, so there are occasional bugs here and there... Be it as it may, the work 
is progressing and the result should come soon.

Thank you for your patience,

Michal

Original comment by f.jo...@email.cz on 30 Nov 2012 at 7:31

[GoogleCodeExporter]

AH the beast of programming! BUGS!

Original comment by billstre...@gmail.com on 30 Nov 2012 at 7:14

[GoogleCodeExporter]

Hello Bill,
working on the Mickey (that is the name I've chosen for the mouse emulator), I 
noticed several problems, that go relatively deep in the linuxtrack 
architecture. If I was going to solve them in the current "stable" version, 
then I'd have to go and reimplement the fix in the new_server branch, that is 
going to be merged to the trunk soon (as base for linuxtrack 1.0). So I came to 
the following decision - I'll go ahead and reintegrate the new branch first, 
and then fix the problems I've found.

This is going to have several consequences - the first one and the most obvious 
one, is a few days delay in getting the working solution to you. But there are 
others, that should be benefitial for you (me and others too); some of them 
(hopefully) invisible (different architecture of linuxtrack server-client 
communication, changed preferences code, ...), while others should be pretty 
visible - new improved GUI (at least I hope users will see it as an 
improvement), working profiles (different applications can have different 
tracking settings), better help, wine games support, and others...

I'm sorry I'm showing you mostly the dark side of software development (delays, 
bugs and more delays, ...), but I want to be pretty sure, that the thing I send 
you works reasonably well and doesn't need a nuclear physicist to setup.

Thank you for the understanding and your patience,

Michal

Original comment by f.jo...@email.cz on 4 Dec 2012 at 6:45

[GoogleCodeExporter]

yes waiting is better, i totally understand.

Original comment by billstre...@gmail.com on 4 Dec 2012 at 6:54

[GoogleCodeExporter]

Hello Bill,
just to let you know - we're back on track... The obvious bugs are smashed, and 
I'm back working on the mickey...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 6 Dec 2012 at 9:17

[GoogleCodeExporter]

Hello Bill,
I'm sorry it took me so long, but finally here is the version, that should work 
reasonably well...

I've never used the SmartNav, so I'd be interested in knowing how would you 
compare the two...

Let me know how does it work (I hope so) for you...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 15 Dec 2012 at 11:17

Attachments:

• linuxtrack121216.zip

[GoogleCodeExporter]

It seems to work in the camera view when the ltr gui is on, but in linux the 
leds are on but it doesn't move the mouse, when i start the ltr gui it comes up 
with a devhelp window with dump prefs button.

Original comment by billstre...@gmail.com on 17 Dec 2012 at 12:55

[GoogleCodeExporter]

Hello Bill,
I'm not sure I understand what is going on...

If you start the ltr_gui, and start tracking, does it track? I mean you see the 
blobs in the camera view and the 3D preview does track too?

If you see the blobs (well, there should be ideally only one, and it should 
have the white cross in it), but it doesn't track, please make sure you have 
the single point model selected (you have to stop the tracking for that)...

If the tracking works (you can pan the view left/right/up/down), try closing 
the ltr_gui and starting the mickey...

When mickey starts, do those numbers in the bottom of the window change? If 
they do, try to calibrate the thing (see the readme for details)...
Thank you for trying it out...

Kind regards,

Michal

Original comment by f.jo...@email.cz on 17 Dec 2012 at 5:59

[GoogleCodeExporter]

when i start the ltr gui the blob in the camera view with shows a blob with the 
cross, the 3d preview window has just a blue backbround but the bottom still 
shows tracking numbers. the mickey doesn't seem to start at all, so maybe thats 
why. I'm attaching screen shots to help.

Original comment by billstre...@gmail.com on 17 Dec 2012 at 8:15

Attachments:

• ltrgui.png
• [ltrgui 1.png](https://storage.googleapis.com/google-code-attachments/linux-track/issue-30/comment-71/ltrgui 1.png)
• [ltrgui 2.png](https://storage.googleapis.com/google-code-attachments/linux-track/issue-30/comment-71/ltrgui 2.png)
• [ltrgui 3.png](https://storage.googleapis.com/google-code-attachments/linux-track/issue-30/comment-71/ltrgui 3.png)

[GoogleCodeExporter]

screen shot

Original comment by billstre...@gmail.com on 17 Dec 2012 at 8:19

Attachments:

• [ltrgui camera view.png](https://storage.googleapis.com/google-code-attachments/linux-track/issue-30/comment-72/ltrgui camera view.png)

[GoogleCodeExporter]

Hello Bill,
I think I know what is going on - the problem is missing QxT library...
Please try to install the following package: 

sudo apt-get install libqxt-dev

To verify you have all that you need, run 

ldd /opt/linuxtrack/bin/mickey

It will show you all libraries linked by the program and check that it can find 
everything (if something is missing, try to find the package on 
packages.ubuntu.com).
Thank you for your patience,

Michal

Original comment by f.jo...@email.cz on 17 Dec 2012 at 9:05

[GoogleCodeExporter]

ok

Original comment by billstre...@gmail.com on 17 Dec 2012 at 9:11

[GoogleCodeExporter]

i didnt have that so now mickey starts, but not tracking or led on. f9 doesnt 
turn it on, but i found something in the ltr gui log. it's not activating the 
smartnav model type.

Original comment by billstre...@gmail.com on 17 Dec 2012 at 11:09

[GoogleCodeExporter]

heres the log

Original comment by billstre...@gmail.com on 17 Dec 2012 at 11:13

Attachments:

• [ltr gui log.txt](https://storage.googleapis.com/google-code-attachments/linux-track/issue-30/comment-76/ltr gui log.txt)

[GoogleCodeExporter]

Hello Bill,
didn't you have the ltr_gui on, when starting mickey?

There are two things you can try:
1) make sure that no ltr_gui and no mickey is running and start mickey... This 
is the default mode of mickey's operation...

2) if 1) doesn't work (it can take few seconds), try to start ltr_gui, then 
start mickey and then start tracking in the ltr_gui... In that case, I'd advise 
you to disable the 3D preview (Misc. pane, second checkbox).

Let me know how it goes... And if 1) doesn't work, please send me all the 
linuxtrack logs - I'd be very interested in knowing what is going on in there...

Kind regards,

Michal

PS. I'm sorry for that QxT inconvenience; that is the problem of this package - 
when the thing is ready, that will be handled by the packaging system and the 
universal package will need to have it compiled it in...

Original comment by f.jo...@email.cz on 18 Dec 2012 at 7:44

[GoogleCodeExporter]

1 did not work. 2 tracks in the camera preview window but mickey has no 
coordinates showing and won't calibrate. so, here's the log

Original comment by billstre...@gmail.com on 18 Dec 2012 at 6:32

Attachments:

• [log file](https://storage.googleapis.com/google-code-attachments/linux-track/issue-30/comment-78/log file)

[GoogleCodeExporter]

Hello Bill,
the log doesn't show anything out of ordinary as far as I can tell...
I'd like to ask you this:

close all ltr_gui/mickey instances and wipe the logs using the following 
command:

rm /tmp/linuxtrack*.log

Then run mickey, wait approximately 30 seconds and shut it down...

Now run the following command:

zip ~/Desktop/mickey_logs.zip /tmp/linuxtrack*.log

It will create a mickey_logs.zip file - please attach it here, so I can take a 
peek at what is going on...
Thank you very much for your help,

Michal

Original comment by f.jo...@email.cz on 18 Dec 2012 at 9:50

[GoogleCodeExporter]

ok

Original comment by billstre...@gmail.com on 18 Dec 2012 at 10:19

Attachments:

• mickey_logs.zip

[GoogleCodeExporter]

Hello Bill,
thank you for the log - right now I noticed a strange thing in your previous 
logs; the ltr_gui was supposed to reside in /opt/linuxtrack/bin directory...

For some reason it seems you have the ltr_gui in your Desktop directory. This 
probably spoils the whole thing. Can you try to wipe out the previous install 
and install the latest package again?

Kind regards,

Michal

Original comment by f.jo...@email.cz on 18 Dec 2012 at 11:18

[GoogleCodeExporter]

One more thing - did you by any chance copied ltr_gui to your desktop and run 
it from there? If you did, please remove the copy and use symbolic link 
instead...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 18 Dec 2012 at 11:45

[GoogleCodeExporter]

yes i did,God i feel dumb now! i'll try that tomorrow.

Original comment by billstre...@gmail.com on 19 Dec 2012 at 1:11

[GoogleCodeExporter]

ok, mickey works now but when i turn it on the mouse goes to the bottom left 
right away, i click calibrate and it says center and push a button. but nothing 
happens, so here's the log.

Original comment by billstre...@gmail.com on 19 Dec 2012 at 5:16

Attachments:

• mickey_logs.zip

[GoogleCodeExporter]

oh yeah, my sip puff switch doesn't work either.

Original comment by billstre...@gmail.com on 19 Dec 2012 at 5:17

[GoogleCodeExporter]

never mind now when i start it it all works!

Original comment by billstre...@gmail.com on 19 Dec 2012 at 5:21

[GoogleCodeExporter]

is there a way to make the sip puff always on even when tracking is paused?

Original comment by billstre...@gmail.com on 19 Dec 2012 at 5:22

[GoogleCodeExporter]

it seems like the sip puff just stops working sometimes too.

Original comment by billstre...@gmail.com on 19 Dec 2012 at 6:06

[GoogleCodeExporter]

it seems like the sip puff just stops working sometimes too.

Original comment by billstre...@gmail.com on 19 Dec 2012 at 6:06

[GoogleCodeExporter]

Hello Bill,
I'm glad to hear that it works at least somehow...

The sip and puff malfunctions - did you find any pattern in that? Does it seem 
to be connected to starting ltr_gui while mickey is running?

Doesn't it work at all, or just some "clicks" are missed?

To your question - the way it is implemented now, the pause means inactive 
sip/puff switch. But if you want to, I can implement the pause in such a way, 
that only illuminationg IR LEDs would be turned off, so the sip/puff switch 
would be active...

Kind regards,

Michal

PS. My internet connection seems to have some problems and it will take few 
days to replace the unit, so I might be unavailable a day or two...

Original comment by f.jo...@email.cz on 19 Dec 2012 at 7:52

[GoogleCodeExporter]

One more thing - when mickey is started, when it initializes the camera, it 
waits two seconds and then the position of the blob is taken as a center... If 
you move your head awy during that moment, then the mouse cursor will behave 
incorrectly.

If you want to change the behavior, I can do that - like on startup, wait for a 
first click (that one would be discarded) and recenter/start tracking then... 
I'm open to ideas - you are the one who is going to use it afterall... 
Kind regards,

Michal

Original comment by f.jo...@email.cz on 19 Dec 2012 at 8:21

[GoogleCodeExporter]

The sip and puff works for awhile then stops. i would like the pause to leave 
the sip and puff on. I also would like it to move faster if that's possible. i 
will remember to not move my head at first. also the calibrate still won't work 
in mickey.

Original comment by billstre...@gmail.com on 19 Dec 2012 at 9:21

[GoogleCodeExporter]

OK Bill, I'll change the implementation so that the sip/puff switch will work 
regardless of the paused/unpaused state...

Higher sensitivity will not be problem - just to make sure we're on the same 
page - you want higher maximum speed, or higher sensitivity overall?

Could you elaborate more on the Calibrate not working?

As for the sip/puff stopping working - you're just using it and suddenly it 
stops?
What if you'd try to pause/unpause it - does it help? And how about the 
tracking - does that work when sip/puff switch stops working?
Kind regards,

Michal

Original comment by f.jo...@email.cz on 19 Dec 2012 at 9:39

[GoogleCodeExporter]

higher overall, and max. just in case.when i press the calibrate in mickey it 
says center then press a button, no button registers and it won't stop 
calibrate and go back to tracking. yes i just use it and then stops, i think in 
a new program, like firefox then moving to dolphin. The tracking works yet just 
not the switch. f9 doesn't fix it. but closing and restarting mickey works.

Original comment by billstre...@gmail.com on 19 Dec 2012 at 9:48

[GoogleCodeExporter]

Hello Bill,
by pressing button in calibration dialogue I mean sip/puff (doesn't matter) - 
it seems to work during my tests...

May I ask you how long does it take for the sip/puff switch to stop working?
Kind regards,

Michal

Original comment by f.jo...@email.cz on 19 Dec 2012 at 11:31

[GoogleCodeExporter]

Hello Bill,
I think I've managed to reproduce the problem with sip/puff switch stops 
working...
It seems that there is some kind of interaction between the GUI and the mouse 
emulation; I'll try to separate the gui and the mickey itself to separate 
processes to see if the problem goes away...

Kind regards,

Michal

Original comment by f.jo...@email.cz on 21 Dec 2012 at 12:13

[GoogleCodeExporter]

ok, thanks, also can you make the mouse full speed right away and disable the 
mouse acceleration?

Original comment by billstre...@gmail.com on 21 Dec 2012 at 2:10

[GoogleCodeExporter]

Hello Bill,
could you please elaborate a bit more on that?

The way it is done now, there is a deadzone and then the more you move your 
head, the faster the pointer goes - is that what you want to change?

Kind regards,

Michal

Original comment by f.jo...@email.cz on 21 Dec 2012 at 11:57

[GoogleCodeExporter]

oh thats what the dead zone is, ok so if i change the dead zone can i just make 
the mouse one speed? not faster as my head moves?

Original comment by billstre...@gmail.com on 21 Dec 2012 at 7:04

[GoogleCodeExporter]

Not really... I didn't anticipate such a way of using that. But I can make it 
that way - no problem.

Kind regards,

Michal

Original comment by f.jo...@email.cz on 21 Dec 2012 at 7:34