Bug 126851 - k3b doesn't unmount source discs
Summary: k3b doesn't unmount source discs
Status: RESOLVED DUPLICATE of bug 96155
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-06 16:18 UTC by Maciej Pilichowski
Modified: 2006-09-26 01:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2006-05-06 16:18:08 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    SuSE RPMs

There are dvd-reader and dvd-writer drives. I've burned some files from the dvd-reader (on the fly + verify). Now I am unable to get the source disc in normal fashion because k3b doesn't unmount disc despite my best efforts:
* erasing files from the project
* changing the directory
* quitting k3b!

The disc is still mounted. I have to unmount it explicitly -- unmount /media/dvd.
Comment 1 Sebastian Trueg 2006-05-06 18:34:34 UTC
and what is the problem? If you mount manually (and mounting through K3b is 
mounting manually) you have to unmount manually.
Comment 2 Maciej Pilichowski 2006-05-06 19:17:08 UTC
> and what is the problem?

? 

Let's say you have to copy files from two discs. In order to do this you have to:
run k3b, start dvd project, add files, burn disc, ___quit k3b, unmount source disc, run k3b again,____ start project, add files, burn disc

Is this really intended? Even without quitting k3b -- if k3b mounted the disc, I would say, let k3b unmount it.
Comment 3 Christoph Burger-Scheidlin 2006-09-26 01:49:22 UTC
If you can unmount the disk while k3b is running then this is not a bug, since k3b does not know when you want to umount the disk and you should be able to use some interface to do so (e.g. media://).

If you cannot umount the disk while k3b is running, this is a duplicate of 96155. I suppose it is, since otherwise you would not have gone through all the trouble of exiting k3b.

*** This bug has been marked as a duplicate of 96155 ***