[mythtv-users] Mythmusic fail
malibyte56 at gmail.com
Wed Nov 2 06:37:36 UTC 2022
>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
>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!
>The menu for accessing *mythmusic* is:
>mthfrontend > Media Library > Listen to Music
** Not there! **
>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
>select * from settings where value='MusicDBSchemaVer';
>This is what I get on MythTV v32-fixes:
>MariaDB [mythconverg]> select * from settings where
>| 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.
For the past seven or eight times I have opened mythfrontend, it has asked
me to upgrade the music database schema. Each time I have allowed it to
upgrade, but it apparently doesn't "take".
[rcs at vader: ~]$ sudo mysql -p
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 649
Server version: 8.0.31-0ubuntu0.22.04.1 (Ubuntu)
mysql> use mythconverg
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
mysql> select * from settings where value='MusicDBSchemaVer';
| value | data | hostname |
| MusicDBSchemaVer | 1024 | NULL |
1 row in set (0.00 sec)
I will try removing/purging mythmusic as a first step.
Why would this make MythWeb non-functional? Just curious.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users