Skip to main content

Unknown media type in type Fix

Problem
Do you see the following every time you go to emerge a package or run update-mime-database?
Unknown media type in type 'all/all'

Unknown media type in type 'all/allfiles'

Unknown media type in type 'uri/mms'

Unknown media type in type 'uri/mmst'

Unknown media type in type 'uri/mmsu'

Unknown media type in type 'uri/pnm'

Unknown media type in type 'uri/rtspt'

Unknown media type in type 'uri/rtspu'

Unknown media type in type 'fonts/package'

Unknown media type in type 'interface/x-winamp-skin'
Want it to go away? Here's how.

Solution
Open up /usr/share/mime/packages/kde.xml or wherever it's located for you. You just need to delete the areas that are messing up. To be honest, I don't know what these sections are actually used for. In fact, I have absolutely no idea what this might do to your system, so keep a backup copy of this file just in case. The file is pretty easy to read, if you understand XML or even HTML you should get the idea on how to edit this. Everything from to just needs to be deleted.
  
    all files and folders
  
  
    all files
That section right there is the problem. Just delete it. If anything else gives you crap, delete that too. Mainly just search around the kde.xml and look for sections like that. Delete anything that shows up as an unknown media type. If you need to view the error list again, to see if you're missing anything, run the following and it will output all of the "Unknown media type in type" errors.
update-mime-database /usr/share/mime

  
    
    compressed Winamp skin
That block of XML can go to hell too. When you're done blasting these sections away, run the above command again and you should get no errors. I'm not sure what application causes this error exactly, but I think it's kde-libs.
Labels:

Comments

Post a Comment

https://gengwg.blogspot.com/

Popular posts from this blog

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into ...
Post a Comment
Read more

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checkin...
2 comments
Read more