Bug 323343

Summary:	When ripping CD, K3b should warn about bad filenames; instead ripping fails with generic error message
Product:	[Applications] k3b	Reporter:	Claus Appel <spectrumdt>
Component:	Copying	Assignee:	k3b developers <k3b>
Status:	REPORTED ---
Severity:	minor	CC:	trueg
Priority:	NOR
Version:	2.0.2
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Claus Appel 2013-08-10 14:01:46 UTC

When ripping CDs, each track gets ripped to a file. Tyically, the user will let K3b auto-generate filenames from the track titles and other metadata. 

It is possible to specify filenames that contain invalid characters, such as question marks. If you do, K3b gives no warning. Instead, when K3b tries to generate the file in question, it just fails with a generic message (presumably from the file system): "An unknown error occurred. Unable to open [filename] for writing."

In my opinion, K3b should validate filenames before it begins ripping, and give the user a warning if the filenames are bad. 

Reproducible: Always

Steps to Reproduce:
1.
Insert any audio CD.
2. Open K3b.
3.
Go to "Rip Audio CD..."
4. Change the title of the first track to simply "?"
5. Click "Start ripping".
6. Go to the tab "File naming".
7. Make sure that "Ripped files pattern" contains "%t".
8. In the view of filenames at the top of this window, verify that the first filename contains a question mark.
9. Click "Start ripping".

Actual Results:  
An error will appear: "An unknown error occurred. Unable to open [filename] for writing."

Expected Results:  
The system should show an error message: "The following filenames are bad. Please correct them..."

Comment 1 Andrew Crouthamel 2018-11-12 02:49:03 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 2 Claus Appel 2018-11-12 16:52:24 UTC

I can confirm that this behaviour still happens in K3b 2.0.2 on KDE Development Platform 4.13.3 (Kubuntu 14.04).

Comment 3 Justin Zobel 2022-12-03 09:01:44 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 4 Bug Janitor Service 2022-12-18 05:14:31 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 5 Claus Appel 2022-12-25 11:22:52 UTC

I can confirm that this still happens in K3b 19.12.3 on Kubuntu 20.04.