Help getting NgcGui working on QtDragon

Hello, I've consulted the following guides:
linuxcnc.org/docs/html/gui/ngcgui.html#ngcgui-ini
linuxcnc.org/docs/html/gui/qtvcp-widgets...cp:widgets:qt-ngcgui

I'm on 
Debian: 6.1.0-30-rt-amd64
linuxcnc-uspace: 1:2.9.4

I've attached my .ini file, and my error linuxcnc.report and a screenshot of the last thing I see before it crashes.

I'm trying to use QtDragon: Utils > NgcGui.
I start by clicking "New Tab."
But when I try to select anything, like "Select Preamble," or "Select Subfile," etc, the program crashes.

I'm thinking it's not finding the subdirectories where these files are located.

But in the [RS274NGC] I have:
I believe the files are there in those directories. Though I also understand some of those are symbolic links, could this be a problem??

To prove the file is there -- for example, the preamble specified in *.ini -- I issue to a terminal:

Nontheless, for example, trying to click "Select Preamble," I was going to guess would choose the
and from a terminal, if I issue:

Then I get back:

Which seems like it's there.

I'm sorry in advance if this is an obvious fix.

Any help would be great.

Thanks again!

 

Vector wrote:

Code:

-rw-r--r-- 1 root root 248 Jan 25 04:20 /home/maker/linuxcnc/nc_files/examples/ngcgui_lib/utilitysubs/mm_std.ngc

It is there, but it is owned by user root, so it will appear non existent to normal users, in your case maker is the normal user that has no access rights to that file.
No idea why or how, but in general, never use "sudo" unless explicitly told to do so.
You can try to manually set the permissions to read that file and see if that works:

I don't see the INI entry in [DISPLAY]:
NGCGUI_SUBFILE_PATH =

Thank you!

cmorley fixed it: that NGCGUI_SUBFILE_PATH was only documented under the linuxcnc.org/docs/html/gui/qtvcp-widgets...cp:widgets:qt-ngcgui because, well, that's where it should be since it's only for Qt.

tommylight, thank you very much, but I think it must be able to see it: since in fact I did "ls -al ... " from the maker user, and there it is. And now, it looks like the program is working. That might've been the problem, but just for future google travelers, in my case it was not.

Thanks again!!