udisks doesn't make sense from cdrom

Bug #1993356 reported by Dimitri John Ledkov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udisks
Unknown
Unknown
qemu (Ubuntu)
Triaged
Low
Unassigned
udisks2 (Ubuntu)
Triaged
Low
Unassigned

Bug Description

udisks doesn't make sense from cdrom

there are journal errors from sending ATA command IDENTIFY, maybe incomplete kernel or qemu support?

Revision history for this message
Athos Ribeiro (athos-ribeiro) wrote :

FWIW, I stumbled across this (apparently similar) bug in fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1936813#c1

Changed in qemu (Ubuntu):
status: New → Triaged
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Yes, same scary warnings

Mar 09 08:33:23 localhost-live udisksd[1020]: Error probing device: Error sending ATA command IDENTIFY PACKET DEVICE to '/dev/sr0': Unexpected sense data returned:
                                              0000: 70 00 05 00 00 00 00 0a 00 58 00 01 21 04 00 00 p........X..!...
                                              0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
                                               (g-io-error-quark, 0)

above looks the same as I have with kinetic desktop iso in the qemu VM cd-rom

Paride Legovini (paride)
affects: udisks (Ubuntu) → udisks2 (Ubuntu)
Revision history for this message
Paride Legovini (paride) wrote :

Looks like this is already reported upstream:

https://github.com/storaged-project/udisks/issues/732

It's more than 2.5 years that the bug doesn't get attention/activity, so I'm marking this Ubuntu bug as having Low importance due to low user impact.

That bug mentions "it's a QEMU issue in the way the CD-ROM device emulation is done", but I unable to verify if this is true or not.

Changed in udisks2 (Ubuntu):
status: New → Triaged
Changed in qemu (Ubuntu):
importance: Undecided → Low
Changed in udisks2 (Ubuntu):
importance: Undecided → Low
Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

We still have no progress in the upstream issue.

Revision history for this message
Athos Ribeiro (athos-ribeiro) wrote :

No progress in the upstream bug so far.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.