GNOME Bugzilla – Bug 680615
Apps using brasero-media are no longer able to find any drives using gvfs 1.13.1+
Last modified: 2012-07-31 09:44:12 UTC
Since I've started testing gnome 3.5.x, I'm no longer able to use apps using libbrasero-media for drive detection (sound-juicer, rhythmbox, goobox). With the gdbus-port of gvfs (done in 1.13.1 cycle), obviously something changed so that libbrasero-media is reporting to find 0 drives and 0 volumes, breaking the above mentioned apps. This is e.g. the brasero-media (brasero master) debug output when trying to use sound-juicer with an 18 Track audio cd: BraseroMedia: (at brasero-media.c:533) Initializing Brasero-media 3.4.1 BraseroMedia: (at brasero-medium-monitor.c:654) Probing drives and media BraseroMedia: (at brasero-medium-monitor.c:659) Found 0 drives BraseroMedia: (at brasero-medium-monitor.c:675) Found 0 volumes BraseroMedia: (at brasero-medium-monitor.c:474) GDrive addition signal BraseroMedia: (at brasero-medium-monitor.c:375) Testing drive /dev/sr0 BraseroMedia: (at scsi-sg.c:181) Getting handle BraseroMedia: (at scsi-sg.c:200) Handle ready BraseroMedia: (at brasero-medium-monitor.c:384) Drive is optical BraseroMedia: (at brasero-drive.c:1456) Initializing drive /dev/sr0 from device BraseroMedia: (at brasero-drive.c:1111) Setting GDrive 0x85fe9f8 BraseroMedia: (at brasero-drive.c:1042) Still initializing the drive properties BraseroMedia: (at brasero-medium-monitor.c:453) New drive added BraseroMedia: (at brasero-drive.c:1327) Trying to open device /dev/sr0 BraseroMedia: (at scsi-sg.c:181) Getting handle BraseroMedia: (at scsi-sg.c:200) Handle ready BraseroMedia: (at brasero-drive.c:1380) Device ready BraseroMedia: (at brasero-drive.c:1201) Checking supported profiles BraseroMedia: (at scsi-get-configuration.c:127) Unaligned data (28) setting to max (65530) BraseroMedia: (at scsi-get-configuration.c:162) Sizes mismatch asked 65530 / received 28 BraseroMedia: (at brasero-drive.c:1212) Dectected medium is 0x8 BraseroMedia: (at brasero-drive.c:1419) Drive caps are 3 BraseroMedia: (at brasero-drive.c:890) Probing new medium BraseroMedia: (at brasero-medium.c:3016) Trying to open device /dev/sr0 BraseroMedia: (at scsi-sg.c:181) Getting handle BraseroMedia: (at scsi-sg.c:200) Handle ready BraseroMedia: (at brasero-medium.c:3039) Open () succeeded BraseroMedia: (at brasero-medium.c:3075) Device ready BraseroMedia: (at brasero-medium.c:2896) Initializing information for medium in HL-DT-ST RW/DVD GCC-4244N BraseroMedia: (at brasero-medium.c:2337) Retrieving media profile BraseroMedia: (at brasero-medium.c:1505) Retrieving media available speeds BraseroMedia: (at brasero-medium.c:1328) Retrieving speed (Get Performance) BraseroMedia: (at scsi-sense-data.c:155) SCSI command error: The device timed out BraseroMedia: (at brasero-medium.c:1339) GET PERFORMANCE failed BraseroMedia: (at brasero-medium.c:1420) Retrieving speed (2A speeds) BraseroMedia: (at scsi-mode-sense.c:129) Getting page size BraseroMedia: (at scsi-mode-sense.c:169) Getting page (size = 56) BraseroMedia: (at brasero-medium-monitor.c:474) GDrive addition signal BraseroMedia: (at brasero-medium-monitor.c:375) Testing drive /dev/sda BraseroMedia: (at scsi-sg.c:181) Getting handle BraseroMedia: (at scsi-sg.c:184) No handle: Permission denied BraseroMedia: (at brasero-medium.c:1492) Maximum Speed (Page 2A) 706 BraseroMedia: (at brasero-medium.c:968) Checking simulate (CD SAO) BraseroMedia: (at brasero-medium.c:981) SAO feature is not supported BraseroMedia: (at brasero-medium.c:926) Checking simulate (CD TAO) BraseroMedia: (at brasero-medium.c:939) TAO feature is not supported BraseroMedia: (at brasero-medium.c:948) Medium can be blanked BraseroMedia: (at brasero-medium.c:1125) Tested simulation 1 1, burnfree 1 BraseroMedia: (at brasero-medium.c:2255) Retrieving media status BraseroMedia: (at brasero-medium.c:2315) Closed media BraseroMedia: (at brasero-medium.c:2022) Reading Toc BraseroMedia: (at brasero-medium.c:2062) 19 track(s) found BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 1 BraseroMedia: (at brasero-medium-monitor.c:489) GVolume addition signal BraseroMedia: (at brasero-medium-monitor.c:497) Existing GDrive skipping BraseroMedia: (at brasero-medium.c:1755) Track 1 (session 1): type = 2 start = 0 size = 39824 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 2 BraseroMedia: (at brasero-medium.c:1755) Track 2 (session 1): type = 2 start = 39824 size = 32024 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 3 BraseroMedia: (at brasero-medium.c:1755) Track 3 (session 1): type = 2 start = 71848 size = 32793 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 4 BraseroMedia: (at brasero-medium.c:1755) Track 4 (session 1): type = 2 start = 104641 size = 10091 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 5 BraseroMedia: (at brasero-medium.c:1755) Track 5 (session 1): type = 2 start = 114732 size = 21537 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 6 BraseroMedia: (at brasero-medium.c:1755) Track 6 (session 1): type = 2 start = 136269 size = 8528 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 7 BraseroMedia: (at brasero-medium.c:1755) Track 7 (session 1): type = 2 start = 144797 size = 16716 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 8 BraseroMedia: (at brasero-medium.c:1755) Track 8 (session 1): type = 2 start = 161513 size = 15051 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 9 BraseroMedia: (at brasero-medium.c:1755) Track 9 (session 1): type = 2 start = 176564 size = 23127 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 10 BraseroMedia: (at brasero-medium.c:1755) Track 10 (session 1): type = 2 start = 199691 size = 6844 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 11 BraseroMedia: (at brasero-medium.c:1755) Track 11 (session 1): type = 2 start = 206535 size = 15857 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 12 BraseroMedia: (at brasero-medium.c:1755) Track 12 (session 1): type = 2 start = 222392 size = 33902 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 13 BraseroMedia: (at brasero-medium.c:1755) Track 13 (session 1): type = 2 start = 256294 size = 16250 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 14 BraseroMedia: (at brasero-medium.c:1755) Track 14 (session 1): type = 2 start = 272544 size = 14891 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 15 BraseroMedia: (at brasero-medium.c:1755) Track 15 (session 1): type = 2 start = 287435 size = 13222 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 16 BraseroMedia: (at brasero-medium.c:1755) Track 16 (session 1): type = 2 start = 300657 size = 11396 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 17 BraseroMedia: (at brasero-medium.c:1755) Track 17 (session 1): type = 2 start = 312053 size = 17810 BraseroMedia: (at brasero-medium.c:1645) Retrieving track information for 18 BraseroMedia: (at brasero-medium.c:1755) Track 18 (session 1): type = 2 start = 329863 size = 28030 BraseroMedia: (at brasero-medium.c:2070) Leadout reached 357893 BraseroMedia: (at brasero-medium.c:2781) Getting CD-TEXT BraseroMedia: (at scsi-read-toc-pma-atip.c:142) Undersized data (4) setting to max (65530) BraseroMedia: (at brasero-medium.c:2946) media is CD ROM closed with audio Initially this bug was reported on gvfs, see Bug 679821. If you think gvfs is doing wrong, please ignore this report.
Honestly if they change something on gvfs i would appreciate to have some information on the API change or a patch. Thanks for reporting the bug.
*** This bug has been marked as a duplicate of bug 679821 ***
(In reply to comment #1) > Honestly if they change something on gvfs i would appreciate to have some > information on the API change or a patch. There was no intentional change nor API change, this was a fallout from port to GDBus (i.e. rewriting non-trivial amount of code). Sadly the root issue is that there are no guarantees GVolumeMonitor should contain all information right after its creation (it's not even mentioned in the docs), the state is undefined. Given the ability to extend GIO volume monitoring functionality there might be backends requiring some time to gather all information or even doing async ops (which requires mainloop to be running). Anyway, please report any inconsistencies to gvfs, applications like Brasero depend heavily on the information we present.