|
application/vnd.debian.binary-package
and
org.kde.apper.desktop
Is what I get on a clean installation.
Perhaps it is different when installing from the live CD? I haven't tried installing from the standard installer with Bullseye, but I am pretty sure the with Buster I would get the same result even in the standard install. I'd be happy to test it if it would
be any help.
But I think it isn't so much a problem with mime associations in general. There seems to be some outstanding issues with apper when I glance through the bug reports. Switching the file association to discover works fines. And when I do so I get the same results
you do when running
xdg-mime query filetype XXX.deb
org.kde.discover.desktop
Thanks,
Caleb
On Mon, 19 Apr 2021 17:02:55 +0900 Norbert Preining <norbert@preining.info> wrote:
> Jo > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? Tried to install a .deb by double clicking on it in Dolphin > > * What was the outcome of this action? Nothing happens > > With an existing XXX.deb (one that you wanted to open), what does (on > the command line) > xdg-mime query filetype XXX.deb > say? > > In my case it is > application/vnd.debian.binary-package > > After that, what does > xdg-mime query default $(xdg-mime query filetype XXX.deb) > say? > > In my case it is > org.kde.discover.desktop > > This is a problem of mime type associations, and this is - honestly > spoken - completely broken in Debian at the moment. THere is work going > on but I am not sure how far this has proceeded. > > Best > > Norbert > > -- > PREINING Norbert https://www.preining.info > Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev > GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 > > &references=<[🔎] 161879847068.4985.8620406809901655187.reportbug@caleb-omen> <[🔎] YH05L10oK7HqXqgn@bulldog.preining.info> |