Difference between revisions of "Chromium--no-sandbox-PN8M-090T"
From ICOP tech wiki
| Line 15: | Line 15: | ||
<p>Put a # to "ExecStart=/usr/libexec/upowerd" <pre> | <p>Put a # to "ExecStart=/usr/libexec/upowerd" <pre> | ||
#ExecStart=/usr/libexec/upowerd | #ExecStart=/usr/libexec/upowerd | ||
| − | </pre> | + | </pre>[[File:Upowersetting.jpg|left|alt=|border|frameless]]<br /> |
| − | [[File:Upowersetting.jpg|left| | ||
| − | <br>Press Ctrl+X and input Y to save. | + | <br> Press Ctrl+X and input Y to save. <br /> |
<br /> | <br /> | ||
Revision as of 16:10, 27 March 2024
Resovling Terminal frozen after closing chromium--no--sandbox
Some of the customer may meet a terminal frozen problem after closing chromium--no-sandbox, and in this article, we will provide a temporary solution to avoid this problem.
*Notice, ICOP could help to issue a new image for resolving this problem, this is just for testing.
Boot up the unit and enter Yocto desktop, click upper-left icon to use weston-terminal.
Input the command below to access the upower.service file
$ cd /lib $ nano systemd/system/upower.service
Put a # to "ExecStart=/usr/libexec/upowerd"
#ExecStart=/usr/libexec/upowerd
Press Ctrl+X and input Y to save.
