Issue with QFont Error and DisplayCenter Layout Corruption when Using TextView Widget in APROL

Ask Questions Other Topics
,
1

1. QFont Error upon TextView Widget Activation

  • As soon as the TextView Widget is activated, a QFont-related error occurs.

  • The error message is identical to the one shown in the attached file “APC_Abnormal.png”.

2. DisplayCenter Layout Corruption on Exit

  • If DisplayCenter is closed while the QFont error has occurred,
    the layout files under the following path become corrupted:

    /home/operator/RUNTIME/cnf/DisplayCenter/user/

  • As a result, UI elements such as the toolbar disappear when DisplayCenter is restarted.

3. Temporary Workaround Identified

We found that executing the following command before closing DisplayCenter prevents the issue:

Shell

chmod 444 /home/operator/RUNTIME/cnf/DisplayCenter/user/*layout_run.rc

Show more lines

  • With this workaround applied, after restarting DisplayCenter, the toolbar remains intact and the layout is not lost.

4. Our Observation / Assumption

Based on the above behavior, we suspect that:

  • There may be a conflict related to QFont handling when the TextView Widget is activated, and

  • During DisplayCenter shutdown, the layout files are rewritten even in an abnormal state, resulting in corrupted layout data.

5. Request for Clarification

Could you please advise on the following points?

  1. Is this a known issue related to the TextView Widget and QFont handling?

  2. Are there any recommended settings, patches, or official solutions for this behavior?

  3. Is using chmod 444 on *layout_run.rc files an acceptable or supported workaround, or could it have side effects?

  4. Is there an alternative recommended method to maintain login persistence for Alarm History without using the TextView Widget?

We would appreciate your guidance on how to resolve this issue properly.

Thank you for your support.

2

Hi @NamKiPark, since you have not received any answer from Community so far, please get in touch with local APROL support team. Discussion closed as a unsolved, but feel free to update us with any new findings. Thanks