I think you’re misunderstanding what I’m saying. You’re saying (I think) 192.168… is getting set by virtue of WHONIX=1 in environment / while I was saying / hoping / asking that unsetting the value permanently clears the problem going forwards?
If you’re saying it will keep coming back, regardless of what you’re doing (due to WHONIX=1) that isn’t entirely explicit.
[‘Simple’ work around would be to change menu entry to 'WHONIX=0 torbirdy - if the behaviour between 0/1 is that targeted.]
er/or, i.e. If none or system proxy setting is kept (vs manual), whether 192.168… is stuffed in there won’t matter.
``- actually … that’s doable within base whonix image. If torbirdy isn’t installed, wrapper will never get called. Once it is (presumably with newer ‘fixed’ version), wrapper will get replaced. In the mean time, updates to current installs would get ‘fixed’. (?)
[quote] Typing “unset WHONIX” … do you know how linux environment variables work?[/quote] Yep. Alternate workaround is, like the anondist’s … wrap icedove in a script / link. (Again, if WHONIX=0 is that surgical.)
[quote]There is no Whonix install time TorBirdy setting. This is only a feature of TorBirdy. Fixing this in Whonix before the TorBirdy update would require some cumbersome hack.
The version on mozilla addons and the torbirdy homepage is newer than the version in Debian stable. You can also try if this is fixed in the latest version. It works for me with 0.1.4.
Interesting, thank you / good to know.
Else I suppose I’d have to change the source within the current installation.
[I dislike going ‘non-standard’ … every customization is one more forgettable fiddly bit at every update, change, etc.]
To your point, a ‘bug’ … is. (It is what it is / situation unavoidable.)