Project

General

Profile

Bug #12843

Another green error from screensaver

Added by Gary Mills 6 months ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
OI-Userland
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:

Description

I noticed this error after an OS upgrade from hipster-20200504 (the USB image) to hipster-20200607 (current a few days ago). This error message appears in green at the top of the screensaver screen:

xscreensaver. ... WARNING: pid ... (.../pyro) sent SIGERM but did not die?

It appears long after the password box has disappeared, but before the screen has blanked. It did eventually blank. I had selected pyro as the application to run while screensaver was active. I believe it comes from this package:

desktop/xscreensaver/hacks@2020.0.1.0
#1

Updated by Gary Mills 6 months ago

I have additional information. Here are the last lines of truss output for the pyro process:

pollsys(0xFFFFFC7FFFDFF058, 1, 0x00000000, 0x00000000) = 1
writev(3, 0xFFFFFC7FFFDFF1A0, 3)                = 5956
pollsys(0xFFFFFC7FFFDFF098, 1, 0x00000000, 0x00000000) = 1
recvmsg(3, 0xFFFFFC7FFFDFEFC0, 32768)           = 32
pollsys(0xFFFFFC7FFFDFF180, 0, 0xFFFFFC7FFFDFF270, 0x00000000) = 0
recvmsg(3, 0xFFFFFC7FFFDFF0C0, 32768)           Err#11 EAGAIN
recvmsg(3, 0xFFFFFC7FFFDFF0A0, 32768)           Err#11 EAGAIN
recvmsg(3, 0xFFFFFC7FFFDFF0C0, 32768)           Err#11 EAGAIN
recvmsg(3, 0xFFFFFC7FFFDFF0A0, 32768)           Err#11 EAGAIN
pollsys(0xFFFFFC7FFFDF6FE0, 1, 0xFFFFFC7FFFDF70F0, 0x00000000) = 0
recvmsg(3, 0xFFFFFC7FFFDFF120, 32768)           Err#11 EAGAIN
recvmsg(3, 0xFFFFFC7FFFDFF100, 32768)           Err#11 EAGAIN
pollsys(0xFFFFFC7FFFDFF058, 1, 0x00000000, 0x00000000) = 1
writev(3, 0xFFFFFC7FFFDFF1A0, 3)                = 5796
    Received signal #15, SIGTERM, in pollsys() [default]
      siginfo: SIGTERM pid=2021 uid=107
pollsys(0xFFFFFC7FFFDFF098, 1, 0x00000000, 0x00000000) Err#4 EINTR

After that process terminated, a new one started up with the same path name and options. It must have been started by xscreensaver . That will be the error. The green error message did not appear at that time, although it did appear 600 seconds later. By this time, the new process was running. The pid shown belongs to xscreensaver. The uid belongs to xscreensaver too.

As far as I can tell, the pyro process handled the signal correctly. The error must be within xscreensaver. This used to work, with no errors. The settings are all left at the defaults.

Also available in: Atom PDF