http://bugzilla.suse.com/show_bug.cgi?id=1029527 http://bugzilla.suse.com/show_bug.cgi?id=1029527#c14 --- Comment #14 from Michael Andres <ma@suse.com> --- @V3 gpg key: In the log I can see that initially 'gpg-pubkey-3d25d3d9-36e12d04' was present in the rpm database. This is a well known old V3 version gpg key and it's presence in the database is causing the 'Unsupported version of key' warnings. If the V3 warnings are gone, the key was most probably removed or updated (this is not visible in the log). In case of doubt, use 'rpm -q gpg-pubkey-3d25d3d9-36e12d04' to check whether is present and 'rpm -e gpg-pubkey-3d25d3d9-36e12d04' to remove it. The key disturbs and is not needed anymore. @rpm error: In the log I see rpm-4.14.2.1-4.1.x86_64.rpm being installed during the update. This new rpm version is then used to further update a bunch of packages until it fails on xscope-1.4.1-6.1.x86_64 ==> xscope-1.4.1-3.15.x86_64(openSUSE-tumbleweed-oss) In fact rpm 'was killed by signal 11 (Neoprávněný přístup do paměti (SIGSEGV))'. When reporting the error libzypp collects whatever rpm wrote to it's stderr, assuming it may be helpful to figure out the reson. But here I suppose the presence of the V3 warning is just a coincidence and not the actual reason for rpms crash. It's a known fact that mixing especially libraries from opensuse and tumbleweed does not work well. If the issues are gone after the system was fully updated to TW this may have been the reason. If the issues persist we may need to have a closer look at rpm. As Michael suggested in c#9, 'rpm --rebuilddb' should be used to make sure rpm and the rpm db are ok. If this does not succeed your system is in danger being damaged again. -- You are receiving this mail because: You are on the CC list for the bug.