I suppose this is the bit of log you referred to:
---
xscreensaver-auth: 06:35:36: re-creating window: size changed
The program 'chbg' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 306 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
xscreensaver-gfx: 06:35:36: 1: child pid 244288 (chbg) exited abnormally with status 1
---
Important to know whether this happens repeatedly, or this was a one-off occurrence and "coming back from hibernation, with 2 screens" normally works OK.

Source RPM: (none) => chbg-2.0.1-29.mga9.src.rpm
CC: (none) => lewyssmith

Hi Lewis.
This is not always the case, but it occurred already, this is why I activated logging.

OK, understand that it normally works, but sometimes throws the error.
You did not say whether you can recover the lost second screen, or what you have to do to get it back - if at all.
It might help to have the O/P of:
 $ inxi -G
and any other graphics info you might know of.

Really do not know where to push this; chbg has been unchanged since forever, so is unlikely to be the reason.
"coming back from hibernation" has been a sore point for some time, but I thought the latest kernels sorted it. Can you say which one you have?

After entering the password, all come back to normal work.
What has been recently updated is xsceensaver.
 uname -a
Linux YZenbook.home 6.4.16-desktop-3.mga9 #1 SMP PREEMPT_DYNAMIC Tue Oct 10 16:51:28 UTC 2023 x86_64 GNU/Linux

inxi -G
Graphics:
  Device-1: Intel HD Graphics 620 driver: i915 v: kernel
  Device-2: Realtek USB2.0 HD UVC WebCam type: USB driver: uvcvideo
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: modesetting,v4l dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 23.1.7 renderer: Mesa Intel HD Graphics 620 (KBL
    GT2)

(In reply to papoteur from comment #4)
> After entering the password, all come back to normal work.
So that is easy enough! Good.

> What has been recently updated is xsceensaver.
 xscreensaver-6.06-3.mga9.src.rpm
 xscreensaver-6.06-3.mga9.tainted.src.rpm
 ---
 xscreensaver-6.08-1.mga9.src.rpm
 xscreensaver-6.08-1.mga9.tainted.src.rpm
The update on my box was 19 October. Are you able to relate the problem to around then, or has it existed since you started with Mageia 9?
Which version are you using: normal or tainted? Try the other?
You could try downgrading it to see whether that changes anything.

> Linux YZenbook.home 6.4.16-desktop-3.mga9
That is the latest issued version, so hopefully includes hibernation/suspend/resume corrections. Rule that out.

I was surprised that 'inxi -G' did not mention two screens; perhaps it wanted -Gxx (or may never show that).

I have the tainted xscreensaver.
I didn't pay attention to which screen was connected when running inxi. Thus, with the 2 screens:
inxi -G
Graphics:
  Device-1: Intel HD Graphics 620 driver: i915 v: kernel
  Device-2: Realtek USB2.0 HD UVC WebCam type: USB driver: uvcvideo
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: modesetting,v4l dri: iris gpu: i915 resolution: 1: 1920x1080~60Hz
    2: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 23.1.7 renderer: Mesa Intel HD Graphics 620 (KBL
    GT2)
I will try the core release.
I think I have upgraded the system at the same time that I get the update. Thus I can't distinct the events.

So the problem came with Mageia 9.
Since chbg has not been updated since it was introduced many years ago, you will understand why we cannot readily push this bug that way.

Can you play with xscreensaver? All 4 version shown in comment 6.

TIA

Running the non-tainted release for now. Wait and see.

Got this morning the same problem
chbg crashed with status 1

Here the sequence from the log during the return from hibernation.
This is with xscreensver 6.08 from core repository.
==========
xscreensaver-systemd: 06:47:39: exec: xscreensaver-command --verbose -deactivate
xscreensaver-gfx: 06:47:42: set DPMS timeouts: 600 660 1200
xscreensaver-gfx: 06:47:42: 0: killing pid 1761900 (chbg)
xscreensaver-gfx: 06:47:42: 0: forked "chbg -xscreensaver -mode smart -bg "#000000"				      				  -interval 0.16 -effect 1 -speed 500	      				  -R `/bin/ls				      				  /usr/share/mga/screensaver/*`" in pid 1762156 on window 0x4700008
xscreensaver-gfx: 06:47:42: 0: next cycle in 600 sec at 06:57:42
xscreensaver-gfx: 06:47:42: 0: child pid 1761900 (chbg) exited normally with SIGTERM
xscreensaver-gfx: 06:47:43: 0: screen change event: new layout:
xscreensaver-gfx: 06:47:43:    RANDR screens: 4, Xinerama: 1; believing RANDR
xscreensaver-gfx: 06:47:43:    screens in use: 1
xscreensaver-gfx: 06:47:43:       0/0: 1920x1080+0+0 (eDP-1)
xscreensaver-gfx: 06:47:43:    rejected screens: 3
xscreensaver-gfx: 06:47:43:       1/0: 1920x1080+0+0 (DP-1) -- output disabled
xscreensaver-gfx: 06:47:43:       2/0: 1920x1080+0+0 (HDMI-1) -- output disabled
xscreensaver-gfx: 06:47:43:       3/0: 1920x1080+0+0 (HDMI-2) -- duplicate of 0
xscreensaver: 06:47:43: ClientMessage DEACTIVATE: deactivating (from pid 1468353)
xscreensaver: 06:47:43: checking init file
xscreensaver: 06:47:43: authorizing
xscreensaver: 06:47:43: grabbing mouse on 0x7bf... GrabSuccess
xscreensaver-command: deactivating

xscreensaver: 06:47:43: pid 1762166: launched xscreensaver-auth --verbose
xscreensaver-auth: 06:47:43: pwnam: couldn't get password of "yves"
xscreensaver-auth: 06:47:43: pwnam: couldn't get password of "root"
xscreensaver-auth: 06:47:43: initial effective uid/gid was root/yves (0/1000)
xscreensaver-auth: 06:47:43: changed uid/gid to yves/yves (1000/1000)
xscreensaver-auth: 06:47:43: running as user "yves"
xscreensaver-auth: 06:47:43: PAM: pam_start ("xscreensaver", "yves", ...) ==> 0 (Succès)
xscreensaver-auth: 06:47:43:   pam_set_item (p, PAM_TTY, ":0") ==> 0 (Succès)
xscreensaver-auth: 06:47:43:   pam_authenticate (...) ...
xscreensaver-auth: 06:47:43:     pam_conversation (ECHO_OFF="Mot de passe : ") ...
xscreensaver-auth: 06:47:46: mouse is at 1073,518 on monitor 0 1920x1080+0+0 "eDP-1"
xscreensaver-auth: 06:47:46: theme: default
xscreensaver-gfx: 06:47:46: 0: screen change event: new layout:
xscreensaver-gfx: 06:47:46:    RANDR screens: 4, Xinerama: 2; believing RANDR
xscreensaver-gfx: 06:47:46:    screens in use: 2
xscreensaver-gfx: 06:47:46:       0/0: 1920x1080+0+0 (eDP-1)
xscreensaver-gfx: 06:47:46:       3/0: 1920x1080+1920+0 (HDMI-2)
xscreensaver-gfx: 06:47:46:    rejected screens: 2
xscreensaver-gfx: 06:47:46:       1/0: 1920x1080+0+0 (DP-1) -- output disabled
xscreensaver-gfx: 06:47:46:       2/0: 1920x1080+0+0 (HDMI-1) -- output disabled
The program 'chbg' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 381 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
xscreensaver-gfx: 06:47:46: 1: newly added window 0x4700009 1920x1080+1920+0
xscreensaver-gfx: 06:47:46: 0: forked "xscreensaver-gl-visual" in pid 1762201
xscreensaver-auth: 06:47:46: kbd layout: French
xscreensaver-auth: 06:47:46: re-creating window: size changed
xscreensaver-gfx: 06:47:47: 0: xscreensaver-gl-visual: GL visual is 0x21 (default)
xscreensaver-gfx: 06:47:47: 1: forked "chbg -xscreensaver -mode smart -bg "#000000"				      				  -interval 0.16 -effect 1 -speed 500	      				  -R `/bin/ls				      				  /usr/share/mga/screensaver/*`" in pid 1762214 on window 0x470000d
xscreensaver-gfx: 06:47:47: 1: offsetting cycle time by 295 sec
xscreensaver-gfx: 06:47:47: 1: next cycle in 895 sec at 07:02:42
xscreensaver-gfx: 06:47:47: 0: child pid 1762156 (chbg) exited abnormally with status 1
xscreensaver-gfx: 06:47:47: 0: cycling in 60 sec
xscreensaver-auth: 06:47:47: re-creating window: occluded
xscreensaver-gfx: 06:47:47: 0: screen change event: layout unchanged
The program 'chbg' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 383 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
xscreensaver-gfx: 06:47:47: 1: child pid 1762214 (chbg) exited abnormally with status 1
xscreensaver-gfx: 06:47:47: 1: cycling in 60 sec
xscreensaver-auth: 06:47:47: re-creating window: occluded
xscreensaver-auth: 06:48:02: XI RawKeyPress  
xscreensaver-auth: 06:48:02: XI RawKeyPress  
xscreensaver-auth: 06:48:02: XI RawKeyRelease
xscreensaver-auth: 06:48:02: XI RawKeyPress  
xscreensaver-auth: 06:48:02: XI RawKeyRelease
xscreensaver-auth: 06:48:02: XI RawKeyRelease
xscreensaver-auth: 06:48:02: XI RawKeyPress  
xscreensaver-auth: 06:48:02: XKB event 2
xscreensaver-auth: 06:48:02: kbd layout: French
xscreensaver-auth: 06:48:03: XI RawKeyPress  
xscreensaver-auth: 06:48:03: XI RawKeyRelease
xscreensaver-auth: 06:48:03: XKB event 2
xscreensaver-auth: 06:48:03: kbd layout: French
xscreensaver-auth: 06:48:03: XI RawKeyRelease
xscreensaver-auth: 06:48:03: XI RawKeyPress  
xscreensaver-auth: 06:48:03: XI RawKeyRelease
xscreensaver-auth: 06:48:03: XI RawKeyPress  
xscreensaver-auth: 06:48:03: XI RawKeyRelease
xscreensaver-auth: 06:48:04: XI RawKeyPress  
xscreensaver-auth: 06:48:04: XI RawKeyPress  
xscreensaver-auth: 06:48:04: XI RawKeyRelease
xscreensaver-auth: 06:48:04: XI RawKeyRelease
xscreensaver-auth: 06:48:05: XI RawKeyPress  
xscreensaver-auth: 06:48:05: authentication input finished
xscreensaver-auth: 06:48:05:     pam_conversation (...) ==> PAM_SUCCESS
xscreensaver-auth: 06:48:06:   pam_authenticate (...) ==> 0 (Succès)
xscreensaver-auth: 06:48:06:   pam_acct_mgmt (...) ==> 7 (Échec de l’authentification)
xscreensaver-auth: 06:48:06:   pam_setcred (...) ==> 0 (Succès)
xscreensaver-auth: 06:48:06: pam_end (...) ==> 0 (Success)
xscreensaver-auth: 06:48:06: deleted auth failure property
xscreensaver-auth: 06:48:06: authentication succeeded
xscreensaver: 06:48:06: pid 1762166: xscreensaver-auth exited and authenticated
xscreensaver: 06:48:06: unlocking
xscreensaver: 06:48:06: unblanking
xscreensaver: 06:48:06: pid 1761882: killing xscreensaver-gfx
xscreensaver: 06:48:06: ungrabbing mouse
xscreensaver: 06:48:06: ungrabbing keyboard
xscreensaver-gfx: 06:48:06: SIGTERM: unblanking
xscreensaver-gfx: 06:48:06: SIGTERM: exiting
xscreensaver: 06:48:06: pid 1761882: xscreensaver-gfx exited with SIGTERM
xscreensaver: 06:48:43: checking init file
xscreensaver: 06:48:45: XI _RawButtonPress   1719, 751 
==============

I have asked in hope the contact for chbg for his opinion.
 http://beebgames.com/contact.php