Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "macos catalina"
-
After updating to macOS Catalina, I can no longer use photoshop CS6.
and the newer versions require login with a licensed account.......
What to do...5 -
I am an stupid human being. How many times should I experience the same problem to learn from it? I don’t know why should I possibly be obsessed by latest MacOS updates? This fucking error ruined my day. Those fucking idiot coders in Apple must use some unit tests (including transparent iTerm in second display). Fuck you all. My £1600 Macbook pro is literally useless until some fucking coder finds what is wrong in their NEW update.3
-
Just wanted to make a clean install on my iMac. What could possibly go wrong?!
Cleaning the hard disk was interrupted by a process running (kextcache). Catalina wouldn't install ("Incomplete systen on target device". Dropping the terminal I could somehow force unmounting and wipe the disk. Had a BSOD in between. Catalina would still not install ("Failed to install pre boot volume"). Later erasing the disk got blocked by the kernel itself. Felt like trouble and it was: Next time I was greeted with a blinking folder containing a questionmark instead of the bitten Apple.
Last resort: Internet recovery. Installing El Capitan was said to take 7 hours so I took a USB time machine backup of latest Catalina. Installed it, but on reboot it get's stuck when progress bar is at 100%. But at least I've a working recovery again. Yeah, progress!5 -
Updated my Mac this afternoon to macOS Catalina. Apart from rearranging all my apps in Launchpad, the major change I notice is that the terminal is using zsh instead of bash... ok... cool. I don't know anything about zsh... what differences can I expect? Should I go back to bash?5
-
I’m new to using gdb to debug. It could detect the places where I was getting SIGSEGV randomly. But there are also rare cases when the program just gets segmentation fault as soon as it starts, and it when that happens, even my gdb gets frozen and I have to shut down my terminal altogether.
What’s with this ? Is this some sort of kernel error (like Bus error) ? I’m using macOS Catalina and gdb 9.1.2