Revert and rename only in the UI
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Aug 25 2018
Aug 24 2018
Aug 23 2018
Sorry if I wasn't clear enough in the first message.
In D15001#313863, @rnicole wrote:Renamed the "GMail" account to "Google". It seems that those who already have a Google account can remove their account from the command-line only, and then add it again from Kube
Renamed the "GMail" account to "Google". It seems that those who already have a Google account can remove their account from the command-line only, and then add it again from Kube
Aug 22 2018
great =)
Let's figure out why carddav doesn't work and rename in the Ui only to Google.
Aug 21 2018
I think the only usable approach will be to decrypt messages as they arrive. Otherwise things like search etc. break.
To re-secure the indexes we *should* probably encrypt the indexes using AES or something else that is fast, but for an initial implementation I don't care too much.
Use full-disk encryption if necessary.
Aug 18 2018
Aug 16 2018
At the moment we avoid starting kube twice by using a lockfile (in flatpak only).
Aug 14 2018
We now check the http header to have a last-modified date within the last 24h.
Aug 13 2018
The problem was that I had multiple flatpaks running in the background which failed to shut-down (yet another problem).
[I] ⋊> flatpak run --command=kube com.kubeproject.kube 12:18:14 Log: kube.store : Upgrading... Warning: kube.storage_lmdb : Failed to to open transaction: "Resource temporarily unavailable" true 0x0 Warning: kube.storage_common : Database error in "{2b163529-9ecf-45dd-a8a7-16b69c648c08}" , code 0 , message: "Error while opening transaction: Resource temporarily unavailable" SIGSEV received 1 0x4053d8 kube() [0x4053d8] 2 0x3153a330b0 /lib/libc.so.6() [0x3153a330b0] 3 0x7f2966d28f04 mdb_txn_begin + 20 4 0x7f297a0a4843 Sink::Storage::DataStore::NamedDatabase::Private::openDatabase(bool, std::function<void (Sink::Storage::DataStore::Error const&)>) + 1283 5 0x7f297a09f8ed Sink::Storage::DataStore::Transaction::openDatabase(QByteArray const&, std::function<void (Sink::Storage::DataStore::Error const&)> const&, bool) const + 493 6 0x7f2979f99cf6 Sink::Storage::DataStore::databaseVersion(Sink::Storage::DataStore::Transaction const&) + 134 7 0x7f2979c6bb4f /app/lib/libsink.so.0.8(+0x851b4f) [0x7f2979c6bb4f] 8 0x7f2979c6b9b2 /app/lib/libsink.so.0.8(+0x8519b2) [0x7f2979c6b9b2] 9 0x7f2979c6b7d4 /app/lib/libsink.so.0.8(+0x8517d4) [0x7f2979c6b7d4] 10 0x7f297a694eaa std::function<KAsync::Job<void> (QSharedPointer<Sink::ApplicationDomain::SinkResource>)>::operator()(QSharedPointer<Sink::ApplicationDomain::SinkResource>) const + 106 11 0x7f297a694ca2 /app/lib/libkubeframework.so(+0x11bca2) [0x7f297a694ca2] 12 0x7f297a693c74 /app/lib/libkubeframework.so(+0x11ac74) [0x7f297a693c74] 13 0x7f297a69402e KAsync::Private::Executor<QSharedPointer<Sink::ApplicationDomain::SinkResource>, void, QSharedPointer<Sink::ApplicationDomain::SinkResource> >::runExecution(KAsync::Future<QSharedPointer<Sink::ApplicationDomain::SinkResource> > const*, QSharedPointer<KAsync::Private::Execution> const&, bool) + 318 14 0x7f297a6938c0 KAsync::Private::Executor<QSharedPointer<Sink::ApplicationDomain::SinkResource>, void, QSharedPointer<Sink::ApplicationDomain::SinkResource> >::exec(QSharedPointer<KAsync::Private::ExecutorBase> const&, QSharedPointer<KAsync::Private::ExecutionContext>) + 816 15 0x7f297a627ff5 KAsync::Private::Executor<void, void>::exec(QSharedPointer<KAsync::Private::ExecutorBase> const&, QSharedPointer<KAsync::Private::ExecutionContext>) + 261 16 0x7f297a690828 KAsync::Job<void, QSharedPointer<Sink::ApplicationDomain::SinkResource> >::exec() + 104 17 0x7f297a68fc17 KAsync::Future<void> KAsync::Job<void, QSharedPointer<Sink::ApplicationDomain::SinkResource> >::exec<QSharedPointer<Sink::ApplicationDomain::SinkResource> >(QSharedPointer<Sink::ApplicationDomain::SinkResource>) + 407 18 0x7f297a68f7d2 /app/lib/libkubeframework.so(+0x1167d2) [0x7f297a68f7d2] 19 0x7f297a68f534 /app/lib/libkubeframework.so(+0x116534) [0x7f297a68f534] 20 0x7f297a6380da std::function<KAsync::Job<void> (QList<QSharedPointer<Sink::ApplicationDomain::SinkResource> >)>::operator()(QList<QSharedPointer<Sink::ApplicationDomain::SinkResource> >) const + 106 21 0x7f297a637ed2 /app/lib/libkubeframework.so(+0xbeed2) [0x7f297a637ed2] 22 0x7f297a6368d4 /app/lib/libkubeframework.so(+0xbd8d4) [0x7f297a6368d4] 23 0x7f297a636cae KAsync::Private::Executor<QList<QSharedPointer<Sink::ApplicationDomain::SinkResource> >, void, QList<QSharedPointer<Sink::ApplicationDomain::SinkResource> > >::runExecution(KAsync::Future<QList<QSharedPointer<Sink::ApplicationDomain::SinkResource> > > const*, QSharedPointer<KAsync::Private::Execution> const&, bool) + 318 24 0x7f297a636520 KAsync::Private::Executor<QList<QSharedPointer<Sink::ApplicationDomain::SinkResource> >, void, QList<QSharedPointer<Sink::ApplicationDomain::SinkResource> > >::exec(QSharedPointer<KAsync::Private::ExecutorBase> const&, QSharedPointer<KAsync::Private::ExecutionContext>) + 816 25 0x7f2979cb79dc KAsync::Private::Executor<void, Sink::Store::UpgradeResult>::exec(QSharedPointer<KAsync::Private::ExecutorBase> const&, QSharedPointer<KAsync::Private::ExecutionContext>) + 268 26 0x408aa5 kube() [0x408aa5] 27 0x4070c8 kube() [0x4070c8] 28 0x405ffe kube() [0x405ffe] 29 0x3153a20291 __libc_start_main + 241 30 0x404f1a _start + 42 Sleeping for 10s to attach a debugger: gdb attach 2
Actually, it didn't resolve itself. It start fine if I first start bash, but not if I run kube directly in the flatpak. One notable difference is that if I start kube directly it will always end up with the same pid inside the container, but if bash is started first we of course end up with another one.
Aug 10 2018
Aug 4 2018
Aug 3 2018
Jul 31 2018
For now we just save drafts and try to avoid crashing.
login name and email address are now separate fields. Separate loginnames for imap and smtp is very unlikely to happen in the UI, but would be doable anyways by editing the configuration files.
We already have a basic editor and support for lists is doable on top of what we have.
This has been solved by removing the button.
Jul 27 2018
So; the lmdb assumption that pid's are unique simply no longer holds with pid namespaces. I suppose this could be seen as an lmdb bug.
I'm also not sure how well the whole separate process for synchronizers works if we were able to start multiple flatpaks. The sockets would have to be shared, and then each synchronizer would just live on in the sanbox of the kube process that started it...
Jul 23 2018
I pushed the fix to master.
Jul 21 2018
Tiles before adjustment.
Jul 20 2018
A trial with a lowered title + screenshot included on top (positioning could be improved a little still).
Jul 17 2018
Jul 16 2018
There does not seem to be any way to override auto-key-retrieve programatically => documentation issue.
Jul 15 2018
And the main problem with that seems to be "keyserver-options auto-key-retrieve" in gpg.conf. Without it things are much more responsive it seems.
Jul 14 2018
Jul 12 2018
The main bottleneck seems to be signature verification and decryption.
And this is what geary does (I am not proposing that we should copy this behaviour in any shape or form):
Jul 11 2018
Here's an attempt with a translucent button that get's a bit more opaque on hover
Jul 7 2018
It looks better live than in the gif, but:
Jul 6 2018
First version:
A downside of dimming/focusing part of the application is that only that part is really usable during the search. This shouldn't be a problem for maillist + conversationview, but if we do the same for the folderlist you have to finish the search to be able to view the contents of the folder properly. Not sure how problematic that will end up being.
That was already fixed.
This might be a flatpak incompatibilty.
This seems to be the EAGAIN error code that is returned from some operation that lmdb does from mdb_txn_begin
- mdb_reader_pid (via mdb_txn_renew0) is doing some fcntl calls.
- sem_wait is being called (via LOCK_MUTEX -> LOCK_MUTEX0). EAGAIN should only returned from sem_try_wait, so this shouldn't actually be a source.
A more useful variant of the backtrace:
Jul 5 2018
Jul 4 2018
We now start an extra gpg-agent with a fixed pinentry to work around the problem.
Jun 20 2018
Another thing to put in the “expert imap account” setting would be that the used e-mail address and log in are not necessarily the same. For example, I get e-mails to the same IMAP server on both my private address and my FSFE address, but neither are the actual username for the server.