2020. 2. 12. 02:22ㆍ카테고리 없음
I thought I downloaded a bad.dmg file. But no, after two more from two different other developers, including a re-download of a previously mountable one, now I can safely conclude it's the abomination known as DiskImageMounter and its henchman diskimages-helper that are the real culprit for this latest string of supposedly unmountable images.
I'm sure nothing short of a reboot would fix it, unless I want to bother figuring out which launchd job or two I could give a kick to. I think what triggered this is simply downloading a few.dmg files and trying to mount all of them via double-clicking in quick succession. Based on what I've read about DiskUtility in 10.12/10.13 and iOS 11 in other threads, I can imagine things could be only getting worse in later OS X. I thought I downloaded a bad.dmg file. But no, after two more from two different other developers, including a re-download of a previously mountable one, now I can safely conclude it's the abomination known as DiskImageMounter and its henchman diskimages-helper that are the real culprit for this latest string of supposedly unmountable images. I'm sure nothing short of a reboot would fix it, unless I want to bother figuring out which launchd job or two I could give a kick to. I think what triggered this is simply downloading a few.dmg files and trying to mount all of them via double-clicking in quick succession.
Based on what I've read about DiskUtility in 10.12/10.13 and iOS 11 in other threads, I can imagine things could be only getting worse in later OS X. Maybe report this bug unless you really don't want it to be fixed. If they are public may be able to take a look fwiw:.dmg is on the way out the door but will not be all the way out for a few years For one, try ChromiumOSX62.0.3202.62.dmg 2017-10-18 79.0 MB It was previously mountable. Now I downloaded it a second time, after two other unmountable dmgs from other devs.
Not surprisingly, DiskImageMounter also claims no mountable image or some gobblygook along that line. No, I haven't rebooted. I refuse to do it, just for this DiskImageMounter stupidity. For one, try ChromiumOSX62.0.3202.62.dmg 2017-10-18 79.0 MB Works fine for me on 10.13. Did you verify the file checksums, especially since you said the file worked one, but not after redownloading?
Nah, it's definitely DiskImageMounter or its auxiliary, since (now) four other DMGs from various places don't mount either. Never had problem with image mounting until AAPL decided to be cute and moved the mounting function from DiskUtility (or its precedessor) to the goofiness of '/System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/Resources/DiskImages UI Agent.app/Contents/MacOS/DiskImages UI Agent' and '/System/Library/PrivateFrameworks/DiskImages.framework/Resources/diskimages-helper'. It's like the NTP fiasco in 10.9. I have been having some really weird issues with dmg files and external drives showing the wrong name or not showing at all in disk utility. My 2TB WD external drive was mounting with the wrong name and therefore Time Machine would not back up. Sometimes it refused to even show up is Disk Utility unless I rebooted.
Didn't matter which port I used to connect it. A reboot always fixes it. Right now I have a 'Brackets.Release.1.11.dmg' file saved in Downloads. When I mount it, it shows up as 'Google Chrome 63.0.32390.30-63.0.3239.40 Beta Update'. The contents of the file appear to be correct (Brackets.app) but any attempt to copy the file anywhere fails.
It tells me, '. One or more required items can't be found. Error code -43'. Unmounting and re-mounting the DMG didn't fix it. Renaming the DMG didn't fix it.
Creating a duplicate of the DMG didn't fix it. Redownloading the DMG didn't fix it. (Also tried downloading from another location just to be sure it wasn't a location issue.). I ran first aid on the SSD in the computer (13' MB Pro escape just a few months old), no issues were found.
Verified the DMG using disk utility, no issues found. Verified the drive after the DMG is mounted (with the wrong name), no issues found. I've seen this with other DMG files since upgrading to HS so I don't think it's anything specific to this one. With another DMG which had this same issue, I compared the checksum on the downloaded file to the one listed on the web and they matched. A reboot always fixes this but that's really the only thing I'm technically proficient enough to do.
I suspect that an upcoming patch will resolve it but until then, I can't help but wonder if the fact that a DMG can be mounted with the wrong name doesn't represent some sort of security risk. So I rebooted, and the problem went away, until yesterday, when two of the three DMGs downloaded refuse to mount. Of course they can't be deleted either, cuz you know, the dumb little 'helpers' are 'using' them. I bet any further DMG downloads would fail to mount too, but they all would mount just fine after YA reboot, but who has time for this reboot-o-rama (much less filing Radar and be AAPL's unpaid guinea pigs) just because AAPL has all the time in the world for animojis / ML auto-correct SNAFUs / auto-indexing your bra pix on your phone, but can't bother hiring competent devs and QA peeps for basic disk image mounting, which used to work just fine in DiskUtility. And if AAPL ever moves to the App Store as the sole delivery mechanism, it'd be an even bigger disaster than DiskimageMounter, because the piece of junk fails to connect about 50% of the time, due to the weird way AAPL makes OS X / macOS resolve DNS.
Diskimagemounter Download Mac
(Yes, I've the dev options enabled, and nothing in that menu could 'fix' that). Again, a reboot 'cures' it. Actually, it even happens on my iPhone, when Search in the App Store becomes totally unresponsive (returns no results) and requires a reboot of the entire phone to 'fix'. Besides, it's totally infeasible to browse for the exact app you know you're looking for, because of the way AAPL has set up App Store.