Discussion:
[Subsurface-divelog/subsurface] Cannot connect on first launch after update on Windows (#1499)
tormento
2018-07-12 16:29:21 UTC
Permalink
Had you the update request prompt?

Firewall is not an issue as I don’t have any. Plus it works ok after second
execution on. There is some internal timeout I think.

Il giorno gio 12 lug 2018 alle 17:15 Lubomir I. Ivanov <
@tormento <https://github.com/tormento>
i've tried reproducing the steps with the latest master and with the
continuous build binaries and i cannot get the first cloud connection to
fail on Windows 7.
do you have a firewall or a proxy installed; i'd blame that on a
networking issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/Subsurface-divelog/subsurface/issues/1499#issuecomment-404547787>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACPiqe-AgJUElGnt5upNPmsoywnvTejcks5uF2f-gaJpZM4VMtno>
.
tormento
2018-07-13 13:02:35 UTC
Permalink
May I ask which is the sense of your hint?

I don't use installer, thus the registry is not touched after every update.
It seems very strange that you have to reenter credentials every time too.

I keep on being convinced that the update check window is the culprit of
the problem. If some of the developers could disable it for nightly, we
would have a proof or not of what I am saying.

Il giorno ven 13 lug 2018 alle ore 14:37 Lubomir I. Ivanov <
No need to re-enter credentials. And yes, the error is red.
in my case i always have to re-enter credentials.
- close subsurface
- open the start menu and enter "regedit" to start it
- in regedit open HKEY_CURRENT_USER / Software
- rename the Subsurface folder to Subsurface_ (this will backup your
settings)
- start subsurface
see if the error happens again.
NOTE: you can always rename your old settings Subsurface_ in regedit back
to Subsurface, but make sure any new Subsurface folders are deleted in
there first.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/Subsurface-divelog/subsurface/issues/1499#issuecomment-404821127>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACPiqT3fgxvL6jn6vK47pa0rb067G7xYks5uGJRtgaJpZM4VMtno>
.
Steve
2018-07-18 15:02:54 UTC
Permalink
From: subsurface <subsurface-***@subsurface-divelog.org> On Behalf Of tormento
Sent: Saturday, 14 July 2018 12:03 AM
To: Subsurface Mailing List <***@subsurface-divelog.org>
Subject: Re: [Subsurface-divelog/subsurface] Cannot connect on first launch after update on Windows (#1499)



May I ask which is the sense of your hint?



I don't use installer, thus the registry is not touched after every update. It seems very strange that you have to reenter credentials every time too.



I keep on being convinced that the update check window is the culprit of the problem. If some of the developers could disable it for nightly, we would have a proof or not of what I am saying.



Il giorno ven 13 lug 2018 alle ore 14:37 Lubomir I. Ivanov <***@github.com <mailto:***@github.com> > ha scritto:

No need to re-enter credentials. And yes, the error is red.

in my case i always have to re-enter credentials.

you can try this:

* close subsurface
* open the start menu and enter "regedit" to start it
* in regedit open HKEY_CURRENT_USER / Software
* rename the Subsurface folder to Subsurface_ (this will backup your settings)
* start subsurface

see if the error happens again.

NOTE: you can always rename your old settings Subsurface_ in regedit back to Subsurface, but make sure any new Subsurface folders are deleted in there first.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <https://github.com/Subsurface-divelog/subsurface/issues/1499#issuecomment-404821127> , or mute the thread <https://github.com/notifications/unsubscribe-auth/ACPiqT3fgxvL6jn6vK47pa0rb067G7xYks5uGJRtgaJpZM4VMtno> . <Loading Image...>







I can confirm I see the same thing on the latest windows 10 builds only the first time after installation ever other time after that works well so suspect something is not initialised properly for first run?



C:\Program Files (x86)\Subsurface>subsurface.exe -vvv



C:\Program Files (x86)\Subsurface>

Subsurface v4.8.1-39-gb7bb9b417775,

built with libdivecomputer v0.7.0-devel-Subsurface-NG (8f4945dc1e83c53ed9d2cdbaaa16e7b117df1f32)

built with Qt Version 5.9.2, runtime from Qt Version 5.9.2

built with libgit2 0.26.0



/SNIP



git storage: Sync with cloud storage

delete proxy setting

Cloud storage: checking connection to cloud server

Checking cloud connection...

git storage: Waiting for cloud connection (1 second(s) passed)

git storage: Waiting for cloud connection (2 second(s) passed)

git storage: Waiting for cloud connection (3 second(s) passed)

git storage: Waiting for cloud connection (4 second(s) passed)

git storage: Cloud connection failed

connection test to cloud server failed QNetworkReply::NetworkError(ProtocolInvalidOperationError) "Error transferring https://cloud.subsurface-divelog.org//make-latte?number-of-shots=3 - server replied: I'm a teapot" 418 "Linus does not like non-fat milk"

Cloud storage: unable to connect to cloud server

git storage: Can't reach cloud server, working with local data

git storage: Load dives from local cache



Steve

Loading...