Going to another conversation and loading again fixed it. Maybe something with the unread state?
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Mar 29 2018
Mar 27 2018
Mar 12 2018
Mar 8 2018
This bug was fixed while re-writting the mailcrypto in the pkey import / export patch
Mar 5 2018
Mar 2 2018
Mar 1 2018
Set up as follows with parameters as suggested above as you have done but there is no option for further settings in Kube (yet)
Feb 28 2018
The settings as described here work for me:
https://www.fastmail.com/help/technical/servernamesandports.html
Feb 26 2018
This has been resolved by providing an error message when we fail to connect.
Nov 15 2017
Should be solved now. We don't use platform plugin anymore, only platform theme.
Oct 11 2017
Oct 9 2017
Oct 8 2017
This is now fixed since we switched to TextEdit (instead of TextArea)
how to reproduce:
Oct 2 2017
Sep 21 2017
yes
Sep 19 2017
Sep 15 2017
Sep 13 2017
The correct behavior would be to have some sort of visual indicator that there are external images and offer an option to download them?
Sep 12 2017
Sep 7 2017
Sounds like a plan =)
What I mean and what we need is:
Sep 6 2017
Found the culprit. The symlink target was missing. Thanks for the report!
Not sure I understand you correctly.
- We need the patch for flatpak to work, right (Right now I can choose between working openUrl and a crashing webengine)?
- You suggest that we just patch the qt copy in the kde runtime until 5.11 is released? (I would agree that this would be nice to bridge the time until 5.11 is out)
Well, unless we patch our Qt in KDE runtime until 5.11 is released, I don't see this as a problem.
I take it this essentially means no functional flatpak until qt 5.11 or so?
Sep 4 2017
Oh, also I tested it and I confirm it works for me.
The issue has been fixed upstream and the runtimes rebuilt.
The icon is clearly there:
flatpak run --command=find org.kde.kube /usr /app -name password-show-on.svg* /usr/share/icons/breeze-dark/actions/16/password-show-on.svg /usr/share/icons/breeze-dark/actions/24/password-show-on.svg /usr/share/icons/breeze-dark/actions/22/password-show-on.svg /usr/share/icons/breeze/actions/16/password-show-on.svg /usr/share/icons/breeze/actions/24/password-show-on.svg /usr/share/icons/breeze/actions/22/password-show-on.svg /app/share/icons/kube/actions/16/password-show-on.svg /app/share/icons/kube/actions/24/password-show-on.svg /app/share/icons/kube/actions/22/password-show-on.svg
Sep 2 2017
This will require:
- Detect outlook
- Search for uids in batches (e.g. 2000 at a time)
- Fetch messages in the same batches.
There was a bug that broke account status monitoring when creating the account for the first time. This has been fixed now.
Aug 31 2017
Yes.
Yes please.
Should we close this until we find any further evidence then?
Yes.
After reinstalling Kube, It seems that I had a PEBCAK moment.
I can't reproduce that by disconnecting my internet:
- Tried an initial sink -> works
- Disconnected the internet and synced again -> results in disconnected state and error message after 40s timeout
- Connected the internet again and synced again -> works and clears the disconnected state
Installed via :
In T6899#108593, @cmollekopf wrote:"Disconnected" simply means that the last operation couldn't reach the server. We don't really maintain much state beyond that.
F5 or clicking the folder always triggers a sync, and if that is successful it will clear the "Disconnected" message you see in the lower left corner.
Closing and reopening Kube should definitely not be necessary.Just to make sure I understand correctly:
- You opened Kube and some operation failed so you ended up in the "Disconnected" state (as signified by the status bar in the lower left corner).
- You tried clicking the folder and pressing F5 but that did not result in any UI changes.
- After a restart clicking the folder again triggered a sync as usual
If that is the case I'll have to try and reproduce it.
If you can reproduce it the log output from step 2 would be useful, clicking the folder or pressing F5 should result in at least some debug output. Also try waiting for 40s to see whether an open connection times out.
Good catch, the bugreport is indeed likely to be the issue. I assume it works with some folders that contain only a few messages?
Unlikely to be flatpak specific.
Unlikely to be flatpak specific.
"Disconnected" simply means that the last operation couldn't reach the server. We don't really maintain much state beyond that.
F5 or clicking the folder always triggers a sync, and if that is successful it will clear the "Disconnected" message you see in the lower left corner.
Closing and reopening Kube should definitely not be necessary.
Thanks for the report. I just checked and the icon should be available from looking at the code. Did you get flatpak from the kde repository or did you build it yourself?