# zypper digest errors & yast2 problems **URL:** \ **Category:** SLES Configure-Administer\ **Created:** [July 16, 2017, 7:40pm UTC](https://forums.suse.com/t/zypper-digest-errors-yast2-problems/30055 "2017-07-16T19:40:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![markusmoeller](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@markusmoeller](https://forums.suse.com/u/markusmoeller)\ **Post date:** [July 16, 2017, 7:40pm UTC](https://forums.suse.com/t/zypper-digest-errors-yast2-problems/30055/1 "2017-07-16T19:40:49Z")
Since the upgrade zypper and yast2 are broken. When I use zipper to install or update packages I get a digest error. Zypper doesn’t get a “wrong” digest it just doesn’t calculate any ☹ and the seg faults ( probably because the digest is empty) # zypper update Warning: Digest verification failed for file ‘updateinfo.xml.gz’ [/var/cache/zypp/raw/UpdatesAfFDdN/repodata/updateinfo.xml.gz] expected ea56add8fc0906735b589327ea516629ca40475d but got Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum ‘..’ is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. Segmentation fault On yast2 I get the following: yast2 sw\_single terminate called after throwing an instance of ‘YUIPluginException’ what(): Couldn’t load plug-in qt YaST got signal 6 at YCP file Wizard.ycp:708 /sbin/yast2: line 435: 23827 Aborted $ybindir/y2base $module “$@” “$SELECTED\_GUI” $Y2\_GEOMETRY $Y2UI\_ARGS Any idea what is wrong ? Normal rpm commands work. Thank you Markus ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [July 16, 2017, 8:21pm UTC](https://forums.suse.com/t/zypper-digest-errors-yast2-problems/30055/2 "2017-07-16T20:21:41Z")
Hi Try cleaning up rpm and zypper; ```auto rpm --rebuilddb zypper clean all zypper ref -f ``` ---
**Author:** ![markusmoeller](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@markusmoeller](https://forums.suse.com/u/markusmoeller)\ **Post date:** [July 16, 2017, 8:31pm UTC](https://forums.suse.com/t/zypper-digest-errors-yast2-problems/30055/3 "2017-07-16T20:31:11Z")
[QUOTE=malcolmlewis;38771]Hi Try cleaning up rpm and zypper; ` rpm --rebuilddb zypper clean all zypper ref -f `[/QUOTE] Unfortunately no change ☹ # rpm --rebuilddb # zypper clean All repositories have been cleaned up. # zypper ref -f Forcing raw metadata refresh Retrieving repository ‘Novell Online SLES11 SP4 Updates’ metadata [\] Warning: Digest verification failed for file ‘updateinfo.xml.gz’ [/var/cache/zypp/raw/Novell Online SLES11 SP4 UpdateswTP5LN/repodata/updateinfo.xml.gz] expected ea56add8fc0906735b589327ea516629ca40475d but got Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum ‘..’ is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. Segmentation fault Thank you Markus ---
**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\ **Post date:** [July 16, 2017, 8:31pm UTC](https://forums.suse.com/t/zypper-digest-errors-yast2-problems/30055/4 "2017-07-16T20:31:29Z")
markusmoeller Wrote in message: [color=blue] > Since the upgrade zypper and yast2 are broken. When I use zipper to > install or update packages I get a digest error. Zypper doesn’t get a > “wrong” digest it just doesn’t calculate any ☹ and the seg faults ( > probably because the digest is empty) > > # zypper update > > Warning: Digest verification failed for file ‘updateinfo.xml.gz’ > [/var/cache/zypp/raw/UpdatesAfFDdN/repodata/updateinfo.xml.gz] > > expected ea56add8fc0906735b589327ea516629ca40475d > but got > > Accepting packages with wrong checksums can lead to a corrupted system > and in extreme cases even to a system compromise. > > However if you made certain that the file with checksum ‘..’ is secure, > correct > and should be used within this operation, enter the first 4 characters > of the checksum > to unblock using this file on your own risk. Empty input will discard > the file. > > Segmentation fault > > On yast2 I get the following: > > yast2 sw\_single > terminate called after throwing an instance of ‘YUIPluginException’ > what(): Couldn’t load plug-in qt > YaST got signal 6 at YCP file Wizard.ycp:708 > /sbin/yast2: line 435: 23827 Aborted $ybindir/y2base > $module “$@” “$SELECTED\_GUI” $Y2\_GEOMETRY $Y2UI\_ARGS > > Any idea what is wrong ? > > Normal rpm commands work.[/color] In addition to Malcolm’s advice, it would be useful to know which repositories you have configured - please can you post the output from “zypper lr -u” . Can you also please elaborate “since the upgrade” - do you mean upgrading of a particular (set of) package(s) or from an earlier version and/or release of SLES? ## HTH. Simon Flood SUSE Knowledge Partner ----Android NewsGroup Reader---- [http://usenet.sinaapp.com/](http://usenet.sinaapp.com/) ---
**Author:** ![markusmoeller](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@markusmoeller](https://forums.suse.com/u/markusmoeller)\ **Post date:** [July 16, 2017, 9:18pm UTC](https://forums.suse.com/t/zypper-digest-errors-yast2-problems/30055/5 "2017-07-16T21:18:41Z")
[QUOTE=smflood;38773]markusmoeller Wrote in message: … In addition to Malcolm’s advice, it would be useful to know which repositories you have configured - please can you post the output from “zypper lr -u” . Can you also please elaborate “since the upgrade” - do you mean upgrading of a particular (set of) package(s) or from an earlier version and/or release of SLES? ## HTH. Simon Flood SUSE Knowledge Partner ----Android NewsGroup Reader---- [http://usenet.sinaapp.com/](http://usenet.sinaapp.com/)[/QUOTE] Sorry I should have mentioned that it was an upgrade from SLES11 SP2 to SP4 and I try now to install latest patches. # zypper lr -u # | Alias | Name | Enabled | Refresh | URI –±---------------------------------±---------------------------------±--------±--------±-------------------------------------------------------------------------------- 1 | Novell Online SLES11 SP4 Updates | Novell Online SLES11 SP4 Updates | Yes | No | [https://nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-i586/](https://nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-i586/) 2 | SLES11\_SDK\_DVD1\_1 | SLES11 SP4 SDK DVD1 | No | No | iso:///?iso=SLE-11-SP4-SDK-DVD-i586-GM-DVD1.iso&url=file:///export/ISOs/SLES11/ 3 | SLES11\_SP4\_DVD1 | SLES11 SP4 DVD1 | No | No | iso:///?iso=SLES-11-SP4-DVD-i586-GM-DVD1.iso&url=file:///export/ISOs/SLES11/ 4 | SLES11\_SP4\_DVD2 | SLES11 SP4 DVD2 | No | No | iso:///?iso=SLES-11-SP4-DVD-i586-GM-DVD2.iso&url=file:///export/ISOs/SLES11/ 5 | SLES11\_SP4\_SDK\_DVD2 | SLES11 SP4 SDK DVD2 | No | No | iso:///?iso=SLE-11-SP4-SDK-DVD-i586-GM-DVD2.iso&url=file:///export/ISOs/SLES11/ Markus ---
**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\ **Post date:** [July 16, 2017, 11:48pm UTC](https://forums.suse.com/t/zypper-digest-errors-yast2-problems/30055/6 "2017-07-16T23:48:15Z")
markusmoeller Wrote in message: [color=blue] > Sorry I should have mentioned that it was an upgrade from SLES11 SP2 to > SP4 and I try now to install latest patches.[/color] Did you upgrade directly from SLES11 SP2 to SLES11 SP4 or did you first upgrade to SLES11 SP3 and then to SLES11 SP4? From the above it sounds like you went directly from SLES11 SP2 to SLES11 SP4 which is not supported by SUSE … although I don’t think it’s the cause of your troubles here (though I am aware of random issues which haven’t been explained). [color=blue] > # zypper lr -u > > # | Alias | Name > > | Enabled | Refresh | URI > > –±---------------------------------±---------------------------------±--------±--------±-------------------------------------------------------------------------------- > 1 | Novell Online SLES11 SP4 Updates | Novell Online SLES11 SP4 Updates > | Yes | No | > [https://nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-i586/](https://nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-i586/) > > 2 | SLES11\_SDK\_DVD1\_1 | SLES11 SP4 SDK DVD1 > | No | No | > iso:///?iso=SLE-11-SP4-SDK-DVD-i586-GM-DVD1.iso&url=file:///export/ISOs/SLES11/ > > 3 | SLES11\_SP4\_DVD1 | SLES11 SP4 DVD1 > | No | No | > iso:///?iso=SLES-11-SP4-DVD-i586-GM-DVD1.iso&url=file:///export/ISOs/SLES11/ > > 4 | SLES11\_SP4\_DVD2 | SLES11 SP4 DVD2 > | No | No | > iso:///?iso=SLES-11-SP4-DVD-i586-GM-DVD2.iso&url=file:///export/ISOs/SLES11/ > > 5 | SLES11\_SP4\_SDK\_DVD2 | SLES11 SP4 SDK DVD2 > | No | No | > iso:///?iso=SLE-11-SP4-SDK-DVD-i586-GM-DVD2.iso&url=file:///export/ISOs/SLES11/[/color] If this is the complete output it suggest you upgraded by adding repos pointing at the various SLES11 SP4-related ISOs - is this correct? How did you then do the upgrade - perhaps just by installing updated packages? I also notice that in the above you have no active SLES11 SP4 Pool repo which could cause a problem when installing future packages but before we fix that I’d like to know how you upgraded. ## HTH. Simon Flood SUSE Knowledge Partner ----Android NewsGroup Reader---- [http://usenet.sinaapp.com/](http://usenet.sinaapp.com/)