By default, Chrome OS is great at picking out the best apps for a specific purpose, but sometimes that's not what you want. While you can easily choose the applications you need, you can also change the default options quite easily. The following article will show you how to change the default apps on Chromebooks.
With Android, you can put the default apps in a central location, but for Chrome OS, you have to open a file to change the default for that file type. For example, you are preparing to use an image file, but it will work the same no matter what you are trying to open.
Open the file manager and navigate to the file you want, then click once on the file. To the right of the navigation bar, you'll see the Open option with a down arrow on the side. You click on that arrow.
A list of applications will appear, find and select Change Default.
In the next list, click the option that you always want to open this file with Open with ...
Please note that some applications cannot be set as default, so you will have to run them manually.
If the application you want to use as default cannot be set to default or just wants to use another application for specific tasks, you can also open the file in a specific application on a per-boot basis. run.
Navigate to the file you want to open, then click on it. Click Open on the right side of the navigation bar, then select the app you want to open that file.
Alternatively, you can right-click the file, then select More Actions, which will open a list of applications compatible with that particular file type.
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
