[k3b] [Bug 404313] New: Linux Mint 19v1 how to change the behaviour of K3b with a blank DVD in a removable drive?
arclite7 at gmail.com
arclite7 at gmail.com
Thu Feb 14 00:43:45 GMT 2019
https://bugs.kde.org/show_bug.cgi?id=404313
Bug ID: 404313
Summary: Linux Mint 19v1 how to change the behaviour of K3b
with a blank DVD in a removable drive?
Product: k3b
Version: 17.12.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: Copying
Assignee: k3b at kde.org
Reporter: arclite7 at gmail.com
CC: michalm at jabster.pl, trueg at kde.org
Target Milestone: ---
SUMMARY
the application fails to check first if a prior copy of itself already exists,
to then open a courtesy dialogue of "A prior iteration K3b exists. Continue
(Y/N)"
STEPS TO REPRODUCE
1. Default behaviour of blank disk enquiry, set to K3b
2. Start multi-media copy project K3b
3. At each subsequent blank (DVD) insertion
OBSERVED RESULT
Confusion over multiple iterations of K3b and its various dialogue windows need
be closed without disrupting th current copy process as this is now obscured
EXPECTED RESULT
So to clear what appears to be an application error, i.e. the application fails
to check first if a prior copy of itself already exists, to then open a
courtesy dialogue of:
"There is already a copy of K3b running, do you really want to start a fresh
iteration of K3b? (Y/N)"
But failing this, how can I now change the default behaviour of the DVD drive
whenever a fresh disk is inserted? This is not made clear after the initial
request for default behaviour! (another programming error after entrapping the
end-user, then ignoring the needs of the end-user/non-programmer!)
SOFTWARE/OS VERSIONS
Linux/Mint Cinnamon 19v1 Tessa
Linux Lenovo-G50-30 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
(available in About System) Not so... better info needed!
KDE Frameworks 5.44.0
Qt 5.9.5 (built against 5.9.5)
The xcb windowing system
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the k3b
mailing list