On 07/09/2017 06:04 AM, Jozef Lošonský wrote: > OK, finaly I solved my issue, as I don't know the historical or > political reasons in gnuradio here is my summary only, it can help to > somebody with similar issue. > > 1) part of code in Generator.py requires xterm variable but it is not > passing through on my system (xterm dependency should be installed > manually on raspbian, but it doesn't matter, probably I'm missing > something else)
It is a result of operator error. There should no reference to X11 anything anywhere in the python script - X11 is the Linux GUI - "No GUI" means no X11 - no xterm. If you want to eliminate the problem then you need to change the way you're doing things. -- Cinaed > ... > #when in no gui mode on linux, use an xterm (looks nice) > if self._generate_options == 'no_gui' and 'linux' in > sys.platform.lower(): > cmds = [XTERM_EXECUTABLE, '-e'] + cmds > ... > it is not working right, despite I'm exporting XTERM_EXECUTABLE > manually in console... > 2) > I did simply comment out that line and replace it by (of course there > are more elegant solutions, but...) > cmds = cmds > 3) hopefully Cinaed Simson is not interesting about my flowcharts/python > codes anymore, because issue wasn't here :) > > > 2017-07-07 6:51 GMT+02:00 Cinaed Simson <cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com>>: > > On 07/06/2017 04:54 PM, Jozef Lošonský wrote: > > OK, again, python script is successfully created/written, and it is > > runnable outside of GRC, the errno13 comes from execve call which is > > incomplete, can you see that, please? > > Send the flowchart and the python code if you want help. > > -- Cinaed > > > > > On Jul 7, 2017 01:27, "Cinaed Simson" <cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com> > > <mailto:cinaed.sim...@gmail.com <mailto:cinaed.sim...@gmail.com>>> > wrote: > > > > On 07/06/2017 02:57 PM, Jozef Lošonský wrote: > > > I'm not behind my pc, but I think that it is possible to > understand my > > > issue, that py file is generated from any flowgraph OK, but "play > > > button" press fails with Errno13 when "No GUI" (of course I'm not > > using > > > any WX or QT block in such case). > > > > Without at least an error message, e.g., Errno13, it's impossible to > > figure out what the problem is since your explanations make no > sense. > > > > In fact, you've never indicated there was an error message. > > > > Typically, an Errno13 is a write permission problem - it's not a > > gnuradio or grc problem. > > > > And the error should have included > > > > Generate Error: [Errno 13] Permission denied: > > > > and then it prints out the location of where you're writing to. > > > > The obvious solution is to find another play to write the file. > > > > -- Cinaed > > > > > > > > > > On Jul 6, 2017 11:48 PM, "Cinaed Simson" <cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com> > > <mailto:cinaed.sim...@gmail.com <mailto:cinaed.sim...@gmail.com>> > > > <mailto:cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com> <mailto:cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com>>>> > > wrote: > > > > > > On 07/06/2017 02:14 PM, Jozef Lošonský wrote: > > > > Hi, there are no GUI elements and graf generated py > file works > > > fine from > > > > console, but GRC only is unable to execute that already > > generated > > > file. > > > > > > Then post the flowgraph and the python code - it's the only > > way we can > > > help you. > > > > > > -- Cinaed > > > > > > > > > > > On Jul 6, 2017 11:08 PM, "Cinaed Simson" > > <cinaed.sim...@gmail.com <mailto:cinaed.sim...@gmail.com> > <mailto:cinaed.sim...@gmail.com <mailto:cinaed.sim...@gmail.com>> > > > <mailto:cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com> <mailto:cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com>>> > > > > <mailto:cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com> > > <mailto:cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com>> <mailto:cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com> > > <mailto:cinaed.sim...@gmail.com > <mailto:cinaed.sim...@gmail.com>>>>> > > > wrote: > > > > > > > > On 07/06/2017 12:10 AM, Jozef Lošonský wrote: > > > > > Hello, > > > > > my GRC is unable to execute graphs (no GUI elements) > > when I > > > switch > > > > > option to No GUI, everything else seems to be > working. > > > > > > > > The option "No GUI" means no GUI elements, i.e., > no graphs. > > > > > > > > If you had a graphical element in your flowgraph, GRC > > should have > > > > complained and printed an error message in the GRC > console > > > when you > > > > clicked on the button "Generate the flow graph". > > > > > > > > In order to generate python code from GRC you have > > disable the GUI > > > > elements in the flowgraph in order to generate > python code. > > > > > > > > > In addition "No > > > > > GUI" py script (generated by same GRC) is > running fine in > > > console > > > > of the > > > > > same user which is running GRC what is interesting. > > > > > > > > I didn't find other > > > > > way how to try get more info about issue than run > > whole GRC > > > under > > > > strace > > > > > -ffy and read the strace file. > > > > > Comparing strace files with working GRC instance on > > another PC > > > > @jcorgan > > > > > did suggest that in execve python is missing. > > > > > > > > And most likely the gnuradio software and the required > > > software packages > > > > needed to run gnuradio on PC @jcorgan are probably > > missing too. > > > > > > > > A working installation of python is one of the > > perquisite to run > > > > gnuradio. > > > > > > > > > > > > > > Bad: > > > > > [pid 2704] execve("/usr/local/bin/", ["", "-e", > > > "/usr/bin/python", > > > > > "-u", "/home/pi/top_block.py"]...= -1 EACCES > > (Permission denied) > > > > > Good: > > > > > [pid 12112] execve("/usr/bin/python", > > ["/usr/bin/python", "-u", > > > > > "/home/loso/top_block.py"], [/* 75 vars */] > > <unfinished ...> > > > > > > > > > > I'm trying to find which env variable or what > option am I > > > missing/have > > > > > wrongly configured in GRC config or somewhere else. > > > > Based on the content of this post, everything on your > > machine > > > is working > > > > correctly. > > > > > > > > If you can actually generate an error message using > > gnuradio - > > > other > > > > then enclosed operator errors - post the error > message, the > > > flowgraph > > > > and the python code. > > > > > > > > > > > > > > Thank you. > > > > > Jozef > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Discuss-gnuradio mailing list > > > > > Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>> <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>>> > > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>> <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>>>> > > > > > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>> > > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>>> > > > > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>> > > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>>>> > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Discuss-gnuradio mailing list > > > > Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>> <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>>> > > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>> <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org> > > <mailto:Discuss-gnuradio@gnu.org > <mailto:Discuss-gnuradio@gnu.org>>>> > > > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>> > > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>>> > > > > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>> > > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>>>> > > > > > > > > > > > _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio