Version: 2.0.2 (using KDE 4.6.5) OS: Linux Now tried 3 versions of my OS (SimplyMepis 11 and 11.0.0.9 both 32 and 64 bit) on freshly formatted partitions. libk3b6-extracodecs, libmp3lame0 etc., and others loaded via synaptic. Regardless, trying to burn mp3 results in only .wav on the CD, with spurious foreign artists and song titles. All take several minutes to load in Dolphin, and the device notifier runs for ages checking the files. Three different versions of my OS on twice-formatted partitions - absolute clean installs. Even went back to KDE 4.5.3 on all three fresh installs. Then I opted to burn .wav files only on a fresh install. Again, spurious filenames and Dolphin having trouble displaying the contents of the CD. Reproducible: Always Steps to Reproduce: As outlined above. Actual Results: As outlined above - although an image file burned OK. Expected Results: Dolphin should instantly read the CD - there should be an mp3 folder visible. Tracks should have their proper names, not spurious names and artists from all over the globe - should play in amarok (won't). And the system device notifier shouldn't be examining the CD, then the file, then caches, then everything else and taking many minutes to do so. But when all this burning takes place, K3B still comes up with... SUCCESS! Cheers. OS: Linux (i686) release 2.6.36-1-mepis-smp Compiler: cc
Hi. After all this time, I don't understand the purpose of this email. Has this k3b problem been resolved? Cheers On 3 July 2012 22:17, Jekyll Wu <adaptee@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=288896 > > Jekyll Wu <adaptee@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |adaptee@gmail.com > Severity|crash |normal > > -- > You are receiving this mail because: > You reported the bug. >
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!
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!
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 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!