Bug 312517

Summary:	K3B resets all of my SCSI Disks when inserting an Audio DIsk
Product:	[Applications] k3b	Reporter:	Daniel Duncan <xdan779>
Component:	Audio Project	Assignee:	k3b developers <k3b>
Status:	RESOLVED WORKSFORME
Severity:	critical	CC:	cfeck, trueg
Priority:	NOR
Version:	2.0.2
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Daniel Duncan 2013-01-03 04:34:02 UTC

If I insert an audio disk into either my DVD or CD Drive, k3b resets all of my scsi disks including my primary root/swap drive and both the DVD and CD Drive, causing the system to hang. This only happens when audio disks are inserted into either of the drives

Reproducible: Always

Steps to Reproduce:
1.Start up k3b
2.Insert Audio CD into either CD or DVD Drive
3.Wait for the disk to read media
4. System Freezes while all disk are reset
5. Can usually recover without rebooting if I remove the media while the resets are taking place
6. If the media is left in the disks continue to reset until the system becomes unrecoverable.

7. of note everything is fine if you insert the audio disk before starting up k3b, system reads it, can even rip using other programs, though I would much rather use k3b. If you start up k3b though while the disk is in the disks start resetting again.
8. This is only standard audio disks that cause an issue, data cdroms work just fine with k3b in both drives, dvd video and data work fine with k3b in the dvd drive.
Actual Results:
system hangs while the drives reset, can usually recover if I can get the disk out during the reset, otherwise the disk continuously reset until a full reset is needed.

Expected Results:
I would have expected the disk to be recognized and the contents displayed, without resetting my drives.

I can reproduce at anytime so any information I have left out or can get you please let me know. I do not care how technical or what it needs to be, I really miss using k3b for my audio disks, so would be appreciated.

Comment 1 Christoph Feck 2013-01-06 15:11:20 UTC

Thanks for reporting the issue. Unfortunately, we have no k3b maintainer at the moment.

Comment 2 Andrew Crouthamel 2018-11-12 02:56:14 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-11-21 04:19:53 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Justin Zobel 2023-01-02 07:43:45 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 5 Bug Janitor Service 2023-01-17 05:15:12 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2023-02-01 05:04:45 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!