Comment # 2 on bug 954143 from Wolfgang Bauer

(In reply to Ancor Gonzalez Sosa from comment #1)
> Last but not least, the absence of apper or the wrong filetype association
> in Plasma 5 are not YaST issues. Reassigning.

Well, we removed apper from the default installation patterns as it is still a
KDE4 application and the update notifier function doesn't work in Plasma5 (we
use plasma5-pk-updates for that now).
You can still install apper manually though with YaST, it is still included in
the distribution, and should add a file type association.

Installing Chrome won't work anyway though (without manually installing the
package's key beforehand), as libzypp got stricter with signature verification
and PackageKit won't handle that (that's already a problem in 13.2 with all
updates installed).

One problem here IMHO is that YaST's .desktop file that contains such a file
association for installing rpms has been removed in 13.2 (IIRC).
So depending how you look at it, it might also be seen as a YaST issue... ;-)