Can't install camview in buster

Where does it spend the time? I would guess at the "Waiting for component 'qtvcp_embed' to become ready..." stage?

You can make some of the cruft disappear by adding the missing items to the [DISPLAY] section of the INI {and probably should, just so you end up with sensible values in the GUI).

I don't know how serious the bad-drawable errors are. Are they regular and continuous?

There should be a sim: axis/qtvcp/qtvcp_tab available.
Can you try it and see if there is a big delay too ?

It works on 2.8.4 here without any noticeable startup delay, the "BadDrawable" messages only seem to appear during shutdown.

I do see these at the top of your messages, I have no idea what they are or whether they cause any issues.

# handle_includes(): <35> found #INCLUDE with no filename
# handle_includes(): <36> CANNOT READ nosuchfile

maybe it has to do with this?
linuxcnc.org/docs/devel/html/config/ini-...html#sub:ini:include

andypugh wrote:

a) Where does it spend the time? I would guess at the "Waiting for component 'qtvcp_embed' to become ready..." stage?

b) You can make some of the cruft disappear by adding the missing items to the [DISPLAY] section of the INI {and probably should, just so you end up with sensible values in the GUI).

c) I don't know how serious the bad-drawable errors are. Are they regular and continuous?
 

Andy
a) It delays the startup of the axis graphical interface. The manual tool change message pops up immediately, but then it is delaying the pop up of the xis window.  See file slow-start.txt. I could not really tie it down 100% sure.   But I would guess, it is happening here "Waiting for component 'qtvcp_embed' to become ready..............[QTvcp][DEBUG]  Calling the handler file's initialized__ function (qtvcp:219)". I guess, this is where the cam_align stuff is being initiated and the corresponding tab being prepared. Could it be slow response of the camera? I also note: the number of the dos "...." changes, as does the time axis is delayed. Have to test, if the dots correspond to delay time (which is what I would expect).

b) some clarification needed: What items do you think are missing?
I'll add the original-version.txt of the expanded ini [DISPLAY] section and the modified-version.txt. Does not behave differently at all.

c) The messages containing "(BadDrawable)" only after closing axis

I'll try the hints given in the gladly received post of you and report back.
greez
chris
 

cmorley wrote:

There should be a sim: axis/qtvcp/qtvcp_tab available.
Can you try it and see if there is a big delay too ?
 

Chris
Yes, unfortunately, see attached output.
greez
chris