Bug 150551 - K3b does not respect user's input on overwrite dialog, always overwrites
Summary: K3b does not respect user's input on overwrite dialog, always overwrites
Status: RESOLVED UNMAINTAINED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-07 02:13 UTC by Peter Jones
Modified: 2010-03-16 16:04 UTC (History)
1 user (show)

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 Peter Jones 2007-10-07 02:13:52 UTC
Version:           k3b-1.0.3-3.fc8 (using KDE KDE 3.5.7)
Installed from:    Fedora RPMs
OS:                Linux

Please see
https://bugzilla.redhat.com/show_bug.cgi?id=321561
I was referred to your site when I filed initially on Fedora's bugzilla.
Comment 1 Rex Dieter 2009-08-14 18:15:41 UTC
Filling in data so folks don't need to go tromping to another site for details:

Description of problem:
When K3b is creating an image from a DVD, duplicate image name is detected, but
writing is allowed, even if the user says "no" to the ensuing dialogue.

Version-Release number of selected component (if applicable):
k3b-1.0.3-3.fc8

How reproducible:
Always.

Steps to Reproduce:
1. Start K3b
2. Select Tools,Copy DVD
3. Set options to "Only Create Image", <existing file>, "Ignore errors"
4. A dialog requesting permission to overwrite the existing file appears
5. Select No
 
Actual results:
K3b copies over the existing file anyway.

Expected results:
K3b should return to main menu, or offer the user a chance to specify a new name

Additional info:

What I actually did was to copy to a new file, then repeat the copying with the
same parameters, just to reassure myself that I wouldn't accidentally overwrite
an existing DVD image.
Comment 2 markuss 2010-03-16 16:04:29 UTC
In an attempt to clean up old bugs that are not valid for K3b 2.0 (=KDE SC 4.x port) anymore, this is now being marked as UNMAINTAINED.
If this bug is still valid for 2.0, please reopen it.