this post was submitted on 25 May 2025
682 points (99.0% liked)

linuxmemes

25135 readers
2699 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    682
    It's gotten better (sub.wetshaving.social)
    submitted 6 days ago by [email protected] to c/[email protected]
    59 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 13 points 5 days ago* (last edited 4 days ago)

    I've had a couple of issues like this:

    • Wireless mouse has a flaky connection. Turns out the issue was the USB port it was plugged into (probably RF interference as other devices worked fine on that port)

    • We had a couple of radio receivers in a server rack. The scale of the project had shrunk over the years, so what used to fill up 2 racks now only half filled them (mostly because of upgraded components becoming faster and smaller over the years). Another project needed needed some rackspace, so we reracked everything into a single rack. When we were done, we found that one of our receivers couldn't get a signal, and another would lose it regularly. Checked over all of our connections and the antennas, but everything seemed normal. Turns out something in the other project was blasting out RF interference.

    • We would occasionally need to manually move data on/off a server using a USB2.0 hard drive. This worked fine for years, until one day we had a server that would randomly disconnect from the drive a few seconds into the transfer. Tried different ports, same issue. The drive itself worked with all the others, so we decided the issue must be with the server. We swapped it out for a brand new one with plans to send the old one back for warranty repairs. Except the new one has the exact same issue. Both servers came from a newish batch from the OEM. Turns out that the earlier versions had a hardware "bug" where the USB ports would source more than the 500ma allowed by the spec. Since they fixed that, our drive would trigger the current limit during sustained use and temporarily depower the port. Solution: get a USB Y cable and power provider power from a wall block

    • I had a mouse that would double click (or more) when you pushed the button. This was pretty obviously a hardware issue, but I figured I could just tell the computer to ignore double clicks that happened "too fast" and avoid needing a new mouse. In theory that should have worked, but the input stack on Linux turned out to be a giant web that I couldn't figure out, so I ended up opening the mouse and soldering on a random capacitor I had lieing around.

    • We had a laptop with a dead monitor that would mysteriously work at times. It turns out that most of the time, it was sitting on another laptop (of the same type). Those laptops had a magnet latch to hold them shut. It turns out that said magnet also was used as part of a "laptop closed" sensor that would disable the monitor, and the bottom laptop would trigger the sensor in the top one.