pyngcgui error

More
3 years 3 months ago #275835 by 10K
pyngcgui error was created by 10K
I hope this is the right place for this...

I'm upgrading LinuxCNC from ver 2.8 to ver 2.9 and Debian from Buster to Bookworm. After installing LinuxCNC, I dropped my old configs directory into the new install. I'm using gmoccapy for the UI. I'm getting an error when running LinuxCNC:

gtk-builder-error-quark: ./pyngcgui_popupkeyboard.ui:22:42 Invalid property: PyNgcGui.gtk_theme_name (11)not enough values to unpack (expected 2, got 1)

Since I have not changed anything, I'm guessing this is associated with the version update. Any ideas?

More info on error in attached files

Please Log in to join the conversation.

More
3 years 3 months ago #275836 by chris@cnc
Replied by chris@cnc on topic pyngcgui error
i would guess it has something to do with this line 29 in your ini
"EMBED_TAB_COMMAND     = gladevcp -x {XID} ./pyngcgui_popupkeyboard.ui"
Take a look at this file. Is the folder right?
Here is the manual 
linuxcnc.org/docs/2.9/html/gui/ngcgui.html

Please Log in to join the conversation.

More
3 years 3 months ago #275858 by newbynobi
Replied by newbynobi on topic pyngcgui error
Hallo,

This is for sure not related to gmoccapy. I guess that pyngc has not been updated to support glade 3 and python3. The Update of LinuxCNC does now require the use of the new versions. gmoccapy has been adapted to this (still small steps to go, but stable running).

The error is error with XML File that is the glade file. GladeVCP tries to read that one and has a problem with it.

Norbert

Please Log in to join the conversation.

More
3 years 3 months ago #275864 by phillc54
Replied by phillc54 on topic pyngcgui error

Please Log in to join the conversation.

More
3 years 3 months ago #275899 by 10K
Replied by 10K on topic pyngcgui error
Thanks for the suggestions!

I replaced both the pyngcgui.ui and the pyngcgui_popupkeyboard.ui files with the ones from github.com/LinuxCNC/linuxcnc/tree/master/configs/sim/gmoccapy

The new versions were very close to the old ones, except that the offending line was removed. I ran LinuxCNC, and the error I asked about had gone away. Unfortunately, the following error lines were still present from before:

Code:
Starting DISPLAY program: gmoccapy 60817411 not enough values to unpack (expected 2, got 1) 'btn_sel_next' 'btn_sel_prev' 'btn_select' 'btn_home' 'btn_dir_up' 'btn_jump_to' not enough values to unpack (expected 2, got 1) not enough values to unpack (expected 2, got 1) 'IconFileSelection' object has no attribute 'on_btn_jump_to' not enough values to unpack (expected 2, got 1) not enough values to unpack (expected 2, got 1) Attribute error <GParamString 'icon-theme-path'> and <class 'str'> sans 10 Attribute error <GParamString 'icon-theme-name'> and <class 'str'> sans 10


This error was also present in the earlier run. Logs attached.

Please Log in to join the conversation.

More
3 years 3 months ago #275900 by HansU
Replied by HansU on topic pyngcgui error
There is a gmoccapy sample sim config with ngcgui in 2.9. Try to start that and compare it with your configuration.

Please Log in to join the conversation.

More
3 years 3 months ago #275904 by newbynobi
Replied by newbynobi on topic pyngcgui error
You may want to start pyngcgui also stand alone to try if that does run OK. 
With command line you can also add the keyboard.

Please Log in to join the conversation.

More
3 years 3 months ago #275931 by newbynobi
Replied by newbynobi on topic pyngcgui error
Hallo,

I just looked again in the error messages and als in the pyngc python code. 
I would suggest to solve first the input.0.btn-joystick does not exist

Error as it could be that this is the one that causes the other errors.

Norbert

1. Start your config without any embedded tab and without pyngc
2. enable first Tab and check
3. eneble next tab and check

Until you are done.

Norbert

Please Log in to join the conversation.

More
3 years 3 months ago #275957 by 10K
Replied by 10K on topic pyngcgui error
Thanks! That put me on the right track.

I'm using a controller with a joystick (and a pendant). For some reason, the name of one of the buttons changed between the old and the new Debian and LinuxCNC versions from input.0.btn-joystick to input.0.btn-trigger.

Easy fix, once I figured it out.

LinucCNC runs now! I have a new problem with the display, but I'll start a new thread for it.

Please Log in to join the conversation.

Time to create page: 0.195 seconds
Powered by Kunena Forum