correct folder depth property not being read from HAL

Bug #71784 reported by Alex Sutcliffe
2
Affects Status Importance Assigned to Milestone
Banshee
Invalid
Medium
banshee (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: banshee

y mass storage device - lsusb shows:

Bus 001 Device 007: ID 10d6:1100 Actions Semiconductor Co., Ltd MPMan MP-Ki 128
MP3 Player/Recorder

only supports playback from directories to a depth of 1 on the filesystem so I
added the line:

<append key="portable_audio_player.folder_depth" type="int">0</append>

to the appropriate section in 10-usb-music-players.fdi

When dragging a song to the device eg AM 180 fro mthe album Under the Western
Freeway by Grandaddy - the file gets created in the following path:

G/Gr/Gra/Gran/Grand/Granda/Grandad/Grandaddy/Under\ the\ Western\ Freeway/

This would suggest that the folder depth has been set to 10. Sure enough,
checking the value returned by:

player_device.GetPropertyInteger("portable_audio_player.folder_depth");

shows that it returns 10. This happens regardless of the value in the fdi file
ie if folder depth is set to 3, it will still return 10

Steps to reproduce:
1. Unplug mass storage device
2. Add section <append key="portable_audio_player.folder_depth"
type="int">0</append> to the section of 10-usb-music-players.fdi for your
player
3. Plug the device in and start banshee
4. Attempt to copy a song from your library to the mass storage player
5. Check where the file has actually been created on the filesystem for your
mas storage player

Actual results:
Song will be created in a folder such as:

G/Gr/Gra/Gran/Grand/Granda/Grandad/Grandaddy/Under\ the\ Western\ Freeway/

Expected results:
Since the folder depth property has been set to 0, the file should be in the
root directory of the mass storage players filesystem.

Does this happen every time?
Yes

Changed in banshee:
status: Unknown → Unconfirmed
Changed in banshee:
status: Unconfirmed → Confirmed
Changed in banshee:
status: Confirmed → Rejected
Revision history for this message
Sebastian Dröge (slomo) wrote :

Rejecting this bug as it was also reject upstream

Changed in banshee:
status: Unconfirmed → Rejected
Changed in banshee:
importance: Unknown → Medium
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.