[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[screen-devel] [bug #66171] screen 5.0.0 doesn't show/log broadcast mess
From: |
Frantisek Sumsal |
Subject: |
[screen-devel] [bug #66171] screen 5.0.0 doesn't show/log broadcast messages |
Date: |
Wed, 4 Sep 2024 10:45:34 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?66171>
Summary: screen 5.0.0 doesn't show/log broadcast messages
Group: GNU Screen
Submitter: mrc0mmand
Submitted: Wed 04 Sep 2024 02:45:30 PM UTC
Category: User Interface
Severity: 3 - Normal
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Release: 5.0.0
Fixed Release: None
Planned Release: None
Work Required: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Wed 04 Sep 2024 02:45:30 PM UTC By: Frantisek Sumsal <mrc0mmand>
I originally reported this to Fedora's Bugzilla, but the same issue happens
with the latest git master as well. I'll copy the original BZ contents below,
since the same stuff applies to the upstream version as well.
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
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66171>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [screen-devel] [bug #66171] screen 5.0.0 doesn't show/log broadcast messages,
Frantisek Sumsal <=