|
Bugzilla – Full Text Bug Listing |
| Summary: | blank cd-r opens kscd requester | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Martin Lasarsch <martin.lasarsch> |
| Component: | KDE | Assignee: | Hannes Reinecke <hare> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 Plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | lshal output after blank cd-r inserted | ||
|
Description
Martin Lasarsch
2005-09-05 16:12:31 UTC
I need lshal output Created attachment 48891 [details]
lshal output after blank cd-r inserted
If this disc is really blank, then this is a HAL bug: volume.disc.is_blank = false (bool) volume.disc.has_data = false (bool) volume.disc.has_audio = true (bool) Could you bring me this CD for testing? room 2.2.9 This looks like a problem with SATA cdrom devices. There is always this error message: Sep 6 13:54:47 linux kernel: sr0: Hmm, seems the drive doesn't support multisession CD's Sep 6 13:55:11 linux kernel: SCSI error : <1 0 1 0> return code = 0x2 Sep 6 13:55:11 linux kernel: SCSI error : <1 0 1 0> return code = 0x2 Sep 6 13:55:11 linux kernel: SCSI error : <1 0 1 0> return code = 0x2 Sep 6 13:55:11 linux kernel: SCSI error : <1 0 1 0> return code = 0x2 Sep 6 13:55:11 linux kernel: SCSI error : <1 0 1 0> return code = 0x2 Sep 6 13:55:11 linux kernel: SCSI error : <1 0 1 0> return code = 0x2 Sep 6 13:55:18 linux kernel: SCSI error : <1 0 1 0> return code = 0x2 Coolo: could we workaround this for the suseplugger until this is really fixed? First check if the cd/dvd is blank and first if not the other propertys as has_audio ? "volume.disc.is_blank = false" doesn't look like a blank CD to me. I don't see what suseplugger can do with this hm, you're right. My mistake. @hare: please take a look at this bug. This is reproduceable a problem with sata. Please retest with RC1. We have quite some SATA patches in there. works for me with pre rc1 on my pc with sata burner |