You'e yping i wong: macOS Catalina stops Twitter desktop app from accepting B, L, M, R, and T in passwords Twitter says a bug in macOS 10.15.1 aka Catalina stops users of the social network's desktop Mac app from entering certain letters in account password fields. When attempting to type their passwords into the application to log in, some characters are ignored, specifically 'b', 'l', 'm', 'r', and 't'. That would make it …
One of the first Windows 10 upgrades disabled six keys on my mum's HP laptop. My first thought was she'd spilled liquid on it, but the keys weren't located next to each other so the update was the next most obvious culprit. I updated the drivers from HP to no effect. Luckily all the keys needed for my password worked, though I had to teach her how to cut and paste characters, which is obviously a pain. I was just about to strip and clean the machine when the next update came, and hey presto, all the keys worked again.
This post has been deleted by its author
PPS: Apparently that $55 billion profit has been further reduced, and is now $55 iion.
Some of that $55 billion profit quite clearly needs to spent on hiring more quality testing and assurance staff for both software and hardware. They also ought to move to a more sane 2 year new operating system release schedule with bug fixes and updates in between.
You can turn it back on again - it's not permanent, just a pain in the arse.
Regedit:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Start = 1
The updates have been resetting it to 3 because surely nobody has an old keyboard that they're comfortable with...
Just keep a cheapie USB keyboard kicking about to make the change (or use the on-screen one).
There was a whole lot to dislike about Steve Jobs, but I can help but think this sort of thing would never have kept appening when he was in charge.
He was, after all, renowned for being an absolute task master when it came to quality checks as well as being one of the only CEOs known to hold those on the top table wholly responsible for their own departments.
It isn't, of course, just a curse of Apple.
It also seems that users- even in the enterprise- have become very tolerant of these repeated problems every time there is an update to an OS or application.
I can imagine that, as a Dev at Apple, the risk of Jobs showing up at YOUR desk to have a screaming tantrum discuss a problematic bug he'd identified, then bursting into tears agreeing to review your fix personally while offering constructive feedback certainly kept you focused on making sure things worked. Telling department heads that any major bugs will mean they'll be picking up their bollocks with a dustpan and brush held personally accountable probably also focused minds.
I guess a visit from "Call me Tim" just doesn't carry the same, ahem, motivational gravitas.
I thought it was pretty clear that I wasn't suggesting things were 100% perfect under him or that there weren't misses, just that there generally tended to be far fewer of them and that people at senior levels tended to be held accountable.
Apologies if that wasn't clear in my initial post.
I used to unreservedly recommend colleagues, family and friends to switch to Apple desktops or laptops.
Since about 2017, no longer.
Apple simply doesn't care about this market segment any more. It has totally lost the plot.
Meanwhile, four years ago, Microsoft switched to free upgrades for Windows 10. It is under far less self-imposed pressure to stick to specific release dates.
Presumably the money it has saved on advertising and marketing new OS names has been and will continue to be substantial, also.
Moreover, Windows 10 minimum and recommended minimum hardware specifications have not changed, except for minimum drive space being raised to 32GB from 16GB (32 bit) and 20GB (64 bit) - arguably long overdue anyway.
What Microsoft seems to understand that Apple does not, is that most PC users could not care less about new OS features, functions, bells, whistles and emojis. They are far more concerned.about continuity of experience - not having to relearn new ways of getting the same old applications working and access to the same old OS functions EVERY year.
And not having the pain of breaking numerous of their trusted applications and having to revert or wait for Apple to pull its finger out and fix bugs.
Time Apple got new Heads of Mac Marketing and Development at least.
Current bunch are very bruised and past their sell-by dates!
I started off agreeing with you until I got to "What Microsoft seems to understand that Apple does not, is that most PC users could not care less about new OS features, functions, bells, whistles and emojis. They are far more concerned.about continuity of experience". Sorry, but that's crud.
If MS understood that people don't care about new OS features, why does MS insist on *two* feature updates a year when one would be plenty? And if MS cares about continuity of experience, why have they still not finished migrating to "Settings" after *four years*? Windows 10 is full of rough edges and half-finished bodges that MS seems to have forgotten about.
When it comes to shonky and unfinished updates being shipped out, MS and Apple are as bad as each other. Neither seems to care about the end-user experience of their operating systems any more sadly.
MacOS - You are unable to log into Twitter
Windows - You have your documents folder deleted
Obviously neither should happen after an update, but if I was forced to have a choice, I know which one I would pick.
Also, in Mac, you go to the App Store and "purchase" thre free update if you want it.
With Windows, it gets forced down your throat whether you want it or not.
Wholeheartedly agree. For the many clueless home users obsessed with getting a laptop, I used to point them to Apple without hesitation up to about 2017. The savings in "[insert unpaid tech support's name here] my computers broken again, can you fix it?" alone were well worth it.
Hardware quality and Op Sys are both regressing at a rate of knots. Butterfly keyboards; (excessive) over-pricing, minimal expansion (if not enforced un-expansion) and negligible repairability - all massive minuses from where they were just 3 years ago. A Macbook Pro was good value not that long ago; when compared to equivalent "premium" PC laptops.
Got a Mac Mini and Macbook Pro (2017) sat at home at the moment and absolutely no intention to upgrade past 10.14 for the forseeable future. And a Mac Pro G5 quad too, but less said about those the better perhaps.
With Windows 10 I cannot recommend Windows in any context at all of course, so I am now really stuck between a rock and a hard place. For casual use, I'd mostly point people to an iPad with a keyboard. For any kind of serious application, for all it is end of life, Win7 still has some major plusses. Or OS X 10.14.
Perhaps unsurprisingly I have shunted most of my personal computing workload onto Linux; and even there the fractured community (particularly in Linux Desktop world) are far from helpful.
BSD is increasingly looking like it's my future. What a time to be alive for a computer fan - the major platforms are all borked so to find anything half interesting one ends up looking backwards at hardware from the 90's or beyond. Most exciting new computer coming soon is the standalone Vampire!
The real story here is the press parroting a twitter dev blaming his problems on Apple, when no-one else has the problem.
Evidence.
1. twitter, multi-billion dollar company has for a long time claimed they couldn't afford to make a Mac App, so they probably don't have much of a Mac dev department.
2. No-one else reporting these problems.
3. UIKeyCommand documentation explicitly says it is for key combos, not single letters. (Quoted at the end of the comment), so this is explicitly not a bug.
4. Oh, UIKeyCommand, so this is a Catalyst App, which is new in Catalina, so when they say regression, they mean Apple did a bug fix from an early Beta. Bet they didn't enable those single key shortcuts in the iOS App.
Supporting quote from UIKeyCommand documentation :-
"Hardware keyboards allow a user to hold down the Control, Option, Command, or other modifier key and press another key in combination to initiate commands such as Cut, Copy, or Paste. You can use instances of this class to define custom command sequences that your app recognizes and then provide an appropriate response."
I think there is enough blame to go around.
The API docs talk about the use of modifier keys, the API allows for the entry of modifiers, but I'm assuming that the API doesn't force the use of a modifier. (i.e. allows you to create a shortcut without any modifier). Whether this is oversight in development, testing or behaviour that they actually wanted is unclear.
However they now have at least one customer building an app using a shortcut without modifier, and so they need to work out what the official line is.
1. Block people creating these.
2. Make this work in a different way (so you can choose on an element whether it handles the key press or not)
3. Explain the behaviour so that people wanting shortcuts without modifiers can still use them.
Spot on. The problem I have is that I cannot validate those issues - I do not have them.
Changing to Catalina beta had some initial pain (the Windows Vista idea of demanding validation of anything that moves in the machine, and Apple went one better by demanding to authorise website downloads). Don't get me wrong, I do like the control (it replicates more or less what Hands Off! was doing) but the changeover should have been a one-off process instead of it showing up every time you start a new app which utterly sinks usability - as I said, a very Vista like approach and even in the System Preferences it has a very unstructured feel to it.
That said, everything else appears to work, including iOS backups via Finder. That said, I did detect featurism (adding features without a real purpose) - I wish they left the hell alone what just worked or left us at least a way to say "act as before". Ramming ideas down people's throat is a Microsoft trait, Apple used to be helpful in keeping UIs mostly the same between versions. No longer :(.
Anyway, for me it works after the initial pain.
Compared to Vista
I don't remember Vista stopping me from inputting passwords...
In fact, I think that the biggest problem Vista had was it's desire to cache as much as possible in memory, which when under-provisioned was less than useful as it would be forced to use the pagefile more than it should need to.
The root cause of the majority of problems was the HW manufacturers selling machines with 1GB or less of memory. If you gave it 2+, it would run great.
Say what you want about it, but it was an improvement over XP for me, and unlike Windows 10, it had ONE control panel that worked consistently.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
