I prefer the term enchanted rocks

well, teaching sand to think has in principle some relation to the problem ( sand = silicon and computer chips are made out of silicon). Not sure is that connection intended or coincidence.

@@ClemensKatzerbrother, that was the entire stick of his comment lmao

@@thahrimdon Alright, thanks. Was guessing so but not sure. My favorite line is "Computer help us to get things done faster, which we wouldn't need to be doing without them in first place".

@@kreuner11 More computer manuals need to be written like alchemical texts like the Ripley Scroll.

Beat me to it! Similar perfectly reasonable explanation once you discover the root cause.

There's also the phase of the moon bug. Happened both in ancient CS history (some timestamp code at MIT) as well as at CERN, who first blamed software, then discovered that the moon's gravity was bending their particle accelerator.

@@BlakeHelms sendmail gives me ptsd...

@@methanbreather* smtp

Oh! No! Unix Hater Book y haunting me again! AAAAAHHHH!

100% Steve credited her. I’m amazed at the ability of people to skip that step. It frankly *adds* to the enigma. Sometimes the end user does have the best diagnostics

It's odd, but it's the type of reason you might be more likely to spot because you're just a regular user and not a tech person. I can hear it now: "Oh, it's Tuesday. It never prints on Tuesday." "What do you mean, 'It never prints on Tuesday'?" "It doesn't. Pay attention, and you'll see." Sure enough.

Sometimes it takes a woman's intuition to notice these kinds of things.

@@seheyt That's why I sometimes discuss bugs I'm having with my tech illiterate dad, he actually helped me find the root cause a few times with his questions that would be dismissed by many people.

Yay Steve's wife!!!

That's a stupid place to put in an air intake tbh

@@betaplay2914 On a motorcycle there aren't many places you can put the air intake, under the seat is common because it's fairly protected from dirt kicked up by the tires,

@@SomnolentFudge You get ventilated seats as a bonus

Heard similar with a carburettor car, back in the day. PROBLEM: Owner tells the mechanic he goes into the shop, buys a tub of ice-cream, sometimes the car needs a long crank to warm restart. Owner advised to make notes. He does so. Car crank problem occurs when owner buys vanilla ice-cream. If he buys any other flavour ice-cream, the car restarts straight away. REASON: the vanilla ice-cream is the most popular seller, so the freezer cabinet is located on its own at the front of the shop. In the shorter time it takes to buy vanilla, the car engine heat-soaks and petrol vaporizes in the fuel line causing a vapour bubble/lock, so the engine needs extended crank to get cooler fuel up from the tank. Buying ice-cream from the other freezers at the back of the store gives the engine more time to cool down and the vapour bubble to disappear.

I feel like I run into so many problems like this in my own life, or not even problems just like explanations for things I was wondering about. Like when I start to go digging in why a certain thing happens in my appartment or something I almost always figure out that it's some bizarre alignment of completely unrelated things. I don't know if this just happens to me or I'm just the only person willing to go looking into seemingly trivial things.

Modern GNOME developer confirmed.

Why would you even want to print at all? Just draw it!

Next, we’re gonna have mail servers that don’t work on Sundays

Why would you print? It just wastes paper.

"Printers aren't userfriendly and buggy.. It shouldn't be officially supported until we find more modern way to solve this issue." *drops printers support from Gnome Settings panel. [Btw I use Gnome and I love it]

that is fascinating, how long ago was this? and how did you end up "fixing" it?

@@3laws292 I think it was mid-90s. Mice still had balls but also a light that shone through toothed wheels for motion detection. We ended up pulling the blind over the study sky light :-)

Kind of had that at church, I set up an temporary audio system in their hall for an 'Alpha course', however the CD player refused to run, eventually I found a piece of strategically placed cardboard between it and a sunny window fixed the problem.

Yep, we had that too, our report was "mouse does not work in the afternoon". Funny thing was it worked for us when we went there to check. All IT guys had bigger hands and we held the mouse differently so we shielded it from the sun :)

Am I the only one that read "house"

I heard a similar story, where by analyzing the output of a sensitive machine, someone traced the issue to a worn-out fan, despite never having been in the building themselves.

A lot of instruments used in physics are so sensitive that this kind of thing isn't even really weird. There's a famous experiment based on the photoelectric effect that is almost always done at night because something as simple as a truck driving by outside can fuck it up.

"You shat over my work"?

@@hedgehog3180 Heard old story at univer from my lector. In USSR times scientists couldn't calibrate some machinery. Found that one of female laborants was wearing neilon stockings. Electrostatics.

Or guys in a satellite dish control who were looking for fast radio bursts from outer space. A few times a year they found a radio signal but could not determine the area of space from which it comes. After many equipment upgrades and money spent, they found that if someone in the kitchen opened the microwave door while it was working there was a small radiation leak which was picked up by sensors.

I didn't even notice that XD

But does he see what he did there?

Yeah, this is one of those situations where technical knowledge is actually an impediment to identifying the problem. A technical user is going to dismiss "it's Tuesday" as having any relevance to the problem, because *obviously* it's not relevant, that's stupid. But not having preconceived notions from technical knowledge allows you to make connections like this, which will usually be unhelpful but every now and then a weird situation like this pops up where it's actually critical.

When a clueless user is more helpful in debugging than a rubber duck.

​@@nezu_ccthis is why qa positions in software companies exist

I've had a user figure out a solution to a problem with Microsoft Exchange 2007 that ended up getting elevated to division manager because everyone thought everyone else was hallucinating! I get a support request that says "Outlook will not attach PDF document unless I rename it". Ok, user probably put stupid characters in the file name that NTFS will handle but SMTP will not, right? Nope. File name was "Report_Output_nnnnnnnn.pdf" where the n's were a running serial number. And Outlook would attach it just fine. But when clicking send Exchange would barf up a spectacular error message with all sorts of complaints about missing character sets and what not. My first question was "How did you think of changing the name?" to which I was replied "I didn't understand the error, but I never liked the look of how the report generator names documents, so I usually rename them myself, and this time I forgot, so I tried that to see if Outlook didn't like it either". Quality thinking right there! That's totally how Outlook works. It can like or not like file names, just like you! :P The user had removed the "_Output_" part... Which looks enough like a key word that I was paying full attention (while trying not to laugh). But it gets weirder! The problem would only trigger if it WASN'T the FIRST instance of the SMTP relay got the e-mail. And because Microsoft is Microsoft... Exchange doesn't use a round-robin approach to scheduling. This means that if the server was mostly idle, the bug wouldn't trigger. Exchange had to be on a multi-core CPU and there had to be enough of a queue that it would start issuing mails to the subsequent threads. Every developer at Microsoft apparently just had a local instance running... which was never busy enough to trigger the bug. But we were Microsoft Gold Partner certified, so they were kinda stuck with listening to me. It took over 3 months before a developer finally reproduced it, and boy did I get a polite mail. What was so bloody weird about it is that it wasn't a general problem. I obtained a whole bunch of the report files, with their original names, and I never found out which combination of numbers couldn't have the "_Output_" in the middle. Some could, some couldn't. But they never explained to me exactly what the problem was. I just kept quiet about it for a long time, as it might have been exploitable somehow.

A factor that is hard for for professional to notice

I have DEFINITELY run into those kind extremely bizarre behaviors, where the description of the bug sounds absolutely bizarre, and yes, we do stare at multiple log files on our screens comparing things until we can find a pattern. Most recently, it was SQL query results being returned at a lower bandwidth from the SQL server when the result consisted of a larger dataset. It turned out it was released to the application server and database server being on different subnets. But that wasn't the problem, the problem was that there was an HAProxy between them that had a kernel parameter set that caused the size of TCP packets that could be sent from one side to the other to be smaller than ideal, so instead of a few large packets, the server was being forced to send a small packet, wait for an ACK, send another small packet, wait for an ACK, etc. Crawled through all packet data from Wireshark just to find out the problem wasn't even on the database or application server, then had to study all the kernel parameters related to how HAProxy handles TCP packets until I found the one to blame. Bam, 25 Gbps bandwidth fixed.

ADAMS!

This the comment i was gonna put if no one else did 🤣

That guy's wife figured it out. Mad props to her for doing what no one else could

👏 👏 👏

I can't be the only one who read this in Raul Julia's voice. Or maybe I am, that movie was terrible. Bro as Bison is the only thing that makes it even remotely watchable. XD

@@AntiSpaceGhost The movie was terrible, but Raul Julia was bloody awesome in it.

YES! YESSSSSS!!

I was looking for this comment

My mother has caught issues like this in all manner of systems she did not understand. It has been both hilarious and infuriating to watch, every single time.

Well if you're not a developer you won't be tunnelvisioned by things that were the cause of previous bugs, I could definitely see someone who isn't that experienced with computers remembering what days their printer didn't work and then noticing a pattern

Yeah, once the "impossible" pattern is discovered, it's easy to figure out, but that kind of pattern is just impossible to imagine unless you think it's possible, and despite being possible, you kind of need to not understand what's possible to believe it.

Not necessarily, just not a dev in that language/operating system. I know a number of system testers who might have made that connection, but only if they weren't working on it.

Reminds me of when folk would send ping user +++ATH over IRC to drop others off, before modems started time-gating the +++ exit data mode string

sounds like a video I watched more recently about Mazda's infotainment system getting broken by %i from a radio station

​@@triffid0hunter Yeah. I remember ping utility that exploits that bug. People used it to free slots on ISP modem pool.

And that's why you always sanitize your inputs.

Close to sanitising is proper encoding. I've seen too much gore. My email address with a + often causes errors, but not even consistently, like my electricity company's website threw an error, but everything seems to work.

Yep. Things failing silently (or more accurately, printing errors only to a nonexistent terminal output) is a way too common issue in the open source world.

@@stevethepocket In the closed source world these Issues do exist too, but you can't even fix them, not even if you are programmer and could understand what is going on - since you can't analyze the source code.

@@deineroehre today I was printing a large PDF on my win11 laptop and the printer just randomly decided to print an entirely black page instead of one of the actual page. This caused the printer to run out of black ink except the printer itself never realized it had run out of black ink so I came back to a bunch of mostly blank pages. The printer also just started printing garbage pages where it fucked up the line spacing completely and I have no idea why because as far as my laptop was concerned everything was fine.

It's usually printer manufacturers that try to write their own drivers without knowing anything about Linux and don't even release source code so people who do know can try to help. Thank god we have IPP Everywhere now. No more flaky at best and nonexistent at worst vendor-provided drivers. The problem is confirming that a new printer supports it (many but not all do now) without buying one and actually testing it, or possibly inferring it from some advertised mobile printing support that may or may not use the same underlying protocol that CUPS uses, since on top of coming up with the absolute dumbest sounding name possible for a technology that completely eliminates the one major software problem that has plagued printers for decades they also decided not to actually market it at all. In case you've never heard of IPP Everywhere, which I assume applies to at least 99% of people reading this, it's a standard built on top of the (fairly useless in practice) basic IPP protocol that defines a common page definition language so printers can work without any specialized driver whatsoever. You'd never ever know it existed though unless you installed a recent version of CUPS and noticed a print queue for a network printer magically appearing, and hadn't already set up that same printer, AND actually decided against all logic to try printing to it despite not having selected a specific driver for it. It's been pretty widely implemented for more than 10 years now I think, but like I said, zero marketing resources. Zero. Seriously. You finally get around to fixing the one problem everyone hates about your industry (ok one of the two problems. fixing the other obvious one means losing a lot of money) and just... don't bother to tell anyone about it? What the fuck.

The opposite is a blue screen crash with random codes, together with endless dump files that the internet can't make sense of.

I once had an Issue where the Wifi in my old house blacked out every time the traffic light outside my toilet turned red. Turns out it had a radar vehicle/pedestrian detector on it, which worked (or at least transmitted a harmonic) at 2.4GHz, and did so at enough power to make everyones Wifi take a dump. I only got the idea after reading a reddit post where someone had the exact same problem, and found the light to be at fault, so I tried it myself, and sure enough: every time that stupid light turns red, 0.5mbps. Light turns green, 45mbps (shitty DSL). Tried it 10+ times, it was definitely the traffic light.

«Cause it's Tuesday. It's common knowledge, like we don't eat red meat on Fridays, or not stay sober on december 31. We don't print on Tuesday, nobody prints on Tueday, and this I'm pretty certain since Gutenberg, I don't remember but that's worldwide. Well have you ever noticed no one prints on Tuesday right? Not even the press, not in schools, have YOU or your parents ever printed even your birthday card on a Tuesday, do you even know about offset printing operators have their rest day today? Go check even to a photographer, a photo booth, ...you found that today? Find me one document printed on a Tuesday. Why do shop's printers are thermal and not ink on paper? So they don't really print, they can print on Tuesday, there's some printers that are like typewriters for that reason i think.» Boss: «I have printed something last tuesday, here's a report of taxe-» «Wow, wait. You printed it on Monday night or was that tasker planned it to get print on Wendsday morning? You printed this on a Tuesday? okay, you did change your computer's date, or ignored the warning with the date ‘‘Are you sure you want to do this’’ this is your right, it's not even illegal in this state, but this is a malpractice, be advised about that. If you want, never repeat to anyone you print on Tuesday, there is a spool, the printer will store what's to print and will turn on tonight at 23:59:59 and start printing today's chore at one second past midnight. I don't make the unwritten rules, just don't aske me to do this. I like you, I won't tell anything, you have a printer in your office, make sure to close the door, we never had this conversation okay?»

bri'ish moment

The Valve-update cycle

I think the worst one is honestly "it started working, but I didn't change anything"

​@@OhhCrapGuy the one after that is "it started working!", "what did you do?", 10 changes get listed, I wonder which did it.

@@TealJosh that's fine, I can find out, just a thousand combinations of fixes to test, and I can automate doing that.

Oh yeah I hate that situation actually. Things I encountered so far: - Made a piece of software, which CRC32 itself by taking the last 4 bytes to write it's CRC to. Avira Antivirus complains. - Deleted that piece of code and UPX'd it because exe size - Avira Antivirus complained AGAIN. Fixed by uninstalling Avira. - Made a piece of software, which was basically a GUI for another program. Failed to run on another computer, saying the registry path doesn't exist. Program had exception handling for that, if it couldn't read the registry key, it would create them. Still failed to run as intended. - Made a program to decrypt and encrypt files of a game for easy modding. Works fine on my PC. Uploaded it to VirusTotal for lulz. Code Red: Ransomware. It didn't even had code for networking, but the sandboxes kept saying it connects to the Internet (how?). Reinstalled my IDE and recompiled the C++ source. Didn't fix the problem. It's not even AES, it's Blowfish. - Made a game using RenPy. Gave it to a friend for testplay. Game requested access to the internet, which it shouldn't do - at all. - Made a program to backup data. Had an easteregg in it. Had to remove the easteregg, because "professional". Extracted the eastergg and made it a standalone. I put the easteregg on my website. My domain gets flagged for malware. I hate programming.

"Then let's ship your machine to the customer" - and that's the story of how Docker was born. (Not really, but it makes a good joke)

And it was a woman, someone's wife. :)

​@@simonmaracine4721 She didn't fix it tho just correlated a pattern

It took a nontechnical person to recognize a pattern that makes no sense according to a superficial understanding of computing.

i mean, we can't assume their wife was a non-technical user tbf

@@yukijoou I mean, she managed to get work done with OpenOffice, so nontechnical is heavily qualified here. "Non-dev" might be less inaccurate

Excellent. You'd think a Japanese manufacturer shouldn't make this type of mistake? It can get pretty toasty and aircon isn't 100% pervasive. But apparently they do.

they take A/C there for granted I think

Except this bug was literally due to magic, not science!

Oof, too real. I have two stories that match that level of pain. First, the bug that only shows in production when the server is under load. Like say 9AM when the code was deployed at midnight. Turns out that .NET Debuggers and memory snapshot tools suck at diagnosing stack overflow errors in code that has awaits. Second, the C++ Program where the original programmers assumed not having an initializer means the object is zero initialized. Pro-tip. It's initialized with whatever is in memory at that location. Which most of the time is zero, but not always!

The Heisenbug: The one that never shows up when observed in a debugger, but is always present in the release build.

I had one where one of the optimization levels wouldn't work right and it took a long time to find out that the compiler had decided something should overlap the stack by a couple bytes.

​​@@arthurmoore9488I've encountered similar issues before where restarting a computer fails to fix an issue, but a shutdown + waiting 10 seconds + power-on fixes it, because certain hardware devices return to their default states when power is removed. A simple restart doesn't reset their cache RAM or registers to zero, so things will continue to fail or behave unexpectedly until returned to a 'safe' state.

I have ran into this. Some compilers may put extra buffer around variables in debug mode, masking out of bounds errors, or the executable may have other differences that cause release only problems. Very frustrating to diagnose.

That laptop wouldn't print on Luesdays.

Lhal’s a good one!

seems like a faulty font to me, either the font is missing the bar or it's ordered the wrong way around (basically the order of the points should be ordered clockwise iirc, and if it's counterclockwise it can cause issues)

@@satibel But the same fonts were fine on other machines. Actually, it wasn't just the horizontal line missing, the corresponding part of the vertical line was missing too. So, it turned 't' not into 'l', but more like into 'i'.

@@danagoyette7932 still seems to me like the font has a quirk on the bar part that doesn't render properly at that resolution.

*Are you sure about that?*

Icarly fan

@@PowerPuffBoysZ That predates iCarly by about 100 years. Maybe more.

So two bugs, the short field, and the fact it allowed the data to extend to another field.

​@@paulstubbs7678 I see that as one bug. On old hardware with such limited memory, where else is the overflow going to go? That and being to slow to afford runtime error detection.

My friend had a car that would only start when he got pissed off, slammed the door, and tried again later. If he wasn't angry enough, it didn't work. We figured out the relay for the fuel pump was in the fuse box near the door. It would stick after shutting off, and needed a jolt to turn on again.

I heard a similar story, where if they went to the store with the express purpose of buying vanilla ice cream, they'd be in and out in a few minutes, but if they went to the store and didn't know what they wanted, they'd wonder around for a bit before returning

​@@JB52520 That reminds me of some older touch screens. Modern touch screens are all capactive reactance based, but there are some other types of touchcreen technologies. Touch screens that work by measureing applied pressure tend not to work until people get annoyed and apply more pressure, causing the touch screen to respond. Such older touch screens might be found in things like old ATMs for example.

Never on Tuesday

@@SeekingTheLoveThatGodMeans7648 Yep!

Microsoft 312

@@ifritdiezel I don't get it.

@@Amos_Huclkeberry it's like microsoft 365 (days in a year) minus all the tuesdays

Debug was really working, then.

I'm sure plenty of hardware engineers have considered just telling the user "it only works if you hold your finger here"!

Makes me think of renaming your game executable the same as a benchmarking suite, so the GPU and CPU will schedule it higher

@@renakunisaki CEOs too. Steve Jobs: "Just avoid holding it that way". (aka "you're holding it wrong")

@@renakunisaki Crack in the ground layer of a multilayer board. A little pressure and the problem goes away - even the pressure of applying a DMM probe to the test points. Yeah, we've seen that one enough that it is now a running joke.

Ah… didn’t think of magic :-)

I have watched the video and still don't understand what Tuesday has

A bug in `file` and `/etc/magic`

I love how a bug in magic sounds

`file` sucks. This is additional evidence but it already did. Windows-style name suffixes are better, since we can't be assed to consistently use content prefixes as an industry.

Unfortunately for me the answer is currently 'no' - networked printer hanging of a Windows PC

Lucky it wasn't a "can't print on Sundays", it would never have been fixed.

Yes, been their, I had a nice neat looking page of Arduino 'C', however it worked more reliably if I put a nasty looking discontinuation in the middle of it, so I didn't......

Maybe someone should start a Museum of Glitches to showcase the most fascinating ones from throughout computing history. Wouldn't be the dumbest thing anyone's ever made a museum of, I'm sure.

You've heard of a "printer jam", right?

it's a file generated to be used by the Joe's Abstract machine interpreter for the erlang programming language

@@mega_gamer93 But why on earth would you try to identify it ONLY by a date? That was just asking for false positives.

​@@alexatkinit's probably just a byte sequence turned out to say "Tue" instead of something meaningful

@@alexatkin as DrPeeper said. its nto that its identified by Tue, its identified by a specific set of bits at the 4th byte.... one that just happend to match exactly with Tue if converted into ASCII

I remember brodie made a video about a guy who restarted linux a crazy amount of times, because a bug would appear randomly and so rarely, he had to restart like thousands of times to solve the issue

hardware bound issues are even _more_ fun. as an example, for some reason an instruction (forgot which) is about twice as fast on amd cpus than intel, sometimes leading to a race condition on one but not the other. grinding gear games, creators of path of exile said they had servers that caused issues, after a while, they just decided to call them cursed and replace them.

To report errors, you need to think about them beforehand. Who would ever have thought that an error in "file" corrupts printing in OOo? And where would you identify/put that error? Back in the day it would have been /var/log/messages, but "file" worked as designed (a filetype was detected, though the wrong one) and OOo had printed "sucessfully". The whole self-diagnose stuff with OBD-Dongles on cars fails if there is an error not known ("impossible") to the developer/car manufacturer. They can diagnose a failed fuse, a failed window Lifter rear passender side, Insulation Fault from the HV-Battery but rarely a corroded fuse or some weird wiring defects.

@@deineroehre If a file is sent and it's found out that it's the wrong type, then something has to be done. What the program did is just do nothing at all and act as if no file was sent, which is wrong.

​@@deineroehre You raise the error in the component that ran "file" to check the file type, and got back an unsupported type. The code as shipped looked roughly like this if (type_supported) { print_it } What's needed is an "} else { report_error } In general, every if() statement should have an else, unless you consciously decide the right choice is to do nothing (such as skipping comment lines). Or more realistically since the print code is probably long: if ( ! supported_type) { throw_error("unsupported file type") } print stuff

Probably similar thoughts as using the value of π to identify a software version...

one somewhat logical reason i can think of is that it might be a some testing from like 0.0.1 version of file, and the dev just happened to forget it there, because probably not that many files have "Tue" written in that exact specific place, for anyone to notice (until 2008)

@@hornattila Also, it is not necessarily so that the "Tu" in that position of such files had anything to do with Tuesday at all.

@@benhetland576 He said in the video it was supposed to be looking for a specific date string, but they forgot to escape the spaces. So yeah, it was looking specifically for a date, which was asking for trouble.

I think your 'instincts' are probably 20/20 hindsight. Sorry, I've done the same. Thinking 'Well, that was a dumb thing to do', but not thinking of all the other 'dumb' options that are taken on a daily basis, which don't cause an issue. As I say, I'm not having a go at you, I have had similar thoughts, but only after knowing what the issue is.

The beginning's of 'Apple serialised iPhone parts', although I also understand Tesla is also guilty of it.

look up platform secure boot (AMD PSB) there was an issue with some lenovo computers having it enabled by default.

Were these new processors with builtin TPM? Or Windows remembered the serial number...

@@bmwiedemann Nope, this was many years ago, early i5 chips I believe. One of the strangest bugs I've ever come across.

Bug or hardware backdoor? Who knows.

Had a similar bug with a faulty Wii. The code is there, I can see it in the memory dump, so why does it crash on this harmless instruction, behaving as if there's nothing there!? ...oh, _every_ game has this bug when run on this machine...

Had a bug with a large, auto-generated assembly file (don't ask) once where the assembler complained about an unrecognized token. Turning on debugging caused the problem to disappear. Digging around showed that it was an ELSE that was not being recognized - looked fine when editing the file. Suspecting a non-printing character had somehow gotten into the token I did a hex dump of the file and found that the faulty token was at address $FFFE - $10001 and turning on debugging shunted the ELSE a few characters further down the file. Smoking gun time.

I once had a similar one: An Atmega2560 with dementia. You could flash a piece of code to it, reset it as often as you like without removing power, then read it back, and it read back the entire hex file without issues, but if you removed power for more than 5 seconds, it deleted the hey file, and instead returned to an older display controller code I had on there before. If you read the code then, it would spit out that display controller hex file, as if it was never reflashed. Super wierd, especially how it kept the old code in the exact same memory location as the new one (my best guess is that the memory cells suffered some kind of damage while flashing that code, causing them to always return to their old values). Still have that thing on my shelf as an example of a super wierd hardware issue.

@unmountablebootvolume that feels totally impossible. What a head scratcher! Very cool. The original hex is totally corrected when read back? On a von Neumann I maybe could see this, but on Harvard? I feel need sniped haha

I finally found worse than "can't replicate" when reporting an issue: the "obviously won't even try to replicate".

Can't replicate as it's Wednesday, closing.

What software do you maintain so I can avoid it?

Man, atleast attempt to replicate the issue before reporting. It takes like 2 minutes to change your pc's date and you can try it on an empty file so you wont waste the paper if it was a troll.

Those are the worst!

Me: my connection always drops when it's raining ISP: (tests on a nice sunny day) works now!

Now think of the poor souls at NASA trying to fix the last memory bug on Voyager......

I've got a similar problem with a combination of file-server using SMB + XFS for filesystem about 10-15 yrs ago, on RHEL and any derivative distro such as CentOS, CERN linux... with windows clients + linux on server side. Nothing as serious as a plain file corruption (it didn't make them unusable), but with this specific setup (SMB+XFS, nothing with NFS+XFS, nothing with SMB+whatever other fs, could be ext3, ext4, reiserfs, even GFS2), the file on the server side always ended up with a different hash while using SMB for transfer and XFS on the receiving end. And it had nothing to do with the hardware (whatever motherboard/memory type/network card/raid card or disk controller involved). My fix ? Not using XFS when windows is involved in exchanging files with a given server.

Depends on your time zone here it's still Monday when released

Wait it's Tuesday?

Right now, it's Tuesday morning in Australia.

He had to release it as he could not print it

Kind of my problem with windows shares on linux, I'm sure if I try and report I'll get some silly comment back that it's not the shares, but rather xxxxx, and the report will be closed, just like was described in this 'No print on Tuesdays' bug, they just seemed to find a reason to sweep it under the carpet. "Life's good were happy" So maybe the real bug here is the Linux bug reporting setup where things have to be categorised and "lo and behold the poor soul" who puts it in the wrong box, in the Linux programmers eye's

I mean, they probably came back to linux by now. If not because of liking linux, but for windows being shittier by the fay

The executive director at my last job told me in a lunch break convo (caveat: he and I were the only two people at that place who were geeks) that this is the core reason why he believes switching to Linux is a no-go for most organizations. Unless Linux has the "killer app" that their organization absolutely needs, then it's just too much hassle to retrain everyone on a different OS with different applications and best practices to justify the cost savings.

Yes, I bet a few did, not because of the bug, but rather the fact they were ignored and nobody took it seriously.

@@pyrioncelendil I think Linux kind of finally has that 'feature', 'No Microsoft ramming xx down your throat'

Linux keeps getting better even when it doesn't actually improve, by just letting the others get worse.

Nothing helps more when trying to get something to work than asking how to make it work, _especially_ if you don't get an answer.

Ah yes, the bugs that disappear as soon as you call a technician!

It makes sense, UTF-16 characters are made up of more bytes, so if the message box is just told "display that many characters from this memory region", it would try to display double the bytes

sounds like something related to the I²C bus. weird.

hmm... my duration is a lot shorter, but I have an issue where one of my monitors cuts out briefly whenever I'm watching something on Prime Video.. next time there's something there I want to watch I'll try unplugging my hub lol

@@isaac_marcus just prime? sounds like a software problem then?

@bullzebub yup, just Prime (well, out of the many things I've used. Could be something else out there that does it). It's probably something software but I could never figure out what it was doing differently (beyond my current knowledge). All video players done in Chrome, displayed on the same monitor, always causes the same one the blink on and off (not the one it's on). Typing it out like this I should try to see if it happens in another browser. I tried things like toggling hardware acceleration, driver updates, the usual suspects.

if you have 5000 series ryzen like me, theres an unfixable bug either in the cpu microcode or in the motherbord firmware (b550) that causes all communications lines from the CPU (USB, SATA, PCIe, ethernet, etc) to temporarily freeze and reset. it shows as keyboard inputs "hanging" on windows and gpu util/power slams to idle (even if theres 3d load from a game) before slamming back to 100%. im sure the power supply and gpu power circuitry love going from 0 watts to 330 watts randomly. if you have this hardware, it could be your issue. edit: this is known as the usb dropout bug, but it affects more than just usb. amd is not being very transparent about this issue at the moment. i suspect this is also partly why were seeing so many high power GPUs burn up power delivery plugs and board components on the nvidia side.

lmao

That is a great comment

printers generally work better on linux

And if she'd only have worked on Tuesdays:"This Openoffice stuff never works!". So, context and background is important...