Bug 1130288 - Corrupted libX11-xcb1-1.6.5-lp150.2.3.1.x86_64 file ?
Summary: Corrupted libX11-xcb1-1.6.5-lp150.2.3.1.x86_64 file ?
Status: RESOLVED DUPLICATE of bug 1130292
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Leap 15.0
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-24 14:11 UTC by Tim Jones
Modified: 2019-03-25 10:41 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
sndirsch: needinfo? (b631093f-779b-4d67-9ffe-5f6d5b1d3f8a)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Jones 2019-03-24 14:11:00 UTC
See below.  I tried the "retry" option but the same occured.


Warning: Digest verification failed for file 'libX11-xcb1-1.6.5-lp150.2.3.1.x86_64.rpm'
[/var/tmp/AP_0xpfhSaJ/x86_64/libX11-xcb1-1.6.5-lp150.2.3.1.x86_64.rpm]

  expected 22038e5981488f2a71256711cf8760a72f463b60ab68094580cd1147ee1aab31
  but got  1724b38cc8feab15b2d6b1e8c6d1b080bf530fa0366c59cea9884b65cc666dc3

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 '1724..' 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.


Package libX11-xcb1-1.6.5-lp150.2.3.1.x86_64 (openSUSE-Leap-15.0-Update) seems to be corrupted during transfer. Do you want to retry retrieval?
Comment 1 Stefan Dirsch 2019-03-25 10:36:03 UTC
I guess you're doing a security update here, right? Please remove /var/tmp/AP_0xpfhSaJ/x86_64/libX11-xcb1-1.6.5-lp150.2.3.1.x86_64.rpm
and try again. Make also sure that your root filesystem ("/") is *not* full.
Comment 2 Marcus Meissner 2019-03-25 10:41:31 UTC
dup of 1130292

please "zypper refresh" and try again.

*** This bug has been marked as a duplicate of bug 1130292 ***