Comment # 1 on bug 1201348 from
Debugging revealed that this is caused by a zypper segfault. The zypper
segfault is independent of transactional-update and also happens when updating
that old snapshot in read-write mode with zypper directly.

Fabian's suspicion is that the crash is caused by a bug in zypper logging,
which has been fixed for a while already... That doesn't help in this case
however as the active zypper updating the packages is still the old version.

Assigning back to Dominique for clarification on how to proceed.


You are receiving this mail because: