[knotes] [Bug 334138] when creates a new note knotes create two and then a warning appear and the note is not saved

[Wolfgang Bauer]

https://bugs.kde.org/show_bug.cgi?id=334138

Wolfgang Bauer <wbauer at tmo.at> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wbauer at tmo.at

--- Comment #2 from Wolfgang Bauer <wbauer at tmo.at> ---
(In reply to comment #1)
> but doesnt
> save it, I suppose akonaditray popup this notification:
> notes cannot write to mail file
> /home/user/.local/share/akonadi_aconotes_resource_0/tmp/a-long-number-and-
> the-host-name
> and this folder doesn't exist, if I create a new agent in akonaditray and
> assign it to the default in knote config knote works well

I got the same error messages here after the successful migration (with a
different folder though, something in ~/local/share/notes/). Everything worked
fine, so I didn't bother until now.
But now I noticed that the notes don't get saved to the hard disk at all (they
only exist in the akonadi database), because that folder that the akonotes
resource points to didn't exist (and didn't get created either).

I tried to reproduce the problem by redoing the migration a few times, and I
found out this:
- If I start knotes from a Konsole, the folder for the new resource is created,
and everything works fine without any error messages
- But: if I start knotes from the K-Menu (the first time, when it should do the
migration), the folder DOES NOT get created. Akonadi fails to store the notes,
and akonaditray gives those annoying error messages.

This seems to be reliably reproducable here, I tried about 10 times now or
more.

So I guess the question is, what's the difference if knotes is started in
Konsole vs. it is started by K-Menu? Why does it fail to create the folder in
the second case?

Oh, and btw, I started knotes without akonadi running now by mistake, then the
migration FAILED (the migrator showed some message about "Could not find root
collection"). Some kind of timeout maybe because akonadi needed too long to
start? This is also reproduceable, I will file a new bug about this.

-- 
You are receiving this mail because:
You are the assignee for the bug.