Knotes says about new format of notes, about converting used notes to new format but doing nothing. Reproducible: Always Steps to Reproduce: 1. Update current Arch linux with existing notes. 2. 3.
? So what is the problem ? What is the result ? What is expected ? etc.
Problem: Knotes looses all notes. I.e. klick onthe notes icon in try shows only string "Notes", fortunately I'm saved file with notes.
Right click on systray, con,figure->collections => select all notes collections -> apply
That's done first, but no effects, I'll restore all by the hand. But this update isn't correct.
(In reply to comment #3) > Right click on systray, con,figure->collections => select all notes > collections -> apply Sadly that doesn't work, as the notes located in ~/.kde/share/apps/knotes/ are never showing up. Also, the notes migration on first start of KMail in the KDE 4.13 release apparently doesn't migrate knotes either, it only migrates notebooks, e.g. what is in the Notes section
kmail doesn't migrate knotes. if you want to migrate notes launch knotes.
Knotes don't migrate existing notes too :) Source file exist without changes in ~/.kde4/share/apps/knotes/notes.ics
It's normal we don't change notes.ics
OK, but why knotes don't show any existing notes from there?
Oh well, I expressed myself badly, I meant the knotesmigrator that is launched when you first start kontact. Nothing is migrated, I have selected all notes sources in the configuration, and my notes don't show up at all. So something is wrong somewhere, could you please tell us what to do to get our knotes content back? I already had to restore everything manually last time, this is getting old...
Did you try knotes-migrator ?
(In reply to comment #11) > Did you try knotes-migrator ? Yes, and apparently that doesn't work either (mind you, it already didn't work when started on kontact first start, so no real surprise here): knotes-migrator knotesmigrator(14032)/kresources KRES::Factory::self: knotesmigrator(14032)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-myriam/ksycoca4" knotesmigrator(14032)/kresources KRES::ManagerImpl::ManagerImpl: knotesmigrator(14032)/kresources KRES::ManagerImpl::readConfig: knotesmigrator(14032)/kresources KRES::Factory::self: knotesmigrator(14032)/kresources KRES::ManagerImpl::readResourceConfig: "6qvKqWy7eW" knotesmigrator(14032)/kresources KRES::Factory::Private::resourceInternal: ( "file" , config ) knotesmigrator(14032)/kresources KRES::Factory::Private::resourceInternal: no such type "file" knotesmigrator(14032)/kresources KRES::ManagerImpl::readResourceConfig: Failed to create resource with id "6qvKqWy7eW" And I also tried the interactive mode and ended up with an empty GUI window and those two additional lines: Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon knotesmigrator(14062)/kresources KRES::ManagerImpl::~ManagerImpl: so unless there is a way to migrate that is not described anywhere, I have no idea what else I can do...
On an another comp migrator says that it depend from akonadiserver. This server was not initiated as useless.
Hmmm. Akonadi is enabled and running, Notes collection is selected, but knotes don't show it...
For me the same thing, after calling KNotes and selecting "Update now" message appears, and exit the program: knotes(21547)/libakonadi Akonadi::EntityTreeModelPrivate::firstFetchJobDone: "Unknown error." knotes-migrator does not return, If you need I can send the result of strace.
Akonadi works on my home comp, but knotes-migrator shows window without any functions. I.e. window appears but do nothing, and no log in a command string. May be that's result of notes in Russian?
Hello @all! :-) Same issue here After Updating (gentoo) the kde-packages from 4.12.4 to 4.13.0: * on first start the migration-wizard was launched by default asking me to import the knodes-Data. * After that, which was done immediately and without showing a result, no entries could bee found anymore as it seems nothing has been "imported" or included/referred from the old/original knotes entries * Probably interesting: knotes has not been started on login (or did not left opened) as normally configured in my profile * I checked in the knodes-settings for all possible collections to have them in, all empty as already reported on previous posts * 'knotes-migrator --interactive' also throws only an "empty" window. * ./kde4/share/apps/knotesmigrator/migration.log contains: [Mi. Apr 23 10:18:33 2014] Info : Starting migration... [Mi. Apr 23 10:18:34 2014] Info : Migration finished. * ./kde4/share/apps/knotes/notes.ics contains (still) all my notes * as also ./kde4/share/apps/knotes/notes/libkcal-* all the appearance settings per entry Does knodes probably expect the entries to be in another directory? And as workaround: can I import all my nodes afterwards, probably with the ics-file(-content)? Thank you for your precious work and for reading my questions!! :-) Sincerely, Thomas
Mine wouldn't migrate property either and every time Korganiser was launched, the KNotes migration window appeared. Think I solved it by changing the sources in KNotes, but will have to check when I get home.
In Preferences KNotes, you have to make sure that Notes is ticked under Collections.
>> In Preferences KNotes, you have to make sure that Notes is ticked under Collections. Yepp, as said, they are checked all there. But unfortunately no effect ;-(
Yes, me too, I have just upgraded from Kubuntu 12.04 to 14.04, I had a small number of notes which Knotes asked to import, I said "yes", but the notes were not imported.
Ah, rooting around. In .kde/share/apps/knotesmigrator - I had some application log messages that rival Microsoft for their helpfulness! [Mon Apr 21 17:26:11 2014] Info : Starting migration... [Mon Apr 21 17:26:11 2014] Info : Migration finished.
Open akonadiconsole look at if you have a resource "akonadi_akonotes_resource*" ?
OK. I admit it, I don't know what I'm doing. I'll take the risk anyway :) "Akonadi Console is purely a development tool. It allows you to view and change internal data structures of Akonadi. You should only change data in here if you know what you are doing, otherwise you risk damaging or losing your personal information management data. Use at your own risk!". Under the Agents tab, I have something called "Notes" with a green light and saying "ready". If I click on that, the details commentary says: Identifier: akonadi_akonotes_resource_0 Type: AkoNotes Status: Online, Idle Status Message: Ready Capabilities: Resource, Notes Mimetypes: text/x-vnd.akonadi.note
>> Open akonadiconsole look at if you have a resource "akonadi_akonotes_resource*" ? I have 4 online/ready jet, akonadi_akonotes_resource_[8-11] One (11) is named as "Lokale Notizen" as meant local notes with the native ressource/path set to "/home/tommi/.local/share//notes/OWgQhnfL0j" Can I probably copy my ics in there(?)
@Thomas, I doubt it, but "I don't know what I'm doing". Well done for finding the folder, I have the same folder and my one and only new note is there. I don't know why the developer(s) departed from the previous standard of putting the notes in a subfolder of .kde It will be interesting to hear what we are supposed to do now.
in tab "Browser" look at in "Lokale Notizen" if there is some notes into.
> in tab "Browser" look at in "Lokale Notizen" if there is some notes into. no there is no one, all "0" and there fore the reffered folder (/home/tommi/.local/share//notes/OWgQhnfL0j) is just not created still, as meant there doesn't exist a "OWgQhnfL0j " in "/home/tommi/.local/share//notes"
you can try to restart migration: rm -f ~/.kde/share/config/knotes-migratorrc knotes-migrator
(In reply to comment #29) > you can try to restart migration: > rm -f ~/.kde/share/config/knotes-migratorrc > knotes-migrator I already tried that as well, still doesn't work, same error. I now have 3 akonadi-akonote-ressources, and a knotes-migrator one, all are empty, and the ~/.kde/share/apps/knotes/notes.ics file is still there with all my notes, I just can't access them, and really, I need that stuff, this is part of my workflow... Looks like I will have to restore them manually, one by one...
* Well, what's about to import the old ics in one way? Exists there a method? * How will they be stored under that given resource "/home/tommi/.local/share//notes/OWgQhnfL0j"? * the knotes-migrator itself seems to have a problem (in our environment) obviously as also more reported to get an empty window (when started --interactive) and neither any output/log. Simply it ends very fast with a CR ^^
I can confirm this on openSUSE with KDE 4.13.0. knotes-migrator doesn't migrate my notes either, even when removing knotes-migratorrc and running it manually. Creating new notes works fine in KNotes, so it's no Akonadi setup issue. I suppose this is because there is no "Notes in Local File" KResource like there was in previous knotes versions. (/usr/share/kde4/services/kresources/knotes/local.desktop, /usr/lib64/kde4/knotes_local.so) After copying those 2 files to my system (from a previous knotes version), the migration completes successfully.
*** Bug 333902 has been marked as a duplicate of this bug. ***
I can confirm that copying these files, deleting knotes-migratorrc and running knotes-migrator solved the problem for me. (openSUSE 13.1, KDE 4.13.0) > (/usr/share/kde4/services/kresources/knotes/local.desktop, > /usr/lib64/kde4/knotes_local.so) > After copying those 2 files to my system (from a previous knotes version), > the migration completes successfully.
very interesting. Indeed I have this two files on my computer and it works. Ok it was removed when I migrated to akonadi. I will read it for 4.13.1 and increase migrator version to regenerate it. I will do it soon.
I am running Kubuntu 14.04 with kde 4.13.0 - I don't have either /usr/share/kde4/services/kresources/knotes or /usr/lib64 at all I tried deleting /.kde/share/config/knotes-migratorrc and that did make knotes try the migration again but nothing was migrated. Should you be in a certain folder when the migration is run?
I work to rewrote knotesmigrator. It will ready this week.
would like to say thank you for, to appreciate your work!
Git commit 69321dd246202d572ccba35ab36f9dd7d5a18925 by Montel Laurent. Committed on 28/04/2014 at 05:56. Pushed by mlaurent into branch 'KDE/4.13'. Fix Bug 333640 - Knotes version 4.13 don't inherit previous notes FIXED-IN: 4.13.1 M +48 -14 migration/knotes/knotesmigrator.cpp M +11 -5 migration/knotes/knotesmigrator.h M +0 -2 migration/knotes/main.cpp http://commits.kde.org/kdepim-runtime/69321dd246202d572ccba35ab36f9dd7d5a18925
it's fixed now I will increase version in knotes too to allow to automatic migrate them
Git commit 23164f2ac500463833a42253e6e282e9a6274b4a by Montel Laurent. Committed on 28/04/2014 at 06:00. Pushed by mlaurent into branch 'KDE/4.13'. increase migrate version number M +1 -1 knotes/utils/knoteutils.cpp http://commits.kde.org/kdepim/23164f2ac500463833a42253e6e282e9a6274b4a
it doesn't depend again kresources now so we will able to migrate knotes from 4.4 to KF5.
*** Bug 333989 has been marked as a duplicate of this bug. ***
*** Bug 334000 has been marked as a duplicate of this bug. ***
I can confirm that the migration is working now. Thank you! There was still one minor issue though. After the migration, knotes just quit here with the following message: m_agentInstance.identifier() : "akonadi_akonotes_resource_4" wolfi@amiga:~> knotes(9239)/libakonadi Akonadi::EntityTreeModelPrivate::firstFetchJobDone: "Unknown error." So you have to start it again, then it works. But I guess I should file a separate bug report for this.
YEs please open a new bug report.
(In reply to comment #46) > YEs please open a new bug report. OK, done: https://bugs.kde.org/show_bug.cgi?id=334027
opensuse 13.1 kde 4.13 updating today => migration is a success . i find again my 6 notes
I see this has been fixed - thank you very much. Do I have do download the source and compile it myself, or is there a .deb package somewhere? Thanks in advance
Please ask in a forum of your distribution if they are offering updated packages prior to the official 4.13.1 release.
Same here after updating from Kubuntu 13.10 to 14.04. A kdepim classic already. Thanks for the quick update Laurent but the question is, how do I "rescue" my old notes so they appear in the new Knotes?
i still have this issue. i'm on kubuntu 14.04 and knotes version 4.13, knotes-migrator 0.1 i also tried to copy the files /usr/share/kde4/services/kresources/knotes/local.desktop and /usr/lib64/kde4/knotes_local.so from an older machine to mine, but doesn't work. Is it possible that new knotes-migrator not yet available for Kubuntu? Some more informations: apt-cache policy knotes knotes: Installed: 4:4.13.0-0ubuntu1 Candidate: 4:4.13.0-0ubuntu1 Version table: *** 4:4.13.0-0ubuntu1 0 500 http://mirror.switch.ch/ftp/mirror/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status dpkg -l | grep knotes ii knotes 4:4.13.0-0ubuntu1 amd64 sticky notes application Thanks for response thomi
At the moment: all notes copied, and all copied notes unreadable, cause all was in Russian.
#52, if you add the Kubuntu Updates PPA in your sources, you gill get the latest update to the migrator and it will import your old notes, BUT... ... as #53 says, there's a problem with the encoding handling in the migrator and any non-ASCII character will get imported as an unknown one (�). If your notes are in a not-a-single-letter-is-in-ASCII language (russian, chinese, arabic, etc...), they will all be unreadable, so I'd recommend waiting to see if it gets fixed.
(In reply to comment #54) > ... as #53 says, there's a problem with the encoding handling in the > migrator and any non-ASCII character will get imported as an unknown one > (�). If your notes are in a not-a-single-letter-is-in-ASCII language > (russian, chinese, arabic, etc...), they will all be unreadable, so I'd > recommend waiting to see if it gets fixed. Hm, it imported all my german umlauts (which are not ASCII as well) just fine here (openSUSE). Anyway, I would say that is a different bug and should be reported separately. This one is RESOLVED FIXED, so don't expect a different bug you mention here getting fixed as well.
Created attachment 87278 [details] akonadi & knotes (In reply to comment #54) > #52, if you add the Kubuntu Updates PPA in your sources, you gill get the > latest update to the migrator and it will import your old notes, BUT... Took me a while to figure this one out :-/ sudo add-apt-repository ppa:kubuntu-ppa/ppa sudo apt-get update sudo apt-get dist-upgrade (thanks to bug #336383 comment #4) So now knotes-migrator ran again and incremented its version: $ cat ~/.kde/share/config/knotes-migratorrc [Migration] Version=2 Also the log now changed to 4 lines per try: $ cat .kde/share/apps/knotesmigrator/migration.log [Do. Mai 29 15:43:39 2014] Info : Starting migration... [Do. Mai 29 15:43:39 2014] Info : Migration finished. [Do. Mai 29 15:48:29 2014] Info : Starting migration... [Do. Mai 29 15:48:29 2014] Info : Migration finished. [Do. Jun 19 12:18:05 2014] Info : Starting migration... [Do. Jun 19 12:18:05 2014] Info : Beginning KNotes migration... [Do. Jun 19 12:18:05 2014] Info : KNotes migration finished [Do. Jun 19 12:18:05 2014] Info : Migration finished. Problem still remains ... no old notes. Reran migrator in interactive mode to no avail: $ knotes-migrator --interactive Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon Finally I've added the old notes.ics as single file ics notes (not mail-dir) resource to akonadi $ ls -la ~/.kde/share/apps/knotes/notes.ics -rw------- 1 holger holger 181570 Mär 27 20:47 /home/holger/.kde/share/apps/knotes/notes.ics But it won't show up as collection in knotes. What else could I try to get my notes back?
(In reply to comment #56) > What else could I try to get my notes back? For the migration to work you actually have to have a legacy knotes KResource correctly configured. So please check that ~/.kde/share/config/kresources/notes/stdrc exists and points to your notes.ics file. If not, create that file (with a text editor) with the following content: -------------------------------------- [General] PassiveResourceKeys= ResourceKeys=aEJOauTlK8 Standard=aEJOauTlK8 [Resource_aEJOauTlK8] NotesURL[$e]=file://$HOME/.kde/share/apps/knotes/notes.ics ResourceIdentifier=aEJOauTlK8 ResourceIsActive=true ResourceIsReadOnly=false ResourceName=Notizen ResourceType=file -------------------------------------- (the ResourceIdentifier and the ResourceName could of course be different) Then remove ~/.kde/share/config/knotes-migratorrc and run knotes-migrator or knotes again to restart the migration.
(In reply to comment #57) > So please check that ~/.kde/share/config/kresources/notes/stdrc exists and Wow great! Thanx for this magic file ... seems you know my harddrive better than I myself. This brought me a step closer. The dialog actually promises to convert 35 notes. But then a bunch of 21 notifications pop up, telling me, they could not write a mail-file to some tmp directory: > Notizen: Die E-Maildatei /home/holger/.local/share//notes/I8m9FANpUf/tmp/1403374340.R513.Meerschweinchen kann nicht geschrieben werden. The problem is the randomly named directory "I8m9FANpUf" does not exist and the name changes in every call to knotes migrator, so I cannot predict it and create it manually. Can I somehow nail this name down? PS: from my .kde/share/apps/knotesmigrator/migration.log [Sa. Jun 21 20:12:20 2014] Info : Starting migration... [Sa. Jun 21 20:12:20 2014] Info : Beginning KNotes migration... [Sa. Jun 21 20:12:20 2014] Info : Creating instance of type akonadi_akonotes_resource [Sa. Jun 21 20:12:20 2014] Info : Instance "akonadi_akonotes_resource_8" synchronized [Sa. Jun 21 20:12:20 2014] Info : Received root collections [Sa. Jun 21 20:12:20 2014] Info : Starting migration of 35 notes [Sa. Jun 21 20:12:20 2014] Info : Root fetch finished [Sa. Jun 21 20:12:20 2014] Info : KNotes migration finished [Sa. Jun 21 20:12:20 2014] Info : Migration finished.
Strange, this morning, after restarting my machine I got three sets of my old notes. I could remove two of them and keep the third. According to akonadi they should reside in a folder .local/share/notes/11JIk70hpr/ which didn't exist. So I created it manually. Now, when I add new notes, they automatically appear in that folder in a subfolder "new". But the other converted notes somehow linger around in hyperspace and don't materialize on my harddrive. At least I don't know where? Even if I change their content (that's why I know, they were not written back to the old notes.ics source they came from). A few times I just got some weird dialog asking me to keep the left or right version.
(In reply to comment #58) > (In reply to comment #57) > > So please check that ~/.kde/share/config/kresources/notes/stdrc exists and > > Wow great! Thanx for this magic file ... seems you know my harddrive better > than I myself. This brought me a step closer. The dialog actually promises > to convert 35 notes. Well, I stumbled over the same "problem" when trying to reproduce bug#334357 with 4.13.1. I wanted to do it with a new user to not pollute my Akonadi settings/database, so I copied over my user's ~/.kde4/share/apps/knotes/ but no notes were migrated. Then I noticed that there's no actual kresource defined (because it was a fresh account). (In reply to comment #59) > Strange, this morning, after restarting my machine I got three sets of my > old notes. I could remove two of them and keep the third. According to > akonadi they should reside in a folder .local/share/notes/11JIk70hpr/ which > didn't exist. So I created it manually. Hm. The akonotes resource should create the folder manually when syncing the notes to the disk, Akonadi is a cache between the applications (knotes in this case) and the data itself (i.e. the notes). You could try to synchronize the notes manually in akonadiconsole, right-click on the resource on the "Browser" tab. > Now, when I add new notes, they > automatically appear in that folder in a subfolder "new". But the other > converted notes somehow linger around in hyperspace and don't materialize on > my harddrive. At least I don't know where? Probably in the Akonadi database. You should be able to remove them in knotes and in akonadiconsole. And remove the unwanted resources as well, either in akonadiconsole or Systemsettings->Personal Information->Akonadi Resources Configuration. > Even if I change their content (that's why I know, they were not written > back to the old notes.ics source they came from). A few times I just got > some weird dialog asking me to keep the left or right version. That dialog appears when a conflict is detected between the cached version and the file on disk (f.e. if the file is changed by a different application). I saw that a lot in KMail in earlier versions, seems to be some timing issue. Select the version you want to keep and it should work. You could try to clean up your akonadi database with "akonadictl fsck" or even "akonadictl vacuum". But that's completely unrelated to this bug report now. If you cannot get it to work, please file a new bug about your problem(s). Or ask in the forums.
Thanks for your help and patience.
(In reply to comment #61) > Thanks for your help and patience. Btw, I noticed similar problems like you describe today. First I couldn't create new notes at all. For some reason there wasn't any collection to save new notes to selected, and I had to enable both of my "Notizen" collections (I had disabled one, but both have the same name, so maybe knotes got confused by that?). After that, creating new notes worked, but the changes didn't get saved, and I got those conflict dialogs all the time (even when just showing the note). Quitting and restarting knotes fixed it for me (my changes were lost though). But as I said, those issues should be reported separately. I will if I can reproduce it. (it works fine again at the moment)
Maybe Akonadi thought, your resources were in read-only mode for some strange reason? In my case changes to imported notes are persisted somewhere, somehow and survive a reboot ... I just don't see them as maildir-folder formated files. I wonder how/what to backup? In contrast any new notes are written to the expected folder.
(In reply to comment #63) > Maybe Akonadi thought, your resources were in read-only mode for some > strange reason? I don't think so. It seemed more like it wanted to store them in a not-existent collection. > In my case changes to imported notes are persisted somewhere, somehow and > survive a reboot ... I just don't see them as maildir-folder formated files. > I wonder how/what to backup? In contrast any new notes are written to the > expected folder. As I said, they are in the Akonadi database, which is a cache between the applications and the data on disk (or server, ...). Have you tried the things I suggested? (akonadiconsole, akonadictl fsck) You should also be able to create a new akonotes resource and move them there (and maybe back again), with akonadiconsole f.e. But again, that's not really related to _this_ bug report. Another note though, as I just noticed this and think you might be misunderstanding something: (In reply to comment #59) > Even if I change their content (that's why I know, they were not written > back to the old notes.ics source they came from). Of course they won't get written back to the old notes.ics file. They are imported now to the akonotes resource, which stores them as maildir in a subfolder of ~/.local/share/notes/. They should get written back there of course if you change them.
*** Bug 335703 has been marked as a duplicate of this bug. ***
5th JUL 2014 - KNotes still don't work" /etc/issue display: Ubuntu 14.04 LTS /n /l KDE version: 4.13.2 knotes -version display: 4.13.2 Clicking KNots icon with right mouse button, choosing "New Note" - nothing seen. Running knotes on konsole displays message: "QDBusconnection: session D-Bus connection created before QCoreApplication. Application may misbehaven. knotes already started"
(In reply to comment #66) > Clicking KNots icon with right mouse button, choosing "New Note" - nothing > seen. Sounds like the issue I described, and Knut Hildebrand in the other bug report. > Running knotes on konsole displays message: > "QDBusconnection: session D-Bus connection created before QCoreApplication. > Application may misbehaven. knotes already started" You cannot start knotes as it is already running. Quit it first. I suppose you will get some message like this then: Error during fetch: "Collection xxx does not exist" Try what I suggested in the other report. But IMHO the other bug is _not_ a duplicate of this. So let's continue in the other report, which I will reopen in a minute.