Edit >> Settings "Segmentation Fault" Init fresh SD wallet Connection Error on startup. #20
Closed
opened 3 years ago by oDinZu
·
12 comments
Loading…
Reference in new issue
There is no content yet.
Delete Branch '%!s(MISSING)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
**General: **
On launch of SD, it says connection error, then says edit user/pass in edit >> settings...I goto settings and the application crashes.
Terminal Logs:
gdb bt logs:
@oDinZu looks like a valid bug.
Something is wrong with
/home/username/.local/share/Hush/SilentDragon/
, does the directory exist?Sweet! I found the sd.debug file with your guidance and it is why SD doesn't work. It is looking for the .komodo directory and I am using hush3:dev.
On init of SD:
@odzinzu good find, SD+SDL server have not yet been updated to work with
dev
branch. I will add comments to your other PR@oDinZu can you recheck this with hushd 3.9.0 and SD
dev
branch and close it if it's no longer relevant? Thanks@oDinZu plz let me know if you still see problems.
hushd
3.9.0 anddev
branch is now compatible with SDdev
branch, we could use more testing before 1.3.0 releaseOn a fresh build of SD, this problem is solved.
I had a similar problem just now on master SD branch and seen you updated it. 😺
On building SD:dev and launching the application on my RPi v8 ARM, no errors or segmentation faults.
I have connected to peers and everything seems to work. I am able to goto edit >> settings without crashing the application.
Ok, closing for now
On my newly born Qt5.15.2 bins for SD Ubuntu 18.04, I receive the segmentation fault on both: master and dev for SilentDragon fresh installs.
Init SD looks like this on 18.04 Ubuntu.
Going to GUI edit >> settings >> Segmentation fault (core dumped)
@odinzu that last debug output helped, my current guess is now that price stats has code which lacks error checking. Is there any way that this machine was disallowed to connect to port 443 of a host, maybe by a VM network filter?
@odinzu if you are able to get a coredump and provide a backtrace, that would also be helpful
@odzinu I added a bit more logging on
dev
branch if you want to run with that, that will help pinpoint the issue a bit more