https://bugs.kde.org/show_bug.cgi?id=402773
--- Comment #5 from Myriam Schweingruber <myr...@kde.org> --- (In reply to hong from comment #3) > thank you for the quick response. > i did the reinstall but it did not help. > here's the output, perhaps you can detect what is missing. > especially those 2 lines about 'unknown media types'? > > sudo apt-get install --reinstall amarok > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 5 not upgraded. > Need to get 0 B/9,058 kB of archives. > After this operation, 0 B of additional disk space will be used. > debconf: unable to initialize frontend: Dialog > debconf: (Dialog frontend requires a screen at least 13 lines tall and 31 > columns wide.) > debconf: falling back to frontend: Readline > (Reading database ... 273197 files and directories currently installed.) > Preparing to unpack .../amarok_2%3a2.9.0-0ubuntu2_amd64.deb ... > Unpacking amarok (2:2.9.0-0ubuntu2) over (2:2.9.0-0ubuntu2) ... > Processing triggers for mime-support (3.60ubuntu1) ... > Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ... > Setting up amarok (2:2.9.0-0ubuntu2) ... > Processing triggers for libc-bin (2.27-3ubuntu1) ... > Processing triggers for man-db (2.8.3-2ubuntu0.1) ... > Processing triggers for shared-mime-info (1.9-2) ... > Unknown media type in type 'all/all' > Unknown media type in type 'all/allfiles' > Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ... > > i am seeing identical "Current Track" problem on 2 different machines. > Amarok, except for this, looks and plays just great! normally there should be more than one package for Amarok to install, if the packaging was done correctly by the distribution. As for the unknown media types I have no idea what this refers to, it is most likely not Amarok related anyway, as these are MIME types we have no control over. -- You are receiving this mail because: You are watching all bug changes.
