We have moved to a new Sailfish OS Forum. Please start new discussions there.
27

[3.3.0] Email client often unresponsive

Tracked by Jolla (In release)

asked 2020-04-06 10:15:04 +0200

cy8aer gravatar image

updated 2020-04-29 09:29:50 +0200

With the new update the email client is unresponsive often.

Example:

Cover shows: last update 13 hours ago (should update hourly). Clicking on it creates black window and warning: Mail client does not respond - wait/kill.

[Update] What I learned now: don't press the update button. Automatical updates work - and don't select update menu item. (of course: still buggy in 3.3.0.16)

edit retag flag offensive close delete

Comments

Mine will often fetch mails like what seems forever.

Kopekenscheich ( 2020-04-06 12:01:40 +0200 )edit

I'm also experiencing the same on Jolla 1. It's happening only since the update to 3.3.0.14

duvi ( 2020-04-06 12:39:09 +0200 )edit

Confirmed with XA2 (h3113). It already starts to struggle right after booting. I don't see anything specific in journalctl. Anything I can do to see debugging info?

Marcel Pol ( 2020-04-06 13:57:25 +0200 )edit

Mine couldn't update / sync Google client any longer for some reason and I didn't get any email at all. Trying to manually sync or press "update / refresh" didn't do the trick, it just stated that couldn't be refreshed. I removed the Google account and added it again and email started to work normally again. This on XA2 Dual-Sim running 3.3.0 too.

Sakke ( 2020-04-06 17:07:01 +0200 )edit

Great!

Spam Hunter ( 2020-04-06 22:00:10 +0200 )edit

3 Answers

Sort by » oldest newest most voted
13

answered 2020-04-06 18:45:27 +0200

mousse04 gravatar image

Hi guys,

I've opened a ticket at Jolla customer support. for this already. They told me that they have opened a ticket in their internal database

edit flag offensive delete publish link more

Comments

3

That's a good thing because while the mail client never was anything to write home about, it now has become downright unusable. Syncing takes forever now despite ceteris paribus. I even removed and added my accounts again to no avail.

Kopekenscheich ( 2020-04-11 12:03:36 +0200 )edit
3

answered 2020-06-08 16:59:59 +0200

friikki218 gravatar image

I have done some testing and sent reports to Jolla HQ in Tampere Finland. They have ticket open and said that hopefully this problem will be solved in the next release 3.4.0 to be announced late summer.

edit flag offensive delete publish link more
2

answered 2020-06-08 21:24:52 +0200

duvi gravatar image

updated 2020-06-08 21:27:53 +0200

This is very sad. They introduce a bug, not in some new application or feature, but in a very basic existing application, as basic as calling, rendering it basically useless (maybe not under all circumstances, but definitely for several users). We report the bug immediately when the pre-release version is out, so they could have time to fix it before the final release. It doesn't get fixed in the final release. Isn't it what pre-release versions are made for? To report / fix bugs before the release gets public?

And now 2 months later it turns out we need to wait for another 2-3 months to get it hopefully fixed? The e-mail application with one simple imap account that has been working fine for 5 years? Unusable for like half a year, in 2020?

Come on, this is really nonsense. This is the first time I'm rushing out on Jolla, but I can't keep it inside ):

edit flag offensive delete publish link more

Comments

I finally decided to kick the native email client and use K9. It is a shame that jolla needs more than 2 month to repair a daily needed program. Bye Bye Sailfish, welcome LOS.

dirksche ( 2020-06-08 23:21:54 +0200 )edit

There are more bugs outside of the email app. With Rokua, Jolla shot himself. I switched to FairEmail. Shall we really wait until late summer? Why? Things got better and important bugs were fixed immediately. Jolla, look here:

3.0.1.14 - Sipoonkorpi - 29 Jan 2019 3.0.1.13 - Sipoonkorpi - 14 Jan 2019 3.0.1.11 - Sipoonkorpi - 02 Jan 2019 3.0.0.11 - Lemmenjoki - 03 Dec 2018 3.0.0.8 - Lemmenjoki - 06 Nov 2018 3.0.0.5 - Lemmenjoki - 29 Oct 2018 2.2.1.23 - Nurmonjoki - 02 Oct 2018 2.2.1.20 - Nurmonjoki - 24 Sep 2018 2.2.1.19 - Nurmonjoki - 14 Sep 2018 2.2.1.18 - Nurmonjoki - 31 Aug 2018 2.2.0.29 - Mouhijoki - 30 May 2018 2.1.4.15 - Lapuanjoki - 09 Apr 2018 2.1.4.14 - Lapuanjoki - 23 Feb 2018 2.1.4.13 - Lapuanjoki - 16 Feb 2018 2.1.4.12 - Lapuanjoki - 12 Feb 2018 2.1.3.7 - Kymijoki - 26 Oct 2017 2.1.3.5 - Kymijoki - 11 Oct 2017 2.1.3.3 - Kymijoki - 06 Oct 2017 2.1.2.3 - Kiiminkijoki - 20 Sep 2017 2.1.1.26 - Jämsänjoki - 24 Aug 2017 2.1.1.25 - Jämsänjoki - 18 Aug 2017 2.1.1.24 - Jämsänjoki - 27 Jul 2017 2.1.1.23 - Jämsänjoki - 17 Jul 2017 2.1.1.12 - Jämsänjoki - 15 May 2017 2.1.0.11 - Iijoki - 29 Mar 2017 2.1.0.10 - Iijoki - 20 Mar 2017 2.1.0.9 - Iijoki - 03 Feb 2017 2.0.5.6 - Haapajoki - 14 Dec 2016 2.0.4.14 - Fiskarsinjoki - 04 Nov 2016 2.0.4.13 - Fiskarsinjoki - 04 Nov 2016 2.0.3.14 - Espoonjoki - 26 Jul 2016 2.0.3.11 - Espoonjoki - 06 Jul 2016 2.0.2.51 - Aurajoki - 23 Aug 2016 2.0.2.48 - Aurajoki - 12 Jul 2016 2.0.2.47 - Aurajoki - 30 Jun 2016 2.0.2.45 - Aurajoki - 08 Jun 2016 2.0.2.43 - Aurajoki - 13 May 2016 2.0.1.11 - Taalojärvi - 26 Apr 2016

4carlos ( 2020-06-10 06:37:26 +0200 )edit
Login/Signup to Answer

Question tools

Follow
10 followers

Stats

Asked: 2020-04-06 10:15:04 +0200

Seen: 1,002 times

Last updated: Jun 08 '20