[mythtv-users] Mythmusic fail

Stephen Worthington stephen_agent at jsw.gen.nz
Mon Oct 31 02:07:30 UTC 2022


On Sun, 30 Oct 2022 16:39:07 -0700, you wrote:

>Hi, all -
>Long-time Myth user here - >15 years.   Things have worked pretty well thus
>far, so haven't needed to post much.
>I'm running 32-fixes, and just upgraded the OS from Ubuntu 20.04 to 22.04.
>It went quite painlessly compared to the jump from 18.04 to 20.04.
>
>However, the only app not working is Mythweb.  I also have noticed that
>every time I fire up the frontend it asks me to upgrade my music database
>schema.  I never use Mythmusic, as I have other utilities for playing my
>music collection.  But I see through some posts back in January that I have
>to fix Mythmusic to get Mythweb to work on 22.04.
>
>There is nothing in the frontend about the music library or Mythmusic.
>Mythtv-setup lists the correct directory for my music files, but there is
>no reference to Mythmusic, or configuring it, at all.
>
>It is installed but apparently not able to be used.
>
>Reading package lists... Done
>Building dependency tree... Done
>Reading state information... Done
>mythmusic is already the newest version
>(2:32.0+fixes.202210281018.ba52c13223~ubuntu22.04.1).
>0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
>Please advise as to how I can get this running...thanks in advance!
>
>*__________________________________*
>
>*Bob*

The menu for accessing mythmusic is:

mythfrontend > Media Library > Listen to Music

If you do not have that menu item when the mythmusic package is
installed, there is something seriously wrong.

I am not sure that removing the mythmusic package would fix your
problem, as the database tables would likely still remain.  Maybe
purging mythmusic would work.  However, it would be better to get the
music database tables upgraded.

The upgrade of database tables for frontend-only modules like
mythmusic happens when mythfrontend is next run after the module has
been upgraded and requires a database upgrade.  Database upgrades for
most tables normally happen when mythtv-setup or mythbackend gets run
for the first time after the packages have been updated, but
frontend-only modules are different.  So, when mythfrontend asks about
upgrading the mythmusic tables, did you say yes?  If not, do that now.

A last resort would be to purge the mythmusic package and then
manually remove all the mythmusic tables from the database.  Then you
would probably also need to remove all the music rows from the
settings table, especially the MusicDBSchemaVer one.  But there is no
guarantee that would work properly, as it would be bypassing all the
usual protections that keep the database sane.

What is your current MusicDBSchemaVer value?  Use these commands to
see it:

sudo mysql
use mythconverg
select * from settings where value='MusicDBSchemaVer';
quit

This is what I get on MythTV v32-fixes:

MariaDB [mythconverg]> select * from settings where
value='MusicDBSchemaVer';
+------------------+------+----------+
| value            | data | hostname |
+------------------+------+----------+
| MusicDBSchemaVer | 1025 | NULL     |
+------------------+------+----------+
1 row in set (0.001 sec)

If you are getting a smaller number than 1025, the mythmusic tables
still need upgrading.


More information about the mythtv-users mailing list