Comment # 4 on bug 953614 from Michael Andres

> [/var/log/zypp/history]
> 2015-10-24 19:56:45|install|MozillaFirefox                    |...|repo-update|
> 2015-10-24 19:58:11|install|MozillaFirefox-translations-common|...|repo-update|
> ...
> 2015-11-04 18:26:48|install|MozillaFirefox                    |...|Mozilla|
> 2015-11-04 18:28:44|install|MozillaFirefox-translations-common|...|Mozilla|

The history file reveals the reason why zypper does not automatically perform
the update. The previously installed version came from the official update
repos (repo-update; vendor openSUSE), the new version from repo Mozilla (vendor
obs://build.opensuse.org).

As vendor changes are not performed automatically, zypper omitted the firefox
update, which was right. 

If you had executed 'zypper up MozillaFirefox
MozillaFirefox-translations-common' zypper would have asked you to confirm the
vendor change.


Now to PK:
> $ grep -- '--root' pk_backend_zypp
> 2015-11-03 17:37:34 ... 'rpm' '--root' .../libzypp-14.40.2-29.2.x86_64.rpm'
> 2015-11-03 17:37:46 ... 'rpm' '--root' .../zypper-aptitude-1.11.34-25.2.noarch.rpm'
> 2015-11-03 17:37:48 ... 'rpm' '--root' .../zypper-log-1.11.34-25.2.noarch.rpm'
> 2015-11-03 17:37:49 ... 'rpm' '--root' .../zypper-1.11.34-25.2.x86_64.rpm'

Those are the last installs mentioned in the pk_backend_zypp log, and you also
find them in the zypp/history file.

According to the history MozillaFirefox was installed the next day at
2015-11-04 18:26:48. But this install is neither in the zypper nor in the PK
log.


A closer look to the screenshot reveals 'Software Manager YaST' in the title
line. So maybe the yast logs can help. Please attach:

  /var/log/YaST2/y2log

(test with "grep -- '--root' /var/log/YaST2/y2log | grep MozillaFirefox" if the
log actually contains the installation. If the logs were already rotated it may
be in y2log-1.gz or y2log-2.gz or...)