Difference between revisions of "Chromium--no-sandbox-PN8M-090T"
From ICOP tech wiki
| Line 14: | Line 14: | ||
$ nano systemd/system/upower.service | $ nano systemd/system/upower.service | ||
</pre>[[File:Nanoupower.jpg|frameless]] | </pre>[[File:Nanoupower.jpg|frameless]] | ||
| − | <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><br /> | </pre><br /> | ||
| Line 30: | Line 30: | ||
| − | <p>Press Ctrl+X and input Y to save.</ | + | <p>Press Ctrl+X and input Y to save.<p /> |
<br /> | <br /> | ||
Revision as of 16:03, 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.
