First, I try to install it by just copying the installer app - "can't be verified".
Then I make a bootable USB stick using DiskMaker X - "can't be verified". I run an integrity check on the installer - all good.
I then try running `/path/to/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB-STICK --applicationpath /path/to/Install\ OS\ X\ El\ Capitan.app --nointeraction` - "can't be verified".
Finally I give up and the system is installed via the App Store. The download fails once, it finally completes, and I am left clueless as to why I couldn't reuse the old installer.
An "expired certificate" error message would have saved me many hours. It's unfortunate for the user that Apple puts so little emphasis on letting them be their own tech support.
Many other examples abound. Most errors at least provide a message, but one so generic as to be useless.
2016-03-03 10:59:16.863 PM AirWatch Agent: void AgentReadCallback(NSData *__strong, NSFileHandle *__strong) [Line 1096] Agent received message of type 140
2016-03-03 10:59:16.863 PM AirWatch Agent: -[AWAgentController isCurrentUserManaged] [Line 221] Current User is managed
2016-03-03 10:59:16.863 PM AirWatch Agent: Server Starting new loop for data
2016-03-03 10:59:26.825 PM AirWatch Agent: void AgentReadCallback(NSData *__strong, NSFileHandle *__strong) [Line 1096] Agent received message of type 140
2016-03-03 10:59:26.831 PM AirWatch Agent: -[AWAgentController isCurrentUserManaged] [Line 221] Current User is managed
2016-03-03 10:59:26.832 PM AirWatch Agent: Server Starting new loop for data
"sparsebundle already in use" is the FOAD of error messages. I do love how the (now stale) tools to fix this are maintained by a volunteer on an external site unrelated to apple.
I try not to be too grumpy about it, but I paid $3k for a laptop not to have to fucking deal with windows-style normal operation of the OS and related tools is busted and you're gonna sink hours into debugging it. And least when linux breaks it tends to leave error messages and details in syslog...
I have had substantially fewer problems with Windows 8.1.
Again this was a clean installation. Windows 10 is a joke.
Tends to. Not directly a Linux issue, but i was trying to figure out why one specific program was giving me corrupted MAC errors when connecting via sftp.
All searches indicated it was a network config issue, but no changes seemed to matter.
Eventually i checked the libs the program was compiled with and found the sftp one was "jurassic". One update later and no more errors.
that said, more often than not, a quick dmesg or tail /var/log/messages is all that i need to get something purring again.
tail -f /var/log/system.log
It was maddening.
MacsBug was an essential utility back in those days.
I just stopped running applications that caused too many crashes.
I miss those days dearly. I LOVED being a Mac user during the 1990s.
Don't complain. Even with torrents and 100Mbps fiber, we max out at 1MB/sec here. It reportedly costs 20,000CNY/month (~USD$4500) for an uninhibited 512k connection out of mainland China, if you can get it. (You generally can't.)
I get 10GB/mo and it's $15 for every GB I go over. I'm a "giant pirate" and would usually go through that in an afternoon when I had comcrap. Oh well.
I've had to carefully maintain the .app's myself across a couple Mac's as Apple stopped letting you download things that are no longer in the store. Now they just don't work at all.
The older I get the more I think maybe Richard Stallman isn't crazy.
Say that I buy a piece of software and receive either an installer download or some medium containing the software. The company removes it from the market. I can still perform new installs of their software.
I buy something from an app store. The developer removes it from said store, making it inaccessible for future installs. This developer did the same thing that the other one did, but I'm worse off. How is it more the fault of the developer than Apple/Google/Amazon/Microsoft/Valve/EA/etc? Who changed the way that software distribution works?
App store guidelines require that packages are sandboxed and signed. If you have a signed application, you can circumvent the signature check by disabling gatekeeper, removing the quarantine attribute, or control-clicking and choosing 'Open'.
The DRM mechanism is called 'receipt validation' and has to be enabled by the app developer:
I can sort of see why Apple provides this (to entice companies to publish in the app store), but a developed can decide to be customer-friendly and not check the receipt. So, I think it's fair to blame the developer, not Apple.
(Please correct me if I am wrong, as said, I never distributed an App Store app.)
Since when? I always download .dmg's and install them outside of the Apple Store. You have to do this roundabout security measure in Preferences to run them, but they're always runnable...
Note: you don't have to. You can Control-Click and then choose 'Open' to bypass the signature or unsigned app check. You can also remove the quarantaine attribute with:
xattr -d com.apple.quarantine Your.app
That way, windows can check whether the signature was made during a time when the certificate was valid. This means that when your certificate expires, you won't be able to sign new binaries, but at least the existing ones continue to work.
This is something Apple should really consider implementing - even just for the sake of archival of old OS versions that people might still want to install for nostalgias sake.
To do this, you'd need to compromise or convince a trusted timestamping authority to sign your signing request with an old date.
But yeah, it looks like Microsoft countersigns, assuming this is what that original comment was referring to: https://msdn.microsoft.com/en-us/library/windows/desktop/bb9...
I can't simply set that clock.
But for the code-signer this trick doesn't work, the sign-tool needs to talk to a time-stamp server, usually owned by a certificate authority. I know that the Microsoft signtool.exe and the Java jarsigner can use timestamps, apparently on OSX this works too (search for --timestamp cmdline arg: https://developer.apple.com/library/mac/documentation/Darwin...)
So like a lot of bugs, this is probably one that happens "to some of the people, some of the time".
(Latest OS X 10.11 on latest-model MacBook Pro.)
It's an edge case, but it's still annoying that I can't do this. What if I'm trying to get a non-functional older Mac running again? Stopping all users from doing this does mitigate incompatibility support issues, but it hobbles power users.
To allow this, I don't think they need to add a switch to preferences. I'd be happy with a defaults invocation.
At least apt is as pissy about expired GPG keys as MacOS is about expired code signing certificates.
I have ended up every time using my older 10.8 (ML) install USB every time, then just firing off the free App Store upgrade to 10.11.
So the drive doesn't even have recovery on it.
I would dearly love for Apple to take a year or two (or, hell, five, I'm happy with the current feature set) and just fix bugs. No new features, just bugs. Do another Snow Leopard release, or three.
Here are some of his previous jobs:
- 12 years in IBM's personal computer business, ultimately serving as the director of North American fulfillment
- vice president for corporate materials at Compaq
- closed factories and warehouses, replacing them with contract manufacturers
- advance investment in flash memory from 2005 onwards, guaranteeing stable supply
A logical extension of stuff like "fulfillment", "corporate materials", and "stable supply" would be: "release new software on a regular basis". No?
Still, what is the commercial alternative? Win 10? Not for me!
My partner's itunes refuses to reliably see her iphone.
TimeMachine shits the bed on the regular.
SMB appears to be the future but TimeMachine still requires brittle afp.
On a 15-in late 2013 laptop with 10.10.current, about once out of every 20 times I open the lid the laptop doesn't wake up. Even when it does wake up there is a black screen for a noticeable amount of time. This never used to happen on 10.9.
Apps regularly lose the ability to create audio (spotify, chrome, vlc) if you let them run too long. The solution is to sudo killall audiod.
etc etc etc
From what El Capitan is... it seems reasonable to conclude that either they simply don't have the management/talent to pull this off anymore, or they only care enough to pretend to do it rather than actually focus on it.
AirDrop still doesn't work though...
Seriously Apple, stop making it so goddamned difficult to use your software!!
This makes me wonder if there could be a set of guidelines that could be formulated for acceptable advertising on websites...?
Two random facts to note. First, as far as I know, TidBITS did the first sponsorship program for Internet content back in 1992. If that was in any way responsible for what Internet advertising has become, I apologize. :-) Since we believe in archival content, you can read that article at http://tidbits.com/article/2995
Second, our primary source of revenue is voluntary memberships. We also make about $5K per year from graphical ads, and in last year's membership drive, I challenged the 90% of our readers who are not members to join, promising that we'd drop the graphical ads and affiliate link generators if we could raise another $5K. Alas, the challenge fell short. http://tidbits.com/article/16234
Unless you blocked all of that, expect to see retargeting ads for PDFpen in the near future.