Koslowski, Sebastian (CEL) wrote
> Can start GRC from a command line and see if any errors are thrown when
> you try open a props dialog?
That would have been a good idea, but I already fixed it somehow.
"Somehow" because it seemingly wasn't the variable I wrote above.
My assumption is that i re
Can start GRC from a command line and see if any errors are thrown when
you try open a props dialog?
Sebastian
On 10/25/2016 08:10 PM, MarkO wrote:
> Hi everyone,
>
> I try to make the story as short as possible:
>
> - installed GRC 3.7.10.1 from source via script on Ubuntu 14.04.
> - decided to
Thanks for your advice Cinaed,
actually none of the three variables was set in .bashrc or .profile.
I am just wondering how GRC 3.7.9 worked without them.
I only set PYTHONPATH=/usr/local/lib/python2.7/dist-packages in .bashrc.
Regards,
Markus
--
View this message in context:
http://gnuradi
On 10/25/2016 11:10 AM, MarkO wrote:
> Hi everyone,
>
> I try to make the story as short as possible:
>
> - installed GRC 3.7.10.1 from source via script on Ubuntu 14.04.
> - decided to update from Ubuntu 14.04 to 16.04.
> - couldn't start GRC anymore
> - reinstallation via script -> didn't wor
Hi everyone,
I try to make the story as short as possible:
- installed GRC 3.7.10.1 from source via script on Ubuntu 14.04.
- decided to update from Ubuntu 14.04 to 16.04.
- couldn't start GRC anymore
- reinstallation via script -> didn't work
- completely removed everything of GRC I could fin
