No. Thinking about the panda is involuntary in that scenario. Typing up and submitting an explicitly unwanted response is not involuntary. It’s a thing a person chooses to do expressly against the wishes of the person making the request.
No. Thinking about the panda is involuntary in that scenario. Typing up and submitting an explicitly unwanted response is not involuntary. It’s a thing a person chooses to do expressly against the wishes of the person making the request.
Wrap it in the wire, then spin one of them. That part’s important! Won’t do anything if you don’t spin it.
No it wouldn’t. The paper is talking about structures on the kilometer scale. In particular, the abstract talks about a 3 km radius habitat simulating 0.3 g of gravity. This would require spinning at only 0.3 RPM. Even if they wanted Earth gravity, it would only require 0.55 RPM. Neither of those are anywhere close to strobe light territory.
EDIT: The above was referring to the University of Rochester’s paper, not to Dr. Jensen’s paper. I didn’t realize they were two different papers. Dr. Jensen’s proposal is for a slightly smaller 2.5 km radius station. This doesn’t change my point any though. Assuming a worst case of Earth gravity would still only require spinning the station at 0.6 RPM. (You can actually go quite a bit smaller than either of those proposals without turning the thing into a rave. A 224 meter radius would still only need to spin at 2 RPM to generate Earth gravity, for example.)
Look in /var/log/Xorg.0.log for Xorg errors.
Check if OpenGL is okay by running
glxinfo
(from the packagemesa-utils
) and checking in the first few lines for “direct rendering: Yes”.Check if Vulkan is okay by running
vulkaninfo
(from the packagevulkan-tools
) and seeing… if it throws errors at you, I guess. There are probably some specific things you could look for but I’m not familiar enough with Vulkan yet.You could
sudo dmesg
and read through looking for problems, but there might be a lot of noise to sift through. I’d start by piping it throughgrep -i nvidia
to look for driver-specific stuff.Might be worth running
nvidia-settings
and poking around to see if anything seems amiss. Not sure what you’d actually be looking for, but yeah.Sometimes switching from
linux
andnvidia
tolinux-lts
andnvidia-lts
can help if the problem is in the kernel or driver. Remember to switch both of these at the same time, since drivers need to match the kernel.You could also try switching from the nvidia drivers to nouveau. Might offer temporary relief and help narrow down where the problem is, at the expense of probably worse performance in heavy games. Ought to be fine for 2D gaming and general desktopping.
Trying a different window manager is always an option. Don’t know how much hassle that is when you use a full DE; I’ve always been the “just grab individual lightweight pieces and slap 'em together” sort so I don’t have any real experience with KDE. But yeah. Find out what the right way to change WM is for your system, then try swapping over to Openbox or something minimal like that and see what happens.
Related to WM/DE, it could be an issue with the compositor maybe. Look up whatever KDE’s compositor is and see if you can turn it off and run a different one?