You are not logged in.
^I meant dealing with dpi was annoying, and the article expanded a bit on that. Not that the article itself was annoying.
It seems X is perfectly aware of both display dimensions and pixels, but chooses not to interpret them.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )
Offline
johnraff wrote:A while ago some of us got into a discussion of dpi as a distracting sidebar to someone's screen display size issues:
https://forums.bunsenlabs.org/viewtopic.php?id=7315There's a link to a very old bug report in there somewhere, very confusing. Essentially it sounds like DE developers decided to ignore Xorg's DPI settings at some point, and therefore Xorg decided to ignore autodetection...?!
johnraff wrote:It is annoying, and this article expands a bit:
https://linuxreviews.org/HOWTO_set_DPI_in_XorgI don't rightly see anything annoying in there (apart from obvious rant about GNOME f*ckery).
But it makes me wonder what will happen if I remove my manual settings again and just see what Xorg autodetects...
What happened is that the Xorg devs decided to be 'bug compatible' with Windows and set the DPI at 96 no matter what the display said.
Microsoft removed the bug with the release of Windows 7.
Xorg still over a decade later declares it NOTABUG and WONTFIX.
Offline
^ that sucks for sure.
Anyhow, it's possible to set correct DPI (or manipulate it generally) with the help of the mentioned article.
Offline
Here is a nice little article from itsfoss explaining the difference between the
apt
and
apt-get
commands used when installing and updating packages.
Difference between apt & apt-get
Thought it might be something interesting to read for a newer Linux user to know what the actual difference is
EDIT : This one might be good too
SSH Academy - Command
Last edited by NightOwl (2021-09-19 20:12:18)
Offline
Help with reading smartctl info
The mysterious list of numbers that comes from 'sudo smartctl -a /dev/sda' or whatever...
Some incomplete, but still helpful, advice here:
https://wiki.unraid.net/Understanding_SMART_Reports
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )
Offline
Help with reading smartctl info
The mysterious list of numbers that comes from 'sudo smartctl -a /dev/sda' or whatever...
Some incomplete, but still helpful, advice here:
https://wiki.unraid.net/Understanding_SMART_Reports
Another thing that can help is adding a GUI frontend.. very simple to do:
sudo apt-get install gsmartcontrol
You then get explanations when you hover the mouse over things. Also a progress bar on the long & short self-tests.
Plus it automatically highlights suspect, marginal, or failed attributes.
Last edited by Bearded_Blunder (2022-04-18 13:59:52)
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
^ +1 for this. Has helped me understand way more than smartctl itself!
Offline
^^That looks nice.
Took a couple of minutes to discover you need to run it as 'gsmartcontrol-root'.
I guess the plain 'gsmartcontrol' is for people for whom the above doesn't work, and have to use su from a terminal?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )
Offline
It appears to be policykit enabled (org.gsmartcontrol).
If you run it from the applications menu under system it pops up a polikit-agent elevation dialogue just like synaptic, gparted, etc.
From a terminal I just do:
pkexec gsmartcontrol
gsmartcontrol-root which the .desktop appears to execute, now you prodded me to look, appears to be a shell script which looks for pkexec first & then falls back to other methods to elevate when pkexec isn't available.
Plain gsmartcontrol is what eventually gets executed as an argument to pkexec, su-to-root, gnomesu, gksu, kdesu, beesu, xdg-su, or sux whichever of that list is found first.
If gsmartcontrol-root fails it errors via xmessage advising to install Polkit, kdesu, gnomesu, gksu, beesu or sux first.
Had I been the developer & assuming no long history, I'd have named the two files the opposite way round so people executed the elevation script instinctively.
The Windows version, which I became aware of first but noted was cross-platform, obviously pops up a UAC prompt.
Last edited by Bearded_Blunder (2022-04-19 14:01:05)
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline