Red Hat Bugzilla – Bug 977807
[abrt] tar-1.26-12.fc18: set_next_block_after: Process /usr/bin/tar was killed by signal 6 (SIGABRT)
Last modified: 2014-04-05 22:34:59 EDT
Description of problem:
I just issued a command - I know now it's incorrect - but it should not make a system crash anyway:
tar -tWf new.tgz
Version-Release number of selected component:
cmdline: tar -tWf new.tgz
runlevel: N 5
Thread no. 1 (4 frames)
#2 set_next_block_after at buffer.c:603
#3 verify_volume at compare.c:596
#4 close_archive at buffer.c:1050
#5 read_and at list.c:287
Created attachment 765036 [details]
Created attachment 765037 [details]
Created attachment 765038 [details]
Created attachment 765039 [details]
Created attachment 765040 [details]
Created attachment 765041 [details]
Created attachment 765042 [details]
Created attachment 765043 [details]
Created attachment 765044 [details]
Created attachment 765045 [details]
Thanks for the report. Its pretty easily reproducible. I tried to raise an
upstream ticket here:
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This issue was fixed upstream by these commits:
It is fixed rawhide (new tar release 1.27). Could be worth fixing in F19 and
(In reply to Pavel Raiskup from comment #13)
> This issue was fixed upstream by these commits:
> It is fixed rawhide (new tar release 1.27). Could be worth fixing in F19 and
FWIW, the second commit is 8a834dfa10 (badly pasted links).
tar-1.26-31.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tar-1.26-31.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
tar-1.26-31.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.