Comment # 4 on bug 1209224 from Joe S

Hi Daike,

>> Would you mind check the status of xrdp process after the issue occured?

Sure no problem, thanks for looking into this.

I am still running TW 20230222 which has version 5.27.0 but plan to update TW
in the next few days.

After machine boots and xrdp starts here is the status

systemctl status xrdp

��������� xrdp.service - xrdp daemon
     Loaded: loaded (/usr/lib/systemd/system/xrdp.service; enabled; preset:
disabled)
     Active: active (running) since Tue 2023-03-21 09:57:00 EDT; 3min 7s ago
       Docs: man:xrdp(8)
             man:xrdp.ini(5)
   Main PID: 980 (xrdp)
      Tasks: 3 (limit: 4593)
        CPU: 1.453s
     CGroup: /system.slice/xrdp.service
             ������������������ 980 /usr/sbin/xrdp --nodaemon
             ������������������2480 /usr/sbin/xrdp --nodaemon

Then I rdp'd, re-enabled the Energy Saving and set it to 1 minute.

After that expired, the problem occurs as initially described.

Here is the status of the rdp service after the problem has occurred

systemctl status xrdp

��������� xrdp.service - xrdp daemon
     Loaded: loaded (/usr/lib/systemd/system/xrdp.service; enabled; preset:
disabled)
     Active: active (running) since Tue 2023-03-21 09:57:00 EDT; 5min ago
       Docs: man:xrdp(8)
             man:xrdp.ini(5)
   Main PID: 980 (xrdp)
      Tasks: 3 (limit: 4593)
        CPU: 1.480s
     CGroup: /system.slice/xrdp.service
             ������������������ 980 /usr/sbin/xrdp --nodaemon
             ������������������2480 /usr/sbin/xrdp --nodaemon

So no issues indicated.

As a further test, I tried to rdp to the same machine but using a different
login user and that 2nd user can login and everything is working fine.

That seems to confirm that xrdp is fine and that the issue is with DPMS change
you mentioned.

I also did the following test which I think will be helpful

1) restart xrdp
2) rdp as user that has timeout set to 1 minute
3) ssh to machine as user and run journalctl -xef and wait for 1 minute for the
issue to occur

The user had the following journal entries right when the problem occurs:

Mar 21 11:23:55 test kded5[11650]: QDBusAbstractAdaptor: Cannot relay signal
KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Mar 21 11:23:59 test org_kde_powerdevil[11741]: org.kde.kscreen.dpms: Failed to
query DPMS state, cannot trigger
Mar 21 11:23:59 test org_kde_powerdevil[11741]: XIO:  fatal IO error 0
(Success) on X server ":200.0"
Mar 21 11:23:59 test org_kde_powerdevil[11741]:       after 318 requests (317
known processed) with 0 events remaining.
Mar 21 11:23:59 test org_kde_powerdevil[11741]: The X11 connection broke:
Unsupported extension used (code 2)

After that occurs the user instance of /usr/libexec/org_kde_powerdevil is no
longer running and the session is unusable.

Hope that helps!

Please let me kow if you need any other information.