https://bugs.kde.org/show_bug.cgi?id=335703
--- Comment #22 from Wolfgang Bauer <[email protected]> --- I tried again now with a completely fresh User account, and knotes (4.13.3) did behave ok: - when creating a new note, it opened a dialog asking in which collection the note should be stored (offering to set it as default as well) - afterwards it also asked whether that collection should be enabled, so that its notes are visible. It did show the same behavior when I copied over old (legacy) notes to a fresh user account and skipped the offered migration. I.e. when creating a new note, it asked where to store it and whether to enable that collection. The second case definitely behaved differently when I tried with 4.13.2 (see comment#18 and comment#19), so either this got fixed in the meantime, or there's another factor causing the problem. What I can still reproduce though is that creating new notes silently fails if the default collection doesn't exist any more, f.e. because the user deleted it in Systemsettings->Personal Information->Configure Akonadi Resources. IMHO knotes should ask for a collection in this case as well. Steps to reproduce: - set a default collection to save notes to in knotes' settings - make sure knotes works, i.e. you can create notes - quit knotes (not sure if this is necessary but I did it in my test) - open systemsettings->Personal Information->Configure Akonadi Resources and delete the akonotes resource that has been set as default in step#1 - start knotes again When you now try to create a new note, nothing happens. You only will get the message 'Error during fetch: "Collection xxx does not exist"' if you started it in a konsole. It should show a dialog in this case as well. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
