Bug 387527 - Dialog shown when the user inadvertently tries to burn a multissesion disc including a session imported from a disc already erased/ejected does not clarify the situation and may be confusing
Summary: Dialog shown when the user inadvertently tries to burn a multissesion disc in...
Status: REPORTED
Alias: None
Product: k3b
Classification: Applications
Component: GUI/Usability (show other bugs)
Version: 22.11.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-02 12:38 UTC by Patrick Silva
Modified: 2022-12-01 12:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (70.89 KB, image/png)
2017-12-02 12:59 UTC, Patrick Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2017-12-02 12:38:12 UTC
I found two situations in which it is possible try to burn
a multissesion disc using a invalid imported session:

insert a multissession rewritable disc
create a multissesion project and import the session from the disc
add some new file(s) to your project
now click "Format" button in toolbar and erase your disc
after erase process, your disc is ejected. Re-insert it and click "burn" button
Click "burn" button again to start burning process
I get the dialog from my screenshot.

OR

insert a multissesion disc
create a multissesion project and import the session from the disc
add some new file(s) to your project
eject actual disc and insert another disc
Click "burn" button to start burning process
Again I get the dialog from my screenshot.

The problem here is that the message from the dialog is not clear and does not explain
the situation. For example, I thought that it was a bug.
https://bugs.kde.org/show_bug.cgi?id=387384#c14

In my screenshot you can see "Searching for old ses".
But this message is hard to see and cut off.

Maybe K3b should prevent the use of an invalid imported session to burn a disc
or show a better message in the dialog to clarify the situation.

I use K3b 17.08.3 on Arch Linux.
Comment 1 Patrick Silva 2017-12-02 12:59:15 UTC
Created attachment 109174 [details]
screenshot
Comment 2 Justin Zobel 2022-12-01 04:34:47 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Patrick Silva 2022-12-01 12:36:54 UTC
Can reproduce the first case at least.

Operating System: Arch Linux
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Graphics Platform: Wayland