Comments

373 Comments

Thank you for testing the update!

Thank you for testing the update!

Thank you for testing the update!

This update has been unpushed.

Bug #587817 does not seem to be fixed with this update:

$ rpm -q valgrind           
valgrind-3.18.1-1.fc34.x86_64
valgrind-3.18.1-1.fc34.i686

$ sh valgrind-fork-sigsegv.c
valgrind-fork-sigsegv.c: line 4:  4845 Segmentation fault      (core dumped) valgrind -q ./a.out
BZ#587817 valgrind gets SIGSEGV on a failure of fork()

Thank you all for feedback! This update seems to be on its way to stable now.

Any idea how to unblock this security update? I tried to click the "Re-Trigger Tests" button to no avail.

Thank you for testing the update!

Thank you for testing the update!

Thank you for testing the update!

@boycottsystemd1 The server in question does not like the User-Agent header that lynx uses by default. The following command works just fine:

$ lynx -useragent=lynx https://fedoramagazine.org/announcing-fedora-34/

@boycottsystemd1 Thanks for feedback! Exactly this happens with lynx-2.8.9-9.fc33 as well. Whatever the issue is has nothing to do with this update.

Thank you for testing the update!

Thank you for testing the update!

Thank you for testing the update!

User Icon kdudka commented & provided feedback on nano-5.8-3.fc33 4 months ago

Thank you for testing the update!

Thank you for testing the update!

User Icon kdudka commented & provided feedback on nano-5.8-3.fc34 4 months ago

Thank you for testing the update!

Thank you for testing the update!

User Icon kdudka commented & provided feedback on nano-5.8-2.fc33 5 months ago

Thank you for testing the update!