control: severity -1 important Hi Vincent,
this only affects users that actually use Wine (if at all, see below). Only then the .desktop file gets created (e.g. on running "winecfg" the first time). Downgrading to important for now. Funnily I can't reproduce this here. Despite having the problematic wine entry in /home my system still uses firefox to open html files. Even after removing and recreating the wine .desktop entries. Therefore I also can't reproduce the specific crash. I'm still working on understanding mime et al.: AFAIK the .desktop files are somehow generated by winemenubuilder. >From the .desktop files the system (not Wine itself) generates a mimeinfo.cache file, which basically is a reverse index of them. It seems the systemwide /usr/share/applications/mimeinfo.cache has precendence over ~/.local/share/applications/mimeinfo.cache (here?): $ grep htm ~/.local/share/applications/mimeinfo.cache application/vnd.ms-htmlhelp=wine-extension-chm.desktop; application/x-extension-htm=wine-extension-htm.desktop; application/x-extension-html=wine-extension-html.desktop; $ grep htm /usr/share/applications/mimeinfo.cache application/xhtml+xml=firefox-esr.desktop; application/xhtml_xml=chromium.desktop; text/html=firefox-esr.desktop;chromium.desktop; $ xdg-mime query default text/html userapp-Firefox-1M35PY.desktop No idea (yet) where/what this userapp-Firefox-1M35PY.desktop exactly is. Outlook: I think we want to keep winemenubuilder generally because that should be used during the installation of Windows applications for creating specific wanted file type associations. But we want to patch out the generation of these general purpose file type associations for e.g. *.html or (imo even more annoying) *.txt. That might even be proposed to upstream. Greets jre