Last time I was hired as a code monkey we used Linux with a dual-monitor setup. The setting would not, under any circumstances, see one of those 1080p monitors as anything more than 480p.
I spent literally half the first day of work looking for solutions, and eventually settled on running some random command i don’t understand copied from the internet running on startup.
If it helps, Mint seems to have this sorted. I was using a 1080 screen and a 2k screen. Now I’ve got two 2k screens (1440 x something?). Mint detected both configurations correctly and set them up for me. The only thing I had to do was tell it which monitor was the primary, and that was only because I prefer my primary screen to be on the right.
I had the 1080 screen set up in portrait mode for a while too, and Mint had no problem with it 👍
That’s really interesting - and I see others are saying the same thing. I have never had this issue, and I’ve been using dual-monitor setups on Linux for years. I’ve never had an issue getting any monitor working correctly with Linux (and I’ve been using Linux practically full time at home since the late 90s). I wonder what’s going on for your issue.
i cannot stand git. nobody is physically capable of explaining how it works and how to actually use day to day. the vocab seems intentionally chosen to be confusing – ‘push’ and ‘pull’ are too similar and vague [edit my uni taught the tree concept first, and explained in such a way that i could never remember if the server would push an update down to me or i would push an update up]
I mean sure, when I first used git it was a bit confusing as I have never used a similar platform but after visiting a few times you can easily get the hang of it. But that post was super exaggerated claiming “no one” can understand it as if its rocket science, so can’t tell if its a troll or just a clueless dude who gave up after trying once.
My comment is actually an unrelated in-joke forcibly coerced into the shape of a discussion about git. It’s a whole fictional magical universe thing with a lore wiki and stuff:
bro what? literally most devs use it day to day and plenty of people know how it works. push and pull are literally opposites, and used to push and pull from a remote, how is it too similar and vague?
To be fair, I have seen many people confused by git (in fact, there is a relevant xkcd). So for you and anyone else that could use some help:
Git is just a version tracker. It is basically like naming a files “project_1”, “project_2”, “project_final”, etc. It just does the hard work of remembering history for you, and only shows you the current version.
The commands are somewhat oddly named, but are fairly intuitive:
git add - adds some of the current changes to the tracker (“stages” them).
git commit - commits (i.e. saves) the currently staged changes to a new point in your history (a ‘commit’)
git checkout - check out, as in take a look at, another branch
And you shouldn’t think about pushing and pulling as a tree; think about it as an action you take. You either pull changes in from the server or you push them up to the server.
For more complex situations, you will need to use more complex functionality. Git is built to help manage changes when working on a team, so it has the concept of creating new branches of history - like an alternate timeline - so that each individual can work on their code as if they were working alone. When they are ready to send their changes to the main (or master) version, they can merge the changes in. In the event that you want to change history, there is git amend and git rebase.
The normal work flow goes like this:
git checkout -b new-feature: check out a new brach, based on the one you are on now
make some changes
git add file.txt (or -A for all): add your changes to tracking
git commit: save the changes to a new commit (a new point in history). This will try to open an editor so you can write a short message explaining the changes; you can use -m “message” to specify a message from the command line if you prefer.
repeat until you are done working
git push: send your changes to the remote server (add –set-upstream origin new-feature if this is the first time for this branch)
open a pull request or something similar so someone else on the team can review and approve your code
merge the pull request in
If your changes fall behind the main branch, you will need to update your branch before merging it in. First, checkout the main branch and pull the new changes. Then, checkout your branch and add the changes from main. There are two ways of doing this:
git merge main - merge the changes you are missing from main, creating a new point in history for the combined changes
git rebase main - change history so that it is as if your changes started from where main is now - change the base of your branch to be the current state of main.
If there are conflicts, stay calm and take a look at your files. You should see something like this (from here:
<pre style="background-color:#ffffff;">
<span style="color:#323232;">here is some content not affected by the conflict
</span><span style="color:#323232;"><<<<<<< main
</span><span style="color:#323232;">this is conflicted text from main
</span><span style="color:#323232;">=======
</span><span style="color:#323232;">this is conflicted text from feature branch
</span><span style="color:#323232;">>>>>>>> feature branch
</span>
You need to edit the file to decide which of main’s code and which of your branch’s code to use. Once you are done, run:
git commit: if you are doing the merge method
git rebase --continue: if you are rebasing. A rebase resolves conflicts one commit at a time, so you might be editing code from previous commits, and you might need to repeat this process for the rest of your commits until you get back up to now.
Another tip: if git complains about uncommited changes, or if you just want to save all of your changes somewhere and go back to a clean slate, you can use git stash. This will create a local stash of your current changes, and allow you to get them back later with git stash apply or git stash pop.
And you aren’t expected to remember it all. That’s what man git, Google, and websites like git.wtf are for. Or, you can call that one friend who understands it, and ask them for help ;)
Travis used to be brutal about this. Email headlines that were like “Still failing…”, one piled up after another when you were trying to tweak the CI process.
Those towers actually fell because someone used an oven as depicted by the image on the right, those planes are CGI and a corporate cover-up trying to avoid an OSHA fine. So obvious, I can’t believe these sheeple actually fell for the lie. Smh my head… 🙄
Now that we’ve moved away from reddit can we just bring back emojis already? I know. I KNOW. They’re hated for some silly reason but I’d rather see 😏 than jk or /s in any form ever.
I’m honestly amazed that the no emoji culture on Reddit persisted even after it became super mainstream. But agreed, I actually like emoji for adding emotion/intent indicators to text. I use them all the time in personal conversations and work Slack, but never ever on Reddit for whatever reason haha.
They’ve been a little less militant about it over the last couple of years. Probably because newer/younger users have been rolling in that don’t have the hate for it lol
Make it just run and pre install it on most computers.
With “just run” I mean things like:
Audio just working
Bluetooth just working
Bluetooth and audio working together (I still can’t get this one right, after 5 evenings of trying)
WiFi supporting all the frequencies, instead of just some
remembering monitor configurations
Troubleshooting audio shouldn’t mean that you almost completely kill your OS with that
You know, things like that that might cost you an evening or two or three to figure and make you feel like you’re the rarest edge case alive. On Windows, these work just fine out of the box.
I know this ain’t easy to get to, but I can’t recommend people to use Linux when even a phones does perfectly fine out of the box results in at least an evening of troubleshooting.
Yeah I use Debian. (At least once a while when I decide to give it yet another shot…)
Edit: in case you are interested, I can give some extra details on that list, and how I fixed them or not. But all these fixes ain’t a thing I’d expect the median user to be able to figure.
Out of curiosity, how long ago did these problems happen? I’ve been using Mint and Xubuntu for a while now, but had to use a few different troubleshooting distros to fix a Windows boot issue, and none of these came up. As these are Debian based distros, I’d expect the same problems to filter down.
The only thing I’ve had issues with lately is setting up a USB wifi adapter on a Raspberry Pi, but I’d expect some problems with that.
Around a year ago I fixed the bigger issues, but I started with Linux around 5 years ago. The WiFi issue has been around a month ago, but didn’t do a lot of troubleshooting outside of rebooting and browsing all wicd settings because well I was offline because of it. Didn’t visit that place again and at home there’s wifi on all bands as well as ethernet almost everywhere, so the issue doesn’t hurt me that much.
Booted into it today to see if things are better, ran the update/upgrade/reboot after and:
Bluetooth seems to be better! It now connects to my headphones even when paired before. But now I fails a2dp even after forget/re-pair.
I had to start the system a couple of times before it actually did start, there’s been some issues finding thermal data of the cpu during startup. I’ll play around with it a bit these days, but sadly it did not magically just work.
Why would you expect issues with an external WiFi adapter for the RasPi?
I wonder if it was an edge case that the Linux driver didn’t account for, like a minor incompatibility between the two devices.
You’ve just reminded me that I had a Bluetooth problem with my laptop a few years ago. My headset would connect and work properly, but wouldn’t be recognised after the laptop had either been to sleep or shut down. I had to go through the bluetooth device folder, something like /dev/bluetooth/, find the folder that corresponded with the headset’s address, and delete the cache folder inside. It would then work until the next sleep / shut down.
I expected problems with the Pi because USB wifi has always seemed to be a bit dodgy, even on Windows, and wifi is apparently still a problem area with Linux. Add to that the Pi’s limited distro, and I thought it was bound to go wrong.
That’s kinda the problem here. I’ve heard people say how complex and difficult Android is so they have to use iOS.
People have personal experiences and beliefs that differ and there’s no way to fix them other than to dive into it and they don’t want to dive into it. Unless they are highly motivated to change they will likely just stay where they’re comfortable.
It’s like trying to logically and reasonably explain why being vegan is morally right to someone who absolutely refuses to read the labels on the stuff they buy. They’re not going to want to go into the BIOS to fix a boot order to boot to a flash drive let alone learn a new UI. Hell, most people didn’t even want to move off Windows XP, 7, now 10 till they are absolutely forced to.
It was never about what problems you have had it is about the problems they have had. Most of the time MacOS/Windows are good enough for most users.
Ubuntu 22.04 (granted it was upgraded a few times, but origianlly a 20.10 box), even with bredr set int he conf, wouldnt work with Airpods…
pop_os does, but since its a dual boot, i have to re-pair them if i use it in another OS, since they share the bluetooth adapater.
Using an egpu has no hotplug. And you need something like egpu-switcher to manage the config. - github.com/hertg/egpu-switcher
this also wont apply to pre-login stuff. You would need to copy that over to a different file there.
this also wouldnt work if you had say…3 monitors and wanted to use 2 configs. In windows you can do that with super+P and swap between extend and only external etc.
My pop_os install wont recognize my logitech 720p USB camera thats like. Its a brand new install of 22.04.
Teams, even in the PWA, and other apps often dont respect the system defaults for sound/mic inputs. Especially if you have a few, which all laptops do since theres always shitty onboard speakers and mics.
There are all experiences of mine from this calendar year. I can work around them mostly. But my wife or others…no way. They would just chuck the PC at me and say “fix it”. These are all also things that work OOB on windows or MacOS.
A fellow laptop user :-) For the monitor setups I use batch files with xrandr settings. I could imagine there being a way to get them to run via hotkeys…
But yes, the whole thing summs up with “I may use it for myself, but I just can’t recommend the whole package without providing tech support for it”.
I just had the opposite problem, tried to re-image a brand new laptop with windows 10, keyboard and mouse dont work in setup. Works in the bios, works in linux, doesn’t work in windows until it can hit windows update. Honestly in recent years stuff in linux just works.
It’s actually kind of beautiful because it makes me think of breaking the grid of space to do some kind of faster-than-light travel.
This could be a ripping seam in the fabric of spacetime at the edge of an Alcubierre warp bubble.
Like a “behind the veil” opportunity appearing as a rent in the backdrop of reality, that you could step through. A secret cave entrance opening in a Zelda game. That feeling.
lemmy.ml
Newest