FahControl freeze when GPU slot not available

[informatorius]

When FAH is configured to use 2 GPU slots but there is only one GPU available then starting FAHcontrol shows an error message and freezes. So it is not possible to remove the wrong GPU slot. Expected behavior: FahControl does not freeze and wrong GPU slot can be removed.

Error message: "iter should be a GTKTreeIter"

FahClient 7.5.1 on Windows 7

https://foldingforum.org/viewtopic.php?f=106&t=31464

[bb30994]

It's clear that when there's a slot defined and no GPU is present, the client doesn't know what to do and it's unfortunate that it doesn't give you the option to edit the configuration. How about allowing the client to continue with a message that reads

Option "gpu-index" has no default and cannot be set
Slot deleted.

I'm not sure how the client will deal with the issue if that's the only slot. Can a config ever happen that has zero slots?

[informatorius]

FAHcontrol should not change configuration itself but just don't freeze, so user can change the config.
FAHclient also ignores the faulty slot.

[bb30994]

You have created an impossible situation. Your configuration says that you have one slot (a GPU slot) but you have zero supported GPUs. What's FAH supposed to do?

FAH might be able to start if you had a functional CPU slot, allowing you to reconfigure a GPU slot, but that, too, gives FAHClient more authority to discard the present config.

Reinstall FAHClient. It might be smart enough to discard the defective config, but I doubt it. The only option I can think of is to reinitialize a default configuration.

[ProDigit]

Fahcontrol should give the option to adjust the slots, or reset to default value of CPU only in that moment. It's dependency on an internet connection, prevents anyone from adjusting those parameters, both in windows and Linux.

This could be a major issue for multi GPU servers, with 1 GPU going bad.

A small fix like this would prevent a majority of users to have to go through the trouble of uninstalling and reinstalling FAH

It's a small fix, I suggest switching to higher priority, unless the new Control app/program will have this fixed.