-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CANNOT INSTALL DAEDALUS FEDORA XFCE #3147
Comments
Can you show me the output of |
Command Line: /usr/bin/python3 /usr/bin/dnfdragora-updater
|
It seems that the segfault happens in a C++ Can you show me |
Hello again, i think is no dnfgradora-updater problem, because i reinstall several version of fedora xfce only for try install daedalus inside, right now this is a new and fresh install from fedora xfce gruop install, and in the early hours of the day i try in a custom fedora server plus xfce inside and get the same result, here are the recent try for install, later coredump andn later coredump list bzip2: Caught a SIGSEGV or SIGBUS whilst decompressing. Possible causes are (most likely first): If you suspect this is a bug in bzip2, or are unsure about (2)
It is possible that the compressed file(s) have become corrupted. You can use the `bzip2recover' program to attempt to recover tar: Unexpected EOF in archive
[blackhero@nonet Downloads]$ coredumpctl list |
Okay, do you maybe have any idea why
|
Hello friends when i try to install multiple times in fedora xfce and get this result:
`./daedalus-5.3.0-59334-mainnet-44942bd51-x86_64-linux.bin
bzip2: Caught a SIGSEGV or SIGBUS whilst decompressing.
Possible causes are (most likely first):
(1) The compressed data is corrupted, and bzip2's usual checks
failed to detect this. Try bzip2 -tvv my_file.bz2.
(2) This computer has unreliable memory or cache hardware
(a surprisingly common problem; try a different machine.)
(3) A bug in the compiler used to create this executable
(unlikely, if you didn't compile bzip2 yourself.)
(4) A real bug in bzip2 -- I hope this should never be the case.
The user's manual, Section 4.3, has more info on (2) and (3).
If you suspect this is a bug in bzip2, or are unsure about (2)
or (3), feel free to report it to: [email protected].
Section 4.3 of the user's manual describes the info a useful
bug report should have. If the manual is available on your
system, please try and read it before mailing me. If you don't
have the manual or can't be bothered to read it, mail me anyway.
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
`
The text was updated successfully, but these errors were encountered: