Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42506 - [keepass] "Unknown media type in type" errors during installation

Attached to Project: Community Packages
Opened by Brendan (watricky) - Thursday, 23 October 2014, 08:02 GMT
Last edited by Timothy Redaelli (tredaelli) - Tuesday, 04 November 2014, 16:09 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Timothy Redaelli (tredaelli)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Installation for keepass results in mime errors/warnings being displayed. Similar issues in the past affecting other packages indicates that this output is normally suppressed.

See:
https://bbs.archlinux.org/viewtopic.php?id=79567
https://bbs.archlinux.org/viewtopic.php?id=154398
https://bbs.archlinux.org/viewtopic.php?id=166743

Additional info:
* package version(s)
[2014-10-23 08:05] [PACMAN] upgraded keepass (2.27-1 -> 2.28-1)
* config and/or log files etc.

See full pacman output in attachment.

Steps to reproduce:

~ $ sudo pacman -Syu
:: Synchronising package databases...
core 116.9 KiB 3.17M/s 00:00 [#######################################################] 100%
...
[snip]
...
(1/7) upgrading keepass [#######################################################] 100%
Unknown media type in type 'chemical/x-alchemy'
Unknown media type in type 'chemical/x-cache'
Unknown media type in type 'chemical/x-cactvs-ascii'
Unknown media type in type 'chemical/x-cactvs-binary'
Unknown media type in type 'chemical/x-cactvs-table'
Unknown media type in type 'chemical/x-cdx'
Unknown media type in type 'chemical/x-cdxml'
Unknown media type in type 'chemical/x-chem3d'
Unknown media type in type 'chemical/x-cif'
Unknown media type in type 'chemical/x-cml'
Unknown media type in type 'chemical/x-daylight-smiles'
...
[etc]
   pacmanlog-terminal.log (6.6 KiB)
   pacmanlog-excerpt.log (7.2 KiB)
This task depends upon

Closed by  Timothy Redaelli (tredaelli)
Tuesday, 04 November 2014, 16:09 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Thursday, 23 October 2014, 08:35 GMT
The problem really isn't in keepass, it's in whatever you have installed that is trying to register those mime types. Like you mentioned, the other install files simply suppress the errors, so you don't see them. Out of curiosity, what does `grep -l 'chemical/x-cache' /usr/share/applications/*` show?
Comment by Brendan (watricky) - Thursday, 23 October 2014, 09:22 GMT
I apologise in advance if this is too much information. ;)

grep -l 'chemical/x-cache' shows no results
grep -l 'chemical/x' shows:
/usr/share/applications/avogadro.desktop
/usr/share/applications/mimeinfo.cache

$ pacman -Qo /usr/share/applications/avogadro.desktop
/usr/share/applications/avogadro.desktop is owned by avogadro 1.1.1-3

$ pacman -Qo /usr/share/applications/mimeinfo.cache
error: No package owns /usr/share/applications/mimeinfo.cache

$ pacman -Qi avogadro | grep 'Dep\|Optional\|Required'
Depends On : openbabel python2-pyqt boost-libs glew python2-numpy
Optional Deps : None
Required By : None
Optional For : None

According to my pacman log, avogadro was originally installed along with KDE when I first installed my system:
[2012-12-30 17:05] Running 'pacman -S kde-meta'
... [snip] ...
[2012-12-30 17:17] installed avogadro (1.1.0-1)
... [snips] ...
[2013-01-07 20:57] upgraded avogadro (1.1.0-1 -> 1.1.0-2)
[2013-01-29 08:38] upgraded avogadro (1.1.0-2 -> 1.1.0-3)
[2013-04-03 13:39] upgraded avogadro (1.1.0-3 -> 1.1.0-4)
[2013-07-23 19:22] [PACMAN] upgraded avogadro (1.1.0-4 -> 1.1.0-5)
[2013-12-08 16:01] [PACMAN] upgraded avogadro (1.1.0-5 -> 1.1.0-6)
[2014-01-20 07:41] [PACMAN] upgraded avogadro (1.1.0-6 -> 1.1.1-1)
[2014-02-11 07:31] [PACMAN] upgraded avogadro (1.1.1-1 -> 1.1.1-2)
[2014-09-08 07:58] [PACMAN] upgraded avogadro (1.1.1-2 -> 1.1.1-3)
Comment by Doug Newgard (Scimmia) - Thursday, 23 October 2014, 09:51 GMT
Doesn't seem to be there. How about grepping through /usr/share/mime/packages? Or maybe something in /usr/local?
Comment by Brendan (watricky) - Thursday, 23 October 2014, 11:28 GMT
Found it there - similar data:

$ grep -R 'chemical/x-cache' /usr/share/mime/packages/
/usr/share/mime/packages/chemical-mime-data.xml: MIME-Type: chemical/x-cache
/usr/share/mime/packages/chemical-mime-data.xml: <mime-type type="chemical/x-cache">
$ pacman -Qo /usr/share/mime/packages/chemical-mime-data.xml
/usr/share/mime/packages/chemical-mime-data.xml is owned by chemical-mime-data 0.1.94-7
$ pacman -Qi chemical-mime-data | grep 'Dep\|Optional\|Required\|Reason'
Depends On : xdg-utils gnome-mime-data hicolor-icon-theme
Optional Deps : None
Required By : None
Optional For : None
Install Reason : Installed as a dependency for another package

pacman log shows it was installed during an -Syu upgrade:
[2013-02-13 13:03] Running 'pacman -Syu'
... [snip] ...
[2013-02-13 13:15] installed chemical-mime-data (0.1.94-6)
... [snip] ...
[2014-07-01 07:16] [PACMAN] upgraded chemical-mime-data (0.1.94-6 -> 0.1.94-7)
Comment by Brendan (watricky) - Thursday, 23 October 2014, 11:32 GMT
I don't use KDE any more - that is possibly related. Perhaps I don't need the chemical-mime-data package installed any more either.

Regarding suppressing the error, it is starting to sound like it is actually the wrong procedure. Perhaps it would be better to parse the error/warning and to give the user output they can use intuitively to find the cause (rather than have us pester you guys). ;)

[edit] - can haz grammar
Comment by Doug Newgard (Scimmia) - Thursday, 23 October 2014, 12:47 GMT
Yep, looks like the problem is actually in chemical-mime-data. Doesn't look like you actually need it (I would suggest running pacman -Qdt to see what else you have left over). If you're ambitious, you can try reporting this upstream. From what I gather, the warnings are harmless which is why suppressing them seems to be the normal course of action.

Loading...