Music app not detecting SD card content after Phone Update:OTA-7

[Tafari]

After the most recent update my SD card content is no longer detected by the Music app, able to browse the media fine using File Manager app as previously. I verified the problem is related to the app by installing PhoenixPlayer app which detects the content fine. Currently using the BQ Aquaris 4.5 handset

[Antoine Lorieau (toinelorieau)]

Hello, I have exactly the same problem since the last OTA update three days ago...
It seems to affect essentially the Music core app that can't find the music on the SD Card...
Does anyone have an idea on how to fix this?

Thanx

PS: using BQ Aquaris 4.5 and Ubuntu 15.04 desktop

[Andrew Hayzen (ahayzen)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Would you be able to provide the following logs (either as an attachment to this bug report or a link to pastebin) as this will help with debugging:
/home/phablet/.cache/upstart/application-click-com.ubuntu.music_music_2.2.910.log
/home/phablet/.cache/upstart/mediascanner-2.0.log

Please let me know if you need instructions to retrieve these files.

[Victor Thompson (vthompson)]

Could we get someone with a BQ Aquaris 4.5 and an SD card to try to see if this is a regression in OTA7?

[Dan González (gonrodda)]

In my case Music app continues to show and play SD music files without problem after OTA7 update. I've not added any files since then though.

Any steps to reproduce this bug or it's just the songs on SD disappearing from Music?

BQ45r26.

[Tafari (marlonaleslie)]

Hi Andrew, i will grab the logs of my phone and attach to this forum, i will let you know if i have any problems getting hold of them.

[Markcortbass (markcortbass)]

I also have this problem. This is my music-app log:
http://paste.ubuntu.com/12973647/

[Victor Thompson (vthompson)]

Thanks Markcortbass! But unfortunately the music app log doesn't seem to have any information related to what you are seeing. Could someone please attach the following two files from a device that exhibits this bug?

1. /home/phablet/.cache/upstart/mediascanner-2.0.log
2. /home/phablet/.cache/mediascanner-2.0/mediastore.db

[Tafari (marlonaleslie)]

Sorry for the delay all, files attached from my phone.

[Tafari (marlonaleslie)]

and here's the mediastore file

[Tafari (marlonaleslie)]

I also have version 2-7 of the mediascanner log on my phone... let me know if you would like me to attach the others.

[Tafari (marlonaleslie)]

appears you may need all versions so attaching them for you now...

[Tafari (marlonaleslie)]

version 3

[Tafari (marlonaleslie)]

version 4

[Tafari (marlonaleslie)]

version 5

[Tafari (marlonaleslie)]

version 6

[Tafari (marlonaleslie)]

version 7

[Tafari (marlonaleslie)]

Let me know if you require anything else

[Tafari (marlonaleslie)]

btw from attachments, mediascanner-2.0.log.6 refers to the time (or just after) the system update at 2015-10-20 9:15:13. mediascanner-2.0.log.5 was the point at which i tried to open the Music app after the update, 2015-10-20 9:37:58... mediascanner-2.0.log.7 shows my great track list i've been without since the update :-)

[Markcortbass (markcortbass)]

This is my Log file:

[Markcortbass (markcortbass)]

And this is my mediastore file:

[Markcortbass (markcortbass)]

I see this error:

Mediascanner service starting at 2015-10-27 8:44:38.

Volume /media/phablet/UBUNTU-SD was mounted.
terminate called without an active exception

[Jean-Baptiste Lallement (jibel)]

Similar message in Tafari's logs (mediascanner-2.0.log.5.gz):

Volume /media/phablet/BFEB-2728 was mounted.
terminate called after throwing an instance of 'std::runtime_error'
  what(): UNIQUE constraint failed: media.id

Mediascanner service starting at 2015-10-20 10:41:49.

Volume /media/phablet/BFEB-2728 was mounted.
terminate called without an active exception

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jonas Platte (jplatte)]

Here's the mediastore.db database as requested on IRC.

[Tafari (marlonaleslie)]

Latest OTA-8 update has resolved this problem, thanks all!