xpad-hackers team mailing list archive

[Dave Rove <question684748@xxxxxxxxxxxxxxxxxxxxx>]

Question #684748 on Xpad changed:
https://answers.launchpad.net/xpad/+question/684748

Dave Rove gave more information on the question:
Aaand I fixed it. After looking for all files related to xpad with
"locate" and looking at xpad's configuration options again, I saw that
there was a startup file ~/.config/autostart/xpad.desktop (presumably
placed there if you configure it to startup on login) and I noticed xpad
had a  config setting to wait for the taskbar (which I had checked).
Although xpad's icon appeared correctly in the taskbar, I wondered if it
was *still* starting too early. If it tried to place a control on the
taskbar before the desktop had properly started then it might well place
a control in the screen's "zero" coordinates.

I replaced the "xpad" command in the desktop startup file with "(sleep
2;xpad;)&" to give it and extra 2 seconds and rebooted. The problem was
gone. I rebooted a few more times to check that it really was that
simple and the problem really had gone, and yes it had.

So there we are. It seems that there's still something a bit
pathological with xpad's startup, but the problem is solved for me.

-- 
You received this question notification because your team Xpad
Developers is an answer contact for Xpad.