SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just updated four machines with the latest -current updates, including the 6.9.0 kernel. Three work fine, but one now has broken graphics. X refuses to start. SDDM gets stuck in a crash loop. Both startx and startkwayland produce an instant server crash. startxfce4 works fine!
The computer is a locally re-badged Clevo N141ZU. lspci reports the graphics card to be Intel WhiskeyLake-U GT2 [UHD Graphics 620]
upon updating last current updates with kernel 6.9.0 Xorg is in some sort of crashing loop. this happens on multiple machines... as reported by the OP 6.6.30 works fine. this is my Xorg.0.log from my desktop running current
I also had the issue with Slackware64-current after the 6.9 kernel upgrade. I pressed e when grub was loading and added mitigations=off as mentioned in https://www.linuxquestions.org/quest...ml#post6501920 and was able to use my machine again. I hope this helps someone else
Theoretically a malicious process can find out what's in the memory of another process on the same processor, but IMO you shouldn't be running executables you don't trust anyway.
I can remember that Firefox was patched to reduce the granularity of its timers so this sort of things couldn't be exploited through javascript from remote websites, so that shouldn't be a concern any more.
I believe it's still a concern for shared hosting companies who use VMs or containerisation for isolation between different customers on the same hardware. Probably not a big deal for your average desktop user or on dedicated servers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.