Hello,

 

Yes, you cannot easily fall in this bug!

 

So, SOGoRefreshViewCheck is a user setting, meaning it can be changed by the 
user in its preferences. Putting a user setting in the sogo.conf does not force 
the value for the users. However, when a new user logs in for the first time, 
its preferences will take all the default values, and the user settings found 
in sogo.conf.

SOGoRefreshViewCheck tells at what interval the view is refreshed with a 
special value “manually”. The front code what just checking if this value was 
not “manually”, otherwise it was assuming it was a correct number in minutes.

Your value was not “manually” but not a number either. This being not a number, 
I think the angularjs timeout 
(https://docs.angularjs.org/api/ng/service/$timeout) function is taking the 
default value for the delay being 0 milliseconds. Hence the infinite loading 
loop.

 

I’ve made a fix for that available tomorrow.

 

Cheers,

-- 

Quentin Hivert || Alinto || R&D Lead Developer 

19 Quai Perrache 69002 Lyon

 <http://www.alinto.com> www.alinto.com

 

From: [email protected] <[email protected]> On Behalf Of Rolf Bode-Meyer
Sent: samedi 5 juillet 2025 20:45
To: [email protected]
Subject: [SOGo] Loading circle loads forever for new users

 

Hi there,

 

I ran into an issue that cost me hours to solve. But I can't wrap my head 
around it if it's a general bug.

 

I'm running a SOGo instance for me and my family on my home server for years 
now (now 5.12.2 but 5.11.4 when I discovered the problem) on Debian (currently 
Bookworm). Logging in with existing users and using the web UI wasn't any 
problem. Last week I logged in the first time with a new account I created 
minutes before on my OpenLDAP directory.

And in SOGo web UI the load circle loads forever, sometimes UI elements flicker 
and the whole UI is nearly unresponsive (in Firefox as well in Edge). This 
happens for mail view, for address book and for caleandar view.

 

Finally I compared the new accoutns config with an older one and noticed that 
the working one had

SOGoRefreshViewCheck = manually;

but the new one

SOGoRefreshViewCheck = manual;

 

Changing is to manually for the new one and the problem is gone.

 

This is reproducable with any account which has never logged in to SOGO or 
whose config has been removed.

 

Now what boggles me is that nobody else seems to have discovered that problem 
as I wasn't able to find a reference to it online. What might have caused it 
only on my installation and how to fix it in general?

 

Regards,

Rolf

Reply via email to