Can you try to run `picard -d` from a terminal, and copy or attach the output here?

Also make sure that your system is full up-to-date with Mageia 6 using `urpmi --auto-update`.

On a Mageia 6 system (not upgraded, direct install from -back then- Cauldron), picard seems to start up fine.

Thanks for the reply.  

I had already performed the urpmi --auto-update command.  

Here is the output from picard -d ..
]$ picard -d
Traceback (most recent call last):
  File "/bin/picard", line 2, in <module>
    from picard.tagger import main; main('/usr/share/locale', True)
  File "/usr/lib64/python2.7/site-packages/picard/tagger.py", line 65, in <module>
    from picard.formats import open as open_file
  File "/usr/lib64/python2.7/site-packages/picard/formats/__init__.py", line 157, in <module>
    from picard.formats.id3 import (
  File "/usr/lib64/python2.7/site-packages/picard/formats/id3.py", line 21, in <module>
    import mutagen.mp3
  File "/usr/lib/python2.7/site-packages/mutagen/mp3/__init__.py", line 14, in <module>
    from mutagen._util import MutagenError, enum, BitReader, BitReaderError, \
ImportError: cannot import name convert_error

This was fixed using:

]# pip install -U mutagen

This was fixed using:

]# pip install -U mutagen

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Thanks for the info, but that's not a proper fix. If picard needs mutagen, the RPM needs to be update to reflect this dependency.

Summary: [SOLVED] Musicbrainz Picard does not launch after upgrade to Mageia 6 => Musicbrainz Picard does not launch after upgrade to Mageia 6, missing mutagen dependency
Resolution: FIXED => (none)
Status: RESOLVED => REOPENED

Well it seems the dependency is already there:

# LC_ALL=C urpme mutagen
To satisfy dependencies, the following 2 packages will be removed (5.8MB):
  mutagen-1.32-1.mga6.noarch
  picard-1.3.2-3.mga6.x86_64
   (due to missing mutagen)

What's the output of `rpm -qa | grep mutagen` on your system?

This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

CC: (none) => ouaurelien
Resolution: (none) => OLD
Status: REOPENED => RESOLVED