Bug 300805 - KJots on KDE 4.8.3: migration doesn't work when migrating from any previous KDE release.
Summary: KJots on KDE 4.8.3: migration doesn't work when migrating from any previous ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kjots
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Mandriva RPMs Linux
: NOR major
Target Milestone: ---
Assignee: Stephen Kelly
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-29 11:23 UTC by mekde
Modified: 2023-01-19 05:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mekde 2012-05-29 11:23:15 UTC
When upgrading to KDE 4.8.3 the KJots migration fails with no books being migrated. 

Additionally, no new KJot Books or Pages can be created.

I've tested this on various rpm Distros using various KDE release and I've discovered that not one of the were able to migrate the KJots books and pages.

Another commonly spoken about issue is not knowing where the KJots books are stored since home/nameduser/.kde4/share/apps/kjots/  is no longer used. It would help immensely if users could backup the" new KJot data"  as we currently have no idea where it's stored.,

Reproducible: Always

Steps to Reproduce:
1. Upgrading from KDE 4.xx to 4.8.3 the "automatic" migration fails.
2. Using the command kjotsmigrator --interactive does not work
3. No import function in KJots 4.8.3 thus this method can't be tested 
Actual Results:  
No results apart from the kjotsmigrator folder and kjotsmigrator log being created.

Expected Results:  
Successful  migration of all KJot Books and Pages

It appears that lots of other users who can't migrate KJots also suffer crashes when attempting the migration.
Comment 1 menschmeier 2012-09-07 19:38:31 UTC
I can confirm this bug on my system too. Migration fails, the automatic and the interactive.
Comment 2 Andrew Crouthamel 2018-11-09 00:59:59 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-18 03:23:41 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-20 07:49:51 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-04 05:26:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-19 05:16:40 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!