-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Failed to initialize GTK." running grc after "conda upgrade --all" #40
Comments
This error is similar to #37 and may have the same cause. Can you post the output of
Interesting. I'll have to take a look with my Pluto to see if there's anything that can be done.
I'd love to include it if it can be made possible. See #29.
|
Thank you for your response. After the upgrade I also tried running
I below is the list before the upgrade,
I below is the list after the upgrade,
Thanks, I will take a look.
Thanks, I will have a go at that when I get some time to do so. |
I subsequently did another re-installation and then upgraded, I did I was under the impression that they effectively do the same thing ? This time the upgrade went without any warnings or errors and Attempts at listing as you requested above,
Thanks in advance |
Curious that when I do
Maybe it's because Anyway, one thing I see from your upgraded package list is that many of the packages are now from the default (Anaconda, no channel name listed) channel instead of the conda-forge channel. I don't know how that happened, because the default channel should be disabled by, well, default. But the upshot is that there could definitely be binary incompatibility there of the type that you are seeing. Given that lots of things are throwing errors that are different, that's my guess. You also don't have the I would try setting
before another Barring that, is there a reason you want to upgrade from the 2022.09.22 release? Might be easiest to stick with that, where at least I'm reasonably sure that set of packages works well together.
I'll have to think about that. I'm pretty sure I've heard of a conda package or two that does something similar, so maybe I'll try to dig that information up. |
I did that after reinstalling and that seems to have solved the problem. So far everything works.
No reason in particular, other than having the impression that it is generally good practice to do so. I have hitherto applied updates immediately after installation (which AFAIK is general and widespread advice and practice after most software packages are installed) and then every month or so beyond that. I will henceforth be more circumspect about doing so. Thanks again for your responses. PS, I am unsure if I should close this issue. For that reason I will for the time being leave it open. Please indicate if you prefer that I do. |
It's generally not a terrible idea, but evidently it has some risks! It's been illuminating for me because I didn't think that much binary incompatibility was lurking out there with the defaults channel, and that's resulted in me making a change that should help all users generally in the future. Thanks! I think I'll close this since the problem has been figured out, but feel free to open new issues if you want to separately document the requests for gr-fosphor and SDRPlay. Those aren't likely to ever drop off my radar, but extra reminders couldn't hurt. |
Hi,
On a Windows 11 machine I am getting the following errors,
After a fresh install of the latest release (2022.09.22) an then running
conda upgrade --all
Any ideas on how to solve this if indeed possible ?
The only way I can get things working is to remove and and reinstall
radioconda
.Also while I am here, a couple of other things.
In a windows
command
prompt,On the same machine and in a
conda
prompt,It seems the
conda
environment does not see devices that are network attached. WithinGRC
it is still possible to use the devices.For example
ip:plutoplus.local
works within aGRC
flow diagram and so does running the resulting python script on its own.This is not really a showstopper, but it would be great if it could be resolved.
Can
SDRplay
support be added either retrospectively, or could it also be included as part of the installation ?Lastly, part of the roadmap to include
gr-fosphor
in as part of the installation, if not could it be and is there any current method by which to install this and OOT GNURadio modules on Windows ?Thanks and best regards.
The text was updated successfully, but these errors were encountered: