Bug 16252

Summary:	k3b finds optical drives locked by the rest of the kde world
Product:	Mageia	Reporter:	Frank Griffin <ftg>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	k3b	CVE:
Status comment:

Description Frank Griffin 2015-06-30 03:41:53 CEST

In the new KDE, loading a blank optical medium (DVD) gives the normal device list popup indicating a blank DVD volume.  However, non-KDE apps like brasero no longer "see" the drive.  Previously, brasero would come up saying "please load a blank disk" and as soon as the KDE device list indicated that it had identified the blank media, the prompt would change to giving the burn candidate as the drive containing the blank.  This no longer happens.

KDE apps behave differently.  K3B "sees" the blank just fine, but when you try to burn an image to it, you get a prompt saying that the optical device is already in use by just about every KDE background app imaginable, and gives you the option to continue if you know what you're doing.  If you continue, it works fine.

My guess is that the device being in use locks non-KDE apps out of seeing the device as eligible.  K3b is smart enough to ask and give the option to override, but other apps aren't.

Reproducible: 

Steps to Reproduce:

Samuel Verschelde 2015-06-30 09:19:03 CEST

CC: (none) => lmenut
Assignee: bugsquad => mageia

Comment 1 Frank Griffin 2015-07-13 15:48:19 CEST

In current cauldron, the problem with brasero is fixed.  The brasero UI looks different, so whatever updated it seems to have brought it in line with current KDE.

The problem with k3b remains.

Comment 2 Frank Griffin 2015-11-04 23:52:58 CET

Still happening in current cauldron under plasma5.

Comment 3 Frank Griffin 2015-11-05 02:31:27 CET

>KDE apps behave differently.  K3B "sees" the blank just fine, but when you try to burn an image to it, you get a prompt saying that the optical device is already in use by just about every KDE background app imaginable, and gives you the option to continue if you know what you're doing.  If you continue, it works fine.

This is the remaining problem, as reflected by the updated summary.  Traditionally, the first thing k3b does is unmount the disk so that it can deal with it at the device level, and I'm assuming that it is now mistakenly thinking that other apps are using the mounted volume, hence the prompt.

The same prompt occurs a second time if you have specified "verify written data" on the burning operation, after the burn is complete and before the disk is re-read for verification.

In any event, the error seems bogus because if the mounted disk truly were in use by anyone, the umount wouldn't work, and the "Continue" option of the prompt wouldn't work.

Summary: Optical drive management is borked in new KDE => k3b finds optical drives locked by the rest of the kde world
Source RPM: kde => k3b

Luc Menut 2015-11-05 08:37:41 CET

CC: lmenut => (none)

Samuel Verschelde 2016-08-25 16:24:19 CEST

Assignee: mageia => kde

Comment 4 Nicolas Lécureuil 2017-03-15 10:13:23 CET

is it still valid on current cauldron ?

CC: (none) => mageia

Comment 5 Frank Griffin 2017-03-15 15:28:20 CET

No, I hadn't used k3b for a while, but this one appears to be fixed.

Comment 6 Frank Griffin 2017-03-15 15:28:49 CET

Closing.

Status: NEW => RESOLVED
Resolution: (none) => FIXED