Mickey not quitting cleanly in Ubuntu

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Type "mickey" in terminal.
2. Press "quit" button.

What is the expected output? 
Unix command line prompt.

What do you see instead?
rich@rich:~$ mickey
Opened /dev/uinput
Name: 'Linuxtrack's Mickey'
Waking up!
Slave reader thread function entered!
Opening the channel!
Fifo opened!
Shortcut set!
Handler installed!
Shortcut set!
Opening master comms!
Starting as master!
Sending string Mickey
Trying to register slave!
Master comms opened => u -> 6  d -> 8
Master is responding!
Master Uplink 6, Downlink 8
Slave @fifo 9 registered!
QThread: Destroyed while thread is still running
rich@rich:~$ We have HUP in Master!
Shutting down tracking!
Master closing fifo 8

What version of the product are you using? On what operating system?
0.99.10 on Ubuntu 14.04 LTS 64 bit

Please provide any additional information below.
This issue is low priority as the workaround is merely to close the terminal. 

Original issue reported on code.google.com by a...@geoff.kelsall.name on 30 May 2014 at 9:55

[GoogleCodeExporter]

Hello,
If I'm not mistaken, if you press enter, the prompt will appear - right?

In fact - you can see it already towards the end (rich@rich:~$):

QThread: Destroyed while thread is still running
rich@rich:~$ We have HUP in Master!
Shutting down tracking!
Master closing fifo 8

The stuff beyond the prompt is just a byproduct of the architecture - there is 
a "hidden" component doing the tracking and the fact that it is controlled 
asynchronously; as the application closes, the tracker detects it and shuts 
down itself - that produces these messages you see...
But in fact the prompt is already there and waiting.

Please let me know if it adresses your concerns...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 30 May 2014 at 8:55

[GoogleCodeExporter]

Ah OK thanks.

Original comment by a...@geoff.kelsall.name on 2 Jun 2014 at 10:33

[GoogleCodeExporter]

Not sure if I can close this issue myself - anyway as far as I am concerned it 
can be closed.

Original comment by a...@geoff.kelsall.name on 4 Jun 2014 at 10:05

[GoogleCodeExporter]

Thank you for the info, I'll close it down then...
Kind regards,

Michal

Original comment by f.jo...@email.cz on 6 Jun 2014 at 5:10

• Changed state: Invalid