Forums
-
The Highlands
-
- 1,756
- posts
-
- 204,423
- posts
-
- 42,528
- posts
-
- 3,521
- posts
-
- 19,257
- posts
-
- 2,036
- posts
-
- 23,437
- posts
-
- 17,564
- posts
-
- 49,639
- posts
-
- 6,439
- posts
-
-
Recent Posts
-
By Cluttermagnet · Posted
No problems, mate! All the help is appreciated. I'm still mulling over one additional oddity I have encountered. When I went to try and make a launcher, I encountered an icon for opera already 'in there' and checked with a + as well. It still does not, however, show up in my actual Menu, only in the Edit Menu environment. That's a little confusing and unexpected... As an experiment, there was one unchecked software in there so I checked it. It immediately started showing up in my menu (Iced Tea Java Web Start). So I know the idea of checking/unchecking is basically working, But NOT for Opera, for some reason. Weird... Clutter -
Especially for "Known Issues" but also for other information about Version 1903, see Windows 10, version 1909 and Windows Server, version 1909 - Windows Release Information | Microsoft Docs. -
- ------------------------------------------------------------------------- Debian Security Advisory DSA-4564-1 security@debian.org https://www.debian.org/security/ Ben Hutchings November 12, 2019 https://www.debian.org/security/faq - ------------------------------------------------------------------------- Package : linux CVE ID : CVE-2018-12207 CVE-2019-0154 CVE-2019-0155 CVE-2019-11135 Several vulnerabilities have been discovered in the Linux kernel that may lead to a privilege escalation, denial of service, or information leak. CVE-2018-12207 It was discovered that on Intel CPUs supporting hardware virtualisation with Extended Page Tables (EPT), a guest VM may manipulate the memory management hardware to cause a Machine Check Error (MCE) and denial of service (hang or crash). The guest triggers this error by changing page tables without a TLB flush, so that both 4 KB and 2 MB entries for the same virtual address are loaded into the instruction TLB (iTLB). This update implements a mitigation in KVM that prevents guest VMs from loading 2 MB entries into the iTLB. This will reduce performance of guest VMs. Further information on the mitigation can be found at <https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/multihit.html> or in the linux-doc-4.9 or linux-doc-4.19 package. A qemu update adding support for the PSCHANGE_MC_NO feature, which allows to disable iTLB Multihit mitigations in nested hypervisors will be provided via DSA 4566-1. Intel's explanation of the issue can be found at <https://software.intel.com/security-software-guidance/insights/deep-dive-machine-check-error-avoidance-page-size-change-0>. CVE-2019-0154 Intel discovered that on their 8th and 9th generation GPUs, reading certain registers while the GPU is in a low-power state can cause a system hang. A local user permitted to use the GPU can use this for denial of service. This update mitigates the issue through changes to the i915 driver. The affected chips (gen8 and gen9) are listed at <https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Gen8>. CVE-2019-0155 Intel discovered that their 9th generation and newer GPUs are missing a security check in the Blitter Command Streamer (BCS). A local user permitted to use the GPU could use this to access any memory that the GPU has access to, which could result in a denial of service (memory corruption or crash), a leak of sensitive information, or privilege escalation. This update mitigates the issue by adding the security check to the i915 driver. The affected chips (gen9 onward) are listed at <https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Gen9>. CVE-2019-11135 It was discovered that on Intel CPUs supporting transactional memory (TSX), a transaction that is going to be aborted may continue to execute speculatively, reading sensitive data from internal buffers and leaking it through dependent operations. Intel calls this "TSX Asynchronous Abort" (TAA). For CPUs affected by the previously published Microarchitectural Data Sampling (MDS) issues (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091), the existing mitigation also mitigates this issue. For processors that are vulnerable to TAA but not MDS, this update disables TSX by default. This mitigation requires updated CPU microcode. An updated intel-microcode package (only available in Debian non-free) will be provided via DSA 4565-1. The updated CPU microcode may also be available as part of a system firmware ("BIOS") update. Further information on the mitigation can be found at <https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html> or in the linux-doc-4.9 or linux-doc-4.19 package. Intel's explanation of the issue can be found at <https://software.intel.com/security-software-guidance/insights/deep-dive-intel-transactional-synchronization-extensions-intel-tsx-asynchronous-abort>. For the oldstable distribution (stretch), these problems have been fixed in version 4.9.189-3+deb9u2. For the stable distribution (buster), these problems have been fixed in version 4.19.67-2+deb10u2. -
+1 it could be VBox. One thing I found with VBox when I used it was it worked best when the installed version of Guest Additions matched the exact version of VBox it was running in. Weird things happen with a mismatch. I don't have a current LXQT install, but 2 systems with siduction/KDE don't have this problem. In fact I was thinking recently how these are currently the best-behaved versions of any OS I've ever had! Touch wood.
-
To summarise my last post which seems to have been misunderstood, if you can launch it from terminal with just "opera" you should be able to put just "opera" in your menu entry. /usr/bin/opera will work anyway so job done!
-
-
Who's Online (See full list)
-
Today's Birthdays
-
-
Member Statistics
