Bug 486754

Summary:	K3b hangs on startup when another process is reading the same device
Product:	[Applications] k3b	Reporter:	Henry Pfeil <hpfeil>
Component:	GUI/Usability	Assignee:	k3b developers <k3b>
Status:	RESOLVED FIXED
Severity:	normal	CC:	michalm, trueg
Priority:	NOR
Version:	24.04.80
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Henry Pfeil 2024-05-07 20:47:32 UTC

SUMMARY
With ddrescue repairing disc rot on /dev/sr1, startup hangs trying to read the damaged disc. 

STEPS TO REPRODUCE
1. Run ddrescue on /dev/sr1 on another virtual desktop
2. Launch k3b
3. Do something else on a different desktop for a while.

OBSERVED RESULT
K3b hangs on the startup logo screen for an undetermined long time. Have to kill the process and relaunch, which sometimes works, mostly not

EXPECTED RESULT
K3b completes launching with the unreadable device grayed out. It should take only a couple of seconds to determine the disc is not readable in its entirety, less time if another process has the device open. [lsof|grep sr1?]

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13

ADDITIONAL INFORMATION
Kernel Version: 6.6.30 64-bit

Comment 1 Henry Pfeil 2024-05-09 18:29:53 UTC

I got around the issue by suspending the ddrescue process before launching K3b. Since this is such an obscure instance of incorrect behavior, more pressing matters may push this to the end of the queue.

Comment 2 Henry Pfeil 2024-06-03 16:30:16 UTC

Upon further rooting around I discovered this is part of a design flaw which I addressed in a different bug. Thus, this bug is closed.