Bug 139561

Summary:	Make the "Unable to reload media" error a notice
Product:	[Applications] k3b	Reporter:	Francois Marier <francois>
Component:	general	Assignee:	k3b developers <k3b>
Status:	REPORTED ---
Severity:	wishlist
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:

Description Francois Marier 2007-01-03 16:10:57 UTC

Version:           0.12.17 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Armando Romero <reportbug@8128.biz> has reported the following inconsistency in version 0.12.17 (see http://bugs.debian.org/405408).

It has to do with two messages for "reloading the media" not being the same: one is an error with a sound effect and the other is a notice simply asking the user to reload the media.  As far as I understand it, Armando is suggesting that the error be made into a notice as well since this does not cause any problems later on (hence, there is no need to alarm the user).

It may be fixed in 1.0 however so feel free to close this bug if it is no longer the case in 1.0.

Armando's original report:

I am often writing DVD-RWs. When k3b starts writing on it, first it says
that it does automatical pre-formatting, but after that it shows
unpleasant warning message with disturbing sound: Unable to reload
media, please reload manually. That is probably due to laptop design.

However, once it has writtn all the data it ejects the DVD and says
gently that user shall reload media and press OK.

My proposal is to remove that disturbing warning after pre-formatting
(blanking) DVD and to have there the same "Reload the media and press
OK" notice, without any sound.

Both, disturbing warning and the notice after completing the DVD are not
logical to be together.

Comment 1 Sebastian Trueg 2007-01-03 23:30:53 UTC

K3b never makes a sound if the reloading fails and never did. The sound is used to inform the user that a medium has to be inserted. This is different from the reloading issue. It will also be emitted if you start writing without a medium in the drive.

So there is technically no inconsistent behaviour but I see how it might seem so to the user. I am not sure at the moment how to solve this properly, though.