High Sierra 10.13.4 Beta discussion

[thehassle]

Anyone else finding 'dark mode' not working properly? Most of the icons in my menu bar are almost invisible including the Apple Menu icon. They're there but almost impossible to see. The drop down menus appear close to what they should be for some but not others such as Wifi which has the locks and fans greyed out. Turning off 'dark mode' returns the menu bar to normal. Here's what it looks like with dark mode on. View attachment 748823

I edited my original post regarding my Adobe Apps not working in this beta. Well, now they work!
Don't ask me why as I didn't do anything. By the way, this is an early 2011 macbook pro.

Same here. Everything was fine wir all Betas and finals before thsi 10.13.4 beta arrived. After this i have issues with Preview App and have the same issue with the Menubar... Dont know what happend here. System ist a MBP from 2011 with HD3000. Mybe it has to do with Apples Development in eGPU Drivers. Seems the GFX Drivers are broken on some Systems.

 

[castheman]

The beta works great, sometimes a little lags but no further problems.
Only a bug with adobe indesign. A key combination with the select tool is not working. So scaling a picture with keeping its aspect ratio(shift key) is not working. But was aspecting problems with adobe, they don't have a great record with osx updates..

 

[fisherking]

had 2 crashes on the current beta; clicking on a link to me to the login screen, and just now, clicking a link in an email gave me a kernel panic... otherwise lol, all good here (missing dictionary notwithstanding)...

 

[mikecwest]

looks like a graphics card issue. you've rebooted? & what happens with quicklook?

I am having this as well, looks fine in quicklook, but is scrambled in preview....

Image above is what it looks like in Preview app.

mage above is what it looks like in Quicklook.

mage above is what it looks like in Quicktime 7 app.

 

[amaze1499]

@performance APFS vs HFS+ on a HDD

there is definitely a huge difference. after I converted the filesystem back to HFS+ 10.3.4 beta 1 was performing smoothly as expected. With APFS the internal HDD achieved read/write speeds between 3MB/s and 12MB/s rendering the whole thing useless. The HDD that runs the OS now shows read/write speeds at around 65MB/s

@timemachine backup: its not possible though to restore from an APFS backup to a HFS+ HDD. Be aware. That needs to be done through migration assistant. that opened up a whole bunch of other issues, in my case one backup was deleted completely. playing with a beta, you should have a second working backup standing by.

 

[Emma's Dad]

Oh man, that sucks. I'll spare you the verbal spanking you should get for 1) not having a backup (clone) of something to fall back on, 2) using your work machine for beta testing!

Ok, try to save everything you can to an external drive or device other than your boot drive. Boot into recovery mode (command+r) and reinstall the OS.

Well, with every mistake there is a lesson rewarded. I got off the Beta downgraded to "street" 10.13.3. I re-installed Displaylink 4.1 and waited with anticipation while I re-booted my "Death Star" FAIL!. all 3 screens were now dark. I yanked the Diamond adapter which is connected to one of my 27inch screens which resulted in the other 2 screens showing my log-in screen. Once past the login the 2 screens were mirrored. I now plugged the 3rd screen adapter into the USB 3 and again all went dark. I knew that Displaylink 4.1 does not support Mirror mode on OS 13+. But WHY would the screen with the adapter cause not only for all 3 to switch to mirror mode But also instantly log me out.

Again searching on this forum I read that several people had the exact same problem. I was inclined to think it had something to do with my system profile settings but that should not be possible as I re-installed a fresh copy of 10.13.3 onto a formatted SDD?. Almost giving up having to cope with 1 less screen I swam the interwebs for 2-3 hours reading and was rewarded by finding a download of a command script named "Reset macOS display persistence" ran it and rebooted followed by several "tabbings" of Command F1 and BINGO...problem solved...

Sorry for going off topic here (well not entirely). Journey from 10.13.4 beta to a warm fire place with a good bowl of soup took 5.5 hours of solid "escape room" type hamster wheeling......learned quite a bit but what a pain in the keister

 

[amaze1499]

Well, with every mistake there is a lesson rewarded. I got off the Beta downgraded to "street" 10.13.3. I re-installed Displaylink 4.1 and waited with anticipation while I re-booted my "Death Star" FAIL!. all 3 screens were now dark. I yanked the Diamond adapter which is connected to one of my 27inch screens which resulted in the other 2 screens showing my log-in screen. Once past the login the 2 screens were mirrored. I now plugged the 3rd screen adapter into the USB 3 and again all went dark. I knew that Displaylink 4.1 does not support Mirror mode on OS 13+. But WHY would the screen with the adapter cause not only for all 3 to switch to mirror mode But also instantly log me out.

Again searching on this forum I read that several people had the exact same problem. I was inclined to think it had something to do with my system profile settings but that should not be possible as I re-installed a fresh copy of 10.13.3 onto a formatted SDD?. Almost giving up having to cope with 1 less screen I swam the interwebs for 2-3 hours reading and was rewarded by finding a download of a command script named "Reset macOS display persistence" ran it and rebooted followed by several "tabbings" of Command F1 and BINGO...problem solved...

Sorry for going off topic here (well not entirely). Journey from 10.13.4 beta to a warm fire place with a good bowl of soup took 5.5 hours of solid "escape room" type hamster wheeling......learned quite a bit but what a pain in the keister

Welcome to the beta team. We test, break, try out and talk about it. Its about the fun.

 

[LarryJoe33]

Well, with every mistake there is a lesson rewarded. I got off the Beta downgraded to "street" 10.13.3. I re-installed Displaylink 4.1 and waited with anticipation while I re-booted my "Death Star" FAIL!. all 3 screens were now dark. I yanked the Diamond adapter which is connected to one of my 27inch screens which resulted in the other 2 screens showing my log-in screen. Once past the login the 2 screens were mirrored. I now plugged the 3rd screen adapter into the USB 3 and again all went dark. I knew that Displaylink 4.1 does not support Mirror mode on OS 13+. But WHY would the screen with the adapter cause not only for all 3 to switch to mirror mode But also instantly log me out.

Again searching on this forum I read that several people had the exact same problem. I was inclined to think it had something to do with my system profile settings but that should not be possible as I re-installed a fresh copy of 10.13.3 onto a formatted SDD?. Almost giving up having to cope with 1 less screen I swam the interwebs for 2-3 hours reading and was rewarded by finding a download of a command script named "Reset macOS display persistence" ran it and rebooted followed by several "tabbings" of Command F1 and BINGO...problem solved...

Sorry for going off topic here (well not entirely). Journey from 10.13.4 beta to a warm fire place with a good bowl of soup took 5.5 hours of solid "escape room" type hamster wheeling......learned quite a bit but what a pain in the keister

Nice to hear you got it resolved. Love that feeling of finding a solution!

 

[gregnoe]

My Preview app is have problem rendering jpg, png images, PDF renders fine, anybody having this problem ?

Yes I am having exactly the same prob. If I save as pdf, it's okay. Otherwise all images/photos are NOT rendered.
[doublepost=1517798837][/doublepost]

Anyone else finding 'dark mode' not working properly? Most of the icons in my menu bar are almost invisible including the Apple Menu icon. They're there but almost impossible to see. The drop down menus appear close to what they should be for some but not others such as Wifi which has the locks and fans greyed out. Turning off 'dark mode' returns the menu bar to normal. Here's what it looks like with dark mode on. View attachment 748823

I edited my original post regarding my Adobe Apps not working in this beta. Well, now they work!
Don't ask me why as I didn't do anything. By the way, this is an early 2011 macbook pro.

YES, exact same problem!

 

[Type4O]

Since installing this beta, I have not able to activate iMessage. I get an authentication error. It deactivated at some point.
Anyone else?
Thanks

 

[dorubrad]

Same exact issues for me, menu bar icons in dark mode are not visible (most of them) and:

<Name of App> may affect the performance of your Mac.
The developer of this app needs to update it to improve it's compatibility.

Just downloaded and installed 10.13.4 Public beta. It took approx 40 minutes.

When I logged in I got several warnings for my 32-bit apps. OfficeTime was the one app that I use a lot where the others could be easily replaced.

<Name of App> may affect the performance of your Mac.
The developer of this app needs to update it to improve it's compatibility.

I'm using Office 2016. Any Office 2011 users see a waring for Office 2011?

 

[wiffle]

10.13.4 broke Safari username/password autofill for me. Sites that would be able to previously autofill no longer do so. Have to click and choose the individual passwords to get in now.

 

[edamet]

I also had this with quick look. I did an Onyx full job on my iMac and after the quick look worked OK again, but the Preview app still wouldn't open them. The photos app also renders all new imports as just red images. I daren't click on thumbnails of older images in case it black-holes them too. What an abysmal set of bugs to release.

Exactly the same problems with the Preview and the Photos here.
iMac 27" mid 2011

 

[Atlantean]

I am having this as well, looks fine in quicklook, but is scrambled in preview....

View attachment 749538
Image above is what it looks like in Preview app.
View attachment 749539
mage above is what it looks like in Quicklook.
View attachment 749540


mage above is what it looks like in Quicktime 7 app.

I'm having the same issue along with Preview and Photos displaying the enlarged image as a red rectangle! The images are stored in iCloud and I can view them perfectly on my iPad and iPhone so I know it's not the image that's corrupt!

 

[jdclifford]

noticed that too; i selected the default (wikipedia) and seems fine. but seems like a mistake...

Apple fixed it the other day. I submitted feedback when I noticed the problem and Apple emailed me on Fri. I tested it and it works fine now in both Max OS and IOS.

 

[fisherking]

Apple fixed it the other day. I submitted feedback when I noticed the problem and Apple emailed me on Fri. I tested it and it works fine now in both Max OS and IOS.

yep! [URL="https://forums.macrumors.com/threads/wtf-happened-to-dictionaries-in-10-13-4.2103608/#post-25778119"]wtf happened to dictionaries in 10.13.4?[/URL]

 

[tywebb13]

My Preview app is have problem rendering jpg, png images, PDF renders fine, anybody having this problem ?

Yeah. The same happens to screen snapshots in 10.13.4 beta 1. The default filetype is png.

Use Shift-Command-4 to make a screen snapshot.


Result is a garbled png file.


To render correctly in preview change the screen snapshot filetype in terminal like this:


defaults write com.apple.screencapture type PDF;killall SystemUIServer


Now Shift-Command-4 will make a pdf screen snapshot instead and this time will render correctly in preview.

 

[fisherking]

Yeah. The same happens to screen snapshots in 10.13.4 beta 1. The default filetype is png.

Use Shift-Command-4 to make a screen snapshot.


Result is a garbled png file.


To render correctly in preview change the screen snapshot filetype in terminal like this:


defaults write com.apple.screencapture type PDF;killall SystemUIServer


Now Shift-Command-4 will make a pdf screen snapshot instead and this time will render correctly in preview.

not having this problem here... (i use screenshots regularly);preview & photos are both working as well...

 

[Atlantean]

not having this problem here... (i use screenshots regularly);preview & photos are both working as well...

I wonder if this bug is picking on certain machines with different graphics cards? It is affecting mine!

Mine is a MacBook Pro 17-inch, Late 2011 — Graphics: AMD Radeon HD 6770M 1024 MB Intel HD Graphics 3000 512 MB

 

[Banglazed]

beta 2 is out

 

[Atlantean]

beta 2 is out

I just installed 17E150f — still the same problems with the images in Preview and Photos!

 

[hsotnicam8002]

I just installed 17E150f — still the same problems with the images in Preview and Photos!

Same problems with images remain for me too.

 

[gwang73]

Does anyone with 10.13.4 b2 access the Mac App Store via the App? All I get is a blank App Store page with "Cannot Connect to the Store", "An internet connection is required" and I do have internet access.

I can't sign in/out either. But I can manually check for updates via Terminal and that works fine.

 

[friednoodles]

10.13.4 broke Safari username/password autofill for me. Sites that would be able to previously autofill no longer do so. Have to click and choose the individual passwords to get in now.

FYI, this isn't a bug, it's a deliberate change. You now have to interact with the browser's interface to cause an autofill. It was introduced into Safari Technology Preview 48. The reason? Autofill is being exploited to steal information, of all kinds:

https://freedom-to-tinker.com/2017/...-web-trackers-exploit-browser-login-managers/

A less crude defense is to require user interaction before autofilling login forms. Browser vendors have been reluctant to do this because of the usability overhead, but given the evidence of autofill abuse in the wild, this overhead might be justifiable.​

And that's what they've decided to do. So until browser makers can come up with a better solution to prevent this stuff happening (it's sadly not as simple as "don't let sites read the value of autofilled fields"), they're requiring that users interact with the browser's interface in some way (not just the field, e.g. clicking) before autofilling occurs, to prevent a script faking an interaction with a field, causing it to autofill and then stealing the value out of it, etc.

 

[hsotnicam8002]

I wonder if this bug is picking on certain machines with different graphics cards? It is affecting mine!

Mine is a MacBook Pro 17-inch, Late 2011 — Graphics: AMD Radeon HD 6770M 1024 MB Intel HD Graphics 3000 512 MB

Problem is the same for me with:

Chipset Model: AMD Radeon HD 6970M
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Dynamic, Max): 2048 MB
Vendor: AMD (0x1002)
Device ID: 0x6720
Revision ID: 0x0000
ROM Revision: 113-C2960K-205
VBIOS Version: 113-C29609-103
EFI Driver Version: 01.00.577

My card was recently replaced by Apple under a replacement scheme.