On Mon, May 6, 2013 at 9:18 AM, Bennett, David S. (Scott)
<scott.benn...@jhuapl.edu> wrote:
>> Scott,
>>
>> Are you using relative path names for the file sink?
>>
>> Tom
>
> Tom,
>
> Thanks for the note. Hopefully my "netiquette" is appropriate here. It's
> been an awfully long time since I've posed in a mailing list.
>
> Per your question referenced above, the path name I have in the dialog box is
> "/home/developer/Documents/gnuradio/record.dat"
>
> If I understand my Linux right, this is an absolute path from root. And it
> is the same path as listed in the python script generated by gnuradio
> companion. I have tried executing gnuradio companion from the terminal while
> in this working directory ("/home/developer/Documents/gnuradio), but I get
> the same error. I have also set this as my working directory in my
> gnuradio.desktop application shortcut with the same results.
>
> Thanks,
> Scott
Yes, you're using the absolute path. I was just checking to see if you
might have been trying to create a file in a write-protected directory
or a place that didn't actually exist, which could have been a result
of using a relative path and having GRC point to a place you weren't
expecting.
But with this info, I'm not sure. That's not an error that GNU Radio
is producing; it's the OS. If you replace the file sink with something
else (like a null sink), do you get the same error? I'm just checking
here to see if it's a problem with the file you are trying to open or
maybe complaining about something else.
Tom
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
