how to quit linux container really safely and correctly

[Mgr. Janusz Chmiel]

I do not see at all. So I AM using The Orca screen reader application to be able to use X11 applications.

But I have found out, that Orca screen reader can not be auto terminated correctly.

If I simply type

Orca &

And If I type exit to terminate Bash shell on terminal.

Terminal window is still being operable with Chromium OS screen readeru.

And If I terminate The Linux container by using context menu item, Orca screen reader depend Python modules start to be corrupted when I restart The container again.

 

Please, how to ensure, that all Linux crucial processes will be really turned of correctly?

Do I have to use some commands such as halt, or some Init commands?

 

Because Google engineers have preconfigured The Debian old stable container for Wayland and because some special window manager is being also used, I can not simply use Mate, Lxde or other GTK based desktops.

Sure, it is no problem, because I do not want to replace The Chromium OS user interface by Those desktop environments.

But how to correctly terminate The Linux container?

I must run orca screen reader from The

/etc/profile

Script.

So I have added The orca &

Command as a last line of this script.

Speech-dispatcher and espeak-ng speech engine work like a charm, because elite Google engineers have even allowed Linux users to use sound output and it is even possible to rrecord. SO even Audacity sound editor work smoothly.

Thank you for your advice.

 

[dragon788]

You could try using `orca -q` to try and tell the running process to stop, otherwise `pkill orca` or `killall orca` before you quit and shutdown the Linux apps container will ensure it is no longer running.

Using `orca &` tells it to go into the background (but keep running) and gives you back your shell. You could use `bg` to list background jobs, and `fg` or `fg number` to bring it back to the foreground and then Ctrl+C aka ^C to kill it.

You can also set some variables to help with Orca inside the Linux apps container, for Qt apps adding QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 to your `~/.profile` may help.

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss
---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.