Version: 2.0.1 (using KDE 4.5.1) OS: Linux The "Save CDDB Entry Locally" does not work correctly, or I do not understand how it works. When I modify CDDB tags and save them locally, K3b seems to ignore my changes and just reloads everything from CDDB. Reproducible: Always Steps to Reproduce: 1. Pop in a CD. 2. Have K3b load information from CDDB. (It does this automatically.) 3. Edit some of the tags. 4. Click "Save CDDB Entry Locally". 5. Close K3b. 6. Restart K3b. Actual Results: K3b forgets my changes and reloads everything from CDDB. Expected Results: K3b should load the changed tags that I saved. OS: Linux (x86_64) release 2.6.35-28-generic Compiler: cc
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!
This bug appears to have been fixed. I can not reproduce it in K3b 2.0.2 on KDE Development Platform 4.13.3 (Kubuntu 14.04).
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!
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!
This appears to have been fixed in K3b 19.12.3.