quit gossiping about me! lol
i'm leaving my cushy, fat-paychecked developer job for another one that doesn't leave me so conflicted with my leftists values and the content of this article is PRECISELY at the core of what i'll be doing most weekdays for the next 3-5 years.
i've unwittingly separated myself from the general linux user experience in my march towards becoming a professional grey beard and seeing old project names that i had forgotten about in the last 15ish years, like anaconda, gives me goosebumps when the memories flood back in.
posts like this make me glad that i decided to build my next daily driver exactly how most people here do it and i wonder if the skills that i've acquired since the last time i did this will help any.
i think that most of them either use something like xrandr or brightnessctl.
i'm not a vegan yet; but i will be eventually once i can figure how to finish the transition and this is great to see.
I use rsync on a cron job and it do it automatically every time i add a new drive or volume.
The same goes for all general use social media platform and singling tiktok out on these grounds can only be intentional.
I did this yesterday while trying to make a backup before formatting and then updating my work rig and I'm SO GLAD that the decades have taught me to take knee-jerk/automatic actions that forces me to make entire volume backups; otherwise this last month of work life would have been AWFUL!!!
I started with Linux in 2002 and about 10 years before I developed my software engineering skillset.
During that time I used to contribute to enlightenment (the desktop environment) because my trekkie obsession led me into making a LCARS interface and there was an online community of trekkies who friendly completed against each other over who can make the better LCARS interface and I got sucked in.
I don't know if that's still a thing about in the FOSS world these days; but I do know that contributors to volunteer projects today follow the same guidelines that the professionals use and I think there's plenty of opportunity there if you can find one of your interests that has any overlap with IT or software development (the later pays SIGNIFICANTLY better).
Also take into account that I'm probably full of shit. Lemmy has been teaching me that I got lucky and my only intention is to share my experience with someone who asked the same question I did to a forum of Linux focused strangers 25ish years ago.
unless you're using a very old or niche distribution, all of your logs are centralized in to a single space and the command journalctl will let you look at them.
in your situation i would use the command journalctl -f to get a live action printout of all the things that are happening as you try to start your x server and you can look through them to find messages in the logs that contain something like "failure" or "error" or "timeout" to find clues as to what's causing your problem.
you don't need the xserver to run linux and most distributions give you 7 virtual terminals that you can log into without the xserver and each one can be accessed using the keyboard combinations alt+crtl+f1 through alt+crtl+f7.
when i used to be in situations like yours i would log into two virtual terminals. i would use one of them to run tail -f $logname and the other to start the xserver. tail -f $logname is the older deprecated version of journalctl -fand they both show you what's happening in your computer as it occurs. you'll likely only need to see it once or twice to get a sense of what's happening and what the interval looks like and you can accomplish something similar if you keep track of your own timestamps by hand and then look through the logs searching for those timestamps in the logs.
share the log messages with errors/failures/timeout/whatever in them and we can both look for clues using google or ai.
how about the logs; any leads there?
i'm headless for servers too; but i'm foolish enough to use the x server as my daily driver. lol
be aware that there are known weak points in all commercial vpns except for mullvad and firefox (so far)