[k3b] [Bug 398190] Can't copy CD after upgrading from Ubuntu 16.04 LTS to 18.04 LTS. Error log in comment.
https://bugs.kde.org/show_bug.cgi?id=398190 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 398190] Can't copy CD after upgrading from Ubuntu 16.04 LTS to 18.04 LTS. Error log in comment.
https://bugs.kde.org/show_bug.cgi?id=398190 --- Comment #7 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 398190] Can't copy CD after upgrading from Ubuntu 16.04 LTS to 18.04 LTS. Error log in comment.
https://bugs.kde.org/show_bug.cgi?id=398190 --- Comment #6 from powder4ski...@gmail.com --- I think I was able to copy with a later version. However, my current issue is K3b becoming unresponsive right after launch. It is so slow to load and read a CD, and I don't think I've used it to make a copy since. I get numerous unresponsive dialogs with option to abort or wait and it takes very long to do anything such as even pulling down a menu to select an option or selecting to read a CD. If I leave it running, it usually will eventually read a CD after about 30 minutes. This problem has been ongoing since Ubuntu 20.04 LTS and currently with Ubuntu 22.04.1 LTS with two different computers. On Tue, Nov 29, 2022 at 10:28 PM Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=398190 > > Justin Zobel changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #5 from Justin Zobel --- > 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! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 398190] Can't copy CD after upgrading from Ubuntu 16.04 LTS to 18.04 LTS. Error log in comment.
https://bugs.kde.org/show_bug.cgi?id=398190 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from Justin Zobel --- 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! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 398190] Can't copy CD after upgrading from Ubuntu 16.04 LTS to 18.04 LTS. Error log in comment.
https://bugs.kde.org/show_bug.cgi?id=398190 --- Comment #4 from Thomas Schmitt --- Hi, Leslie Zhai wrote: > Is it better to *remove* the unusual -raw96r option by default, what I mean, > just set writingMode's default value to TAO or SAO? Welcome suggestion. Well, we shall not take away any option (even if it helps to shoot the user's foot). About defaults we can ponder when we know how that option was chosen by powder4ski...@gmail.com (maybe by default, maybe by hand ?). > It failed to mkdir for such weird path: > $mkdir -p /tmp/SO U/SO U/SO U/SO U/k3bCdCopy0/ You have to put the blanks into quotation marks. Like mkdir -p '/tmp/SO U/SO U/SO U/SO U/k3bCdCopy0/' But i suspect that rather K3B decided to create that directory. > Related to BUG385367 and BUG384117 385367 is about ripping (i.e. from CD to hard disk). 384117 seems to be a duplicate of thet. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 398190] Can't copy CD after upgrading from Ubuntu 16.04 LTS to 18.04 LTS. Error log in comment.
https://bugs.kde.org/show_bug.cgi?id=398190 --- Comment #3 from Leslie Zhai --- Hi Thomas, Thanks for your kind response! > the wodim option -raw96r is unusual and (years ago) was a source of trouble > for me. Any idea how K3B came to think that it is good to use it ? > > It is chosen in libk3b/projects/k3bcdrecordwriter.cpp if >d->writingMode == K3b::WritingModeRaw > > This seems to be configurable. Try to choose "TAO" or "SAO" instead. Is it better to *remove* the unusual -raw96r option by default, what I mean, just set writingMode's default value to TAO or SAO? Welcome suggestion. > > (I see code which sets WritingModeRaw in src/k3bwritingmodewidget.cpp) > > - > > I further wonder about the strange file addresses, like > /tmp/SO U/SO U/SO U/SO U/k3bCdCopy0/Track02.wav > > I assume that this is one path, not five. But why the blanks and why > four directories "SO U" ? > Can this be due to a misconfiguration of K3B ? > Does a directory "/tmp/SO U/SO U/SO U/SO U" exist while K3B is > attempting to do its job ? Related to BUG385367 and BUG384117 What about change the *tmp* directory to $HOME/Music? It failed to mkdir for such weird path: $mkdir -p /tmp/SO U/SO U/SO U/SO U/k3bCdCopy0/ Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 398190] Can't copy CD after upgrading from Ubuntu 16.04 LTS to 18.04 LTS. Error log in comment.
https://bugs.kde.org/show_bug.cgi?id=398190 --- Comment #2 from Thomas Schmitt --- Hi, the wodim option -raw96r is unusual and (years ago) was a source of trouble for me. Any idea how K3B came to think that it is good to use it ? It is chosen in libk3b/projects/k3bcdrecordwriter.cpp if d->writingMode == K3b::WritingModeRaw This seems to be configurable. Try to choose "TAO" or "SAO" instead. (I see code which sets WritingModeRaw in src/k3bwritingmodewidget.cpp) - I further wonder about the strange file addresses, like /tmp/SO U/SO U/SO U/SO U/k3bCdCopy0/Track02.wav I assume that this is one path, not five. But why the blanks and why four directories "SO U" ? Can this be due to a misconfiguration of K3B ? Does a directory "/tmp/SO U/SO U/SO U/SO U" exist while K3B is attempting to do its job ? - A cdrskin run from command line (without CD-TEXT for now) would look like (while being in the directory with the Trackxx.wav files): cdrskin -v dev=/dev/sr0 speed=48 -audio Track01.wav Track02.wav \ Track03.wav Track04.wav Track05.wav Track06.wav Track07.wav \ Track08.wav Track09.wav Production of CD-TEXT would need a file for option "textfile=" which K3B prepared and which you would need to prepare, too. CD-TEXT has few influence of the burn success. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 398190] Can't copy CD after upgrading from Ubuntu 16.04 LTS to 18.04 LTS. Error log in comment.
https://bugs.kde.org/show_bug.cgi?id=398190 Leslie Zhai changed: What|Removed |Added CC||scdbac...@gmx.net, ||zhaixi...@loongson.cn --- Comment #1 from Leslie Zhai --- Hi, Thanks for your bug report! Could you try other backend, for example libburnia https://dev.lovelyhq.com/libburnia/web/wikis/home Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
