Comment # 12 on bug 981011 from Michael Andres

The log for PID 10496 fits to the initial backtrace and c#7:

> 2016-05-23 11:11:52 <1> mal(10496) [packagekit] pk-backend-zypp.cpp(zypp_get_package_by_id):884 bundle-lang-common-en;13.2-21.4;noarch;repo-oss
> 2016-05-23 11:11:52 <1> mal(10496) [packagekit] pk-backend-zypp.cpp(backend_get_update_detail_thread):2407 bundle-lang-common-en;13.2-21.4;noarch;repo-oss noSolvable
> ---------------------------(10520)---------------------------
> ...
> 2016-05-23 11:11:52 <1> mal(10520) [zypp] ZYppFactory.cc(readLockFile):221 read: Lockfile /var/run/zypp.pid has pid 10496 (our pid: 10520) 
> 2016-05-23 11:11:52 <1> mal(10520) [zypp] ZYppFactory.cc(isProcessRunning):193 Checking /proc/10496{[2-No such file or directory]}
> 2016-05-23 11:11:52 <1> mal(10520) [zypp] ZYppFactory.cc(zyppLocked):273 10496 is dead. Taking the lock file.

The log ends after 'pk-backend-zypp.cpp(backend_get_update_detail_thread):2407'
reported it found 'noSolvable' for
'bundle-lang-common-en;13.2-21.4;noarch;repo-oss'. The backend crashed and the
next PID 10520 finds the orphaned lock file of 10496.

The backend must check for zypp_get_package_by_id returning 'noSolvable' and do
whatever is appropriate in this situation.