![]() persistence/settings.cpp:2411 : Debug: Creating new profile settings in "/home/user/.config/tox//aaaaaa.ini" main.cpp:251 : Debug: commit: build without git persistence/settings.cpp:133 : Debug: "Loading settings from :/conf/qtox.ini" persistence/settings.cpp:129 : Debug: No settings file found, using defaults What I mean is even if I had known I would need to set the connection options again after making a new account, when I first load into the new account, it would attempt to connect to the tox network over my default IP address until I go and manually change things (unless I disable my internet, load into the new profile, change to tor, and then reenable internet).Įdit: Was just reading over () and saw the example for doing it with toxic - " toxic –force-tcp –SOCKS5-proxy 127.0.0.1 9050" Not only would this allow you to easily share this setting between accounts if you choose (such as changing your qTox shortcut to include them thus making any profile load those connection settings), but it would allow you to easily use your chosen settings on newly created accounts without ever having to connect to tox over a connection you don't want to. I thought about ways this might be able to be changed, and the best one I could think of are launch options/cli flag settings to set connection settings, like proxy type/IP/UDP settings etc on launch. I eventually realized it was because I made a new account a few months ago and never set the same connection settings, and connection settings are saved on a per account basis. QTox version: (version numbers in menu … `Settings → About`)Īt first I thought I had a bug that deleted settings, because I checked my advanced settings after updating and noticed my connection wasn't set to go through tor and had a random port instead of 9050. twstrike/coyim/gui/account.go:169 where it freeze: twstrike/coyim/gui/account.go:170 +0x7fĬreated by /twstrike/coyim/gui.(*gtkUI).showServerSelectionWindow.func1 twstrike/coyim/gui/registration.go:83 +0x1a7 Panic: runtime error: invalid memory address or nil pointer dereference (CoyIM:3353): dbind-WARNING **: 17:17:40.507: Error retrieving accessibility bus address: .ServiceUnknown: The name was not provided by any. Steps to reproduce very easy just try to make it work/connect normally and it just wont continue. Im testing CoyIM and … i discovered its not connecting either its freeze up on registration or shutdown itself. ![]() Whonix 15 going to be released soon based on Debian Buster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |