Bug 2309284

Summary: screen 5.0.0 doesn't show/log broadcast messages
Product: [Fedora] Fedora Reporter: Frantisek Sumsal <fsumsal>
Component: screenAssignee: Josef Ridky <jridky>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: jridky, lnykryn, phracek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-06-08 16:02:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frantisek Sumsal 2024-09-02 18:22:20 UTC
Description of problem:
In our upstream test suite one of our test started recently failing on Fedora Rawhide. After some debugging it looks like screen 5.0.0 doesn't log broadcast/wall messages anymore in other screens, and when such message is issued it garbles the current screen. Downgrading to screen-4.9.1-1.fc40.x86_64 makes everything work as expected.

Version-Release number of selected component (if applicable):
screen-5.0.0-1.fc42.x86_64

How reproducible:
always

Steps to Reproduce:
# screen -L -Logfile screen.log
## Create a second screen (C-a c) and issue `shutdown -r` in the newly created screen

Actual results:
The broadcast message gets overlaid on top of the current screen, making the text garbled. There's no broadcast message in the first screen.

Output from the terminal:
```
[root@vm-10-0-187-183 ~]# shutdown -r

[root@vm-10-0-187-183 ~]# t.redhat.com on pts/2 (Mon 2024-09-02 14:14:42 EDT):

The system will reboot at Mon 2024-09-02 14:15:42 EDT!

Reboot scheduled for Mon 2024-09-02 14:15:42 EDT, use 'shutdown -c' to cancel.
```

Output from the screen log file:
```
# cat screen.log 
root@vm-10-0-187-183:~[root@vm-10-0-187-183 ~]# root@vm-10-0-187-183:~[root@vm-10-0-187-183 ~]# root@vm-10-0-187-183:~[root@vm-10-0-187-183 ~]# shutdown -r
Reboot scheduled for Mon 2024-09-02 14:17:13 EDT, use 'shutdown -c' to cancel.
root@vm-10-0-187-183:~[root@vm-10-0-187-183 ~]# 
exit

exit

exit
```

Expected results:
There is no broadcast message in the second screen, but there is one the first screen (tested with screen-4.9.1-1.fc40.x86_64).

Output from the terminal:
```
[root@vm-10-0-186-235 ~]# shutdown -r
Reboot scheduled for Mon 2024-09-02 14:20:07 EDT, use 'shutdown -c' to cancel.
[root@vm-10-0-186-235 ~]# 
```

Output from the screen log file:
```
# cat screen.log 
root@vm-10-0-186-235:~[root@vm-10-0-186-235 ~]# root@vm-10-0-186-235:~[root@vm-10-0-186-235 ~]# shutdown -r

Broadcast message from root.redhat.com on pts/2 (Mon 2024-09-02 14:19:07 EDT):

The system will reboot at Mon 2024-09-02 14:20:07 EDT!

Reboot scheduled for Mon 2024-09-02 14:20:07 EDT, use 'shutdown -c' to cancel.
root@vm-10-0-186-235:~[root@vm-10-0-186-235 ~]# 
exit

exit
```

Comment 1 Frantisek Sumsal 2024-09-04 14:47:17 UTC
I filed an upstream ticket (https://savannah.gnu.org/bugs/index.php?66171) since the same issue is reproducible with the latest upstream's git as well.

Comment 2 Aoife Moloney 2025-02-26 13:11:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 3 Fedora Release Engineering 2026-05-06 11:53:24 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
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 EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2026-06-08 16:02:00 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.