I'm a developer. My code is working as expected on Google Chrome and Firefox. But I tried it on Safari and it's a disaster. I would like to know what's wrong, what is different in those cases, and if I should report bugs. My coding objective is to select options in the list. This will automatically select options for the two others in the list. One can be edited, not the second one. This is fine on Chrome and Firefox, as I said. On mobile (iOS 18.5, iPhone 16e): - The list that can be edited is well auto-selected, not the second one - The second one can be edited (even if it should not) I enabled dev mode, but it doesn't seem to change anything. On my Mac Mini (macOS 15.5): - The list that can be edited is well auto-selected, not the second one - Cannot edit the second list, so it's fine - I change the code of a JS file, refresh page -> no change. I go to Chrome, refresh -> see changes. Is there a specific refresh needed?

I just updated my Mojave machine to Security Update 2020-006 but my bridgeOS has not updated, it remains on 18P50347c which I got when I tried Big Sur DP4/PB1 on 7 August 2020? I don't have any other Macs so "downgrading (from beta to release) bridgeOS using Apple Configurator 2" isn't an option. How can I get the latest bridgeOS on my Mojave Mac mini?

I've downloaded the correct file from Samsung but the file is not recognized and the open command is unavailable. Can't install it on this new Mini, but my old Mini (late 2014) can still print to that device. Can I somehow get the driver file from the old Mini and use it on the new one? Any other ideas?

I am trying to pair my Bluetooth keyboard with a Mac Mini. The Bluetooth preference window shows the keyboard as "discoverable" however, when I try to pair, the keys don't seem to register when I try to type the pairing code. I tried it on my MacBook as well, and it doesn't work. However, on my girlfriend’s MacBook it does work. It seems to be an OS issue, as I am running macOS Monterey on the Mac mini and my MacBook, and she is running macOS Catalina. I don't really want to downgrade my OS. Are there any solutions that might work?

This machine (mid-2011 with macOS Big Sur retrofit) is used as a HTPC/media player in a somewhat interference-rich environment. As long as there is some kind of media playback active, even if it is video with a silent audio track, all is fine. However, a few seconds after no longer playing back anything, it appears the sound circuitry powers down leaving the output in a somewhat high-impedance state, leading to all kinds of noise being picked up by the analog wiring (ticking noises that appear to be from some SMPS in the system if not using an audio isolation transformer, hum injected into the same transformer if using one). Is there some hidden software option to simply keep the sound circuitry on line (actively outputting silence) at all times?

When I just started using my M4 Mac mini, I was using a cheap Chinese display from Taobao with the brand name "YSNO". This display lied that it was a HiDPI display to the Mac, causing all text and on-screen elements to be giant, but still crisp and sharp. The problem this causes is that everything is humungous. The problem can be solved in the normal macOS by manually setting the resolution to a non-HiDPI one, but for some reason, the boot menu remembered the YSNO display's incorrect configuration and I can't find a way to make it forget it. When I try to open Apple Diagnostics by holding down the power button to access the boot picker, then holding down Command+D, the list of languages has a huge font size (displayed with crisp, but unwanted HiDPI) and extends past the bottom of the screen, and I can't reach the "continue" button. The text is also cut off. This problem persists on my old Samsung monitor (I stopped using the YSNO monitor), which does not show incorrect configuration. I tried running sudo nvram -c to clear the NVRAM, and I also tried running sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool NO to force disable HiDPI. None of these commands disabled the HiDPI in the boot picker and the Diagnostics mode. Is there any way I can reset the screen resolution/HiDPI setting to the display default in the boot picker and Diagnostics mode? My macOS HiDPI is already off. The only thing that bothers me are these modes. Even the Apple logo and progress bar the computer shows when it is booting is giant, as if my monitor was a HiDPI display.

I backed up my old mac mini (2011) using Time machine to a NAS over SMB. Now I'd like to restore the mini from the backup, however the SMB mount is not accessible from the Recovery mode (at least on OS X Lion, as also referenced on https://apple.stackexchange.com/questions/122389/mounting-smb-network-share-from-mavericks-recovery-mode?rq=1) and I cannot easily reconfigure the NAS share to use AFP. Nevertheless, I can login into the NAS using SSH and I can see the files:

nas% ls /mnt/uloziste/macbackup/mini/vladak/
.apdisk                           .DS_Store                         Vladimir’s Mac mini.sparsebundle/ 
nas% ls /mnt/uloziste/macbackup/mini/vladak/Vladimir’s\ Mac\ mini.sparsebundle/
bands						com.apple.TimeMachine.Results.plist		Info.plist
com.apple.TimeMachine.MachineID.bckup		com.apple.TimeMachine.SnapshotHistory.plist	token
com.apple.TimeMachine.MachineID.plist		Info.bckup

How do I transfer these files to a USB drive (formatted as Mac OS Extended) so that the Recovery mode will recognize it as a Time machine drive and will be able to recover from it ?

I'm setting up an old mac mini (specs below) with a dual boot (Ubuntu) and I've run into an issue getting to the Apple boot manager or the EFI boot manager. Essentially the monitor does not activate for either boot manager, however, if I wait or hit return straight away OSX loads, if I hit right and then return Ubuntu loads. So the boot manager is there but the screen simply isn't coming on yet. As soon as an os loads the monitor comes on and works just fine. The monitor is connected to the mac mini using a display port cable. The monitor works just fine on other computers with the same cable. I've tried a whole load of things: - reset PRAM or NVRAM and SMC - tried a different cable (display port adaptor to vga cable - so different port on the monitor) - did a fresh install of OSX (initially 10.6 and then updated to 10.8.5) - tried a different monitor (an old vga CRT) always the same. I'm now using the hdmi out of the mac mini (hdmi adaptor to dvi cable) and the monitor displays the boot manager as expected on boot up. So the problem seems to be either the display port on the mac mini (which doesn't make sense - it doesn't work and then it works once the os is loaded) or perhaps a display port driver (is the driver that specific?) incompatibility with the monitor (but it does the same with a different monitor) - neither really makes sense. Does the boot manager use its own drivers? Could they be corrupt (across fresh installs)? Is there something I'm missing here that I could try? -- Mac Mini mid 2010, 2.4Ghz Intel Core 2 Duo Nvidia GeForce 320m 256mb OSX 10.8.3

I have a Mac mini which has no display which I connect to it by sharing the screen to my laptop. The Mac mini runs apps which controls my live show's backing tracks, lights and video. The video projector is connected to the mini via HDMI. I would like the mini to still use the Built-in display as the primary, and the projector act like a second display so it can be used for the videos, but allow me to still see the Mini desktop and other apps via the screen share. However, when the projector is connected, the Mac automatically selects it as the primary display, and Built-in Display is gone. Is there a way around this?

I've been reading up around sleep settings as I keep finding my Late 2012 Mac Mini in a weird hung state each morning that requires a force-reboot (it's like running Windows 10 years ago!) I thought the "deep sleep" function was to blame but when I ran pmset-g I got this: System-wide power settings: Currently in use: standby 0 Sleep On Power Button 1 womp 1 autorestart 0 hibernatefile /var/vm/sleepimage powernap 0 networkoversleep 0 disksleep 10 sleep 60 autopoweroffdelay 14400 hibernatemode 0 autopoweroff 1 ttyskeepawake 1 displaysleep 10 standbydelay 4200 However https://apple.stackexchange.com/questions/113954/difference-between-autopoweroff-and-standby-in-pmset says: > With the release of the OS X Mountain Lion v10.8.2 supplemental update > 2.0, a new feature was introduced to enter safe sleep after four hours of the computer being connected to AC power. This is an effort to > comply with the European Energy Standards (ErP Lot6). **This will only > occur if there is no wireless or Ethernet activity and no activity > from external devices such as USB storage devices**. I have an external USB hard-drive as the 2nd drive on my SSD MacMini as my main data drive. If this is turned off, I recently noticed the system won't boot (folder with a question mark) which seems odd for an ancillary drive. Either way, would the presence of this drive prevent deep-sleep/hibernate/standby? - It will sleep a couple of hours fine, it's only overnight it has issues - It generally still has lights on my connected USB mini-hub when it is frozen - It typically "semi-wakes"; the screen recognises an active input and typically I get a black screen with a responsive mouse cursor I started writing a totally different question but then was thinking whether my USB drive might be a culprit here or I should be looking elsewhere? How can I tell if the Mac is is sleeping Vs standby Vs hibernate Vs deep-sleep to track down which transition or action is causing the problem?

I have an M1 Mac Mini running Sonoma 14.3. I would like to be able to put it to sleep or shut it down when not in use to conserve energy. But, I also want to be able to remotely power it up so I can access it when I need to using VNC, SMB, or SSH. I have typically done this by sending WOL (WakeOnLan) magic packets from my home router which is pfSense. This has always worked fine—until this Mini. I've checked the Energy Saver prefs, made sure womp=1 in pmset -g and even tried mucking around with nvram / darkwake settings. I'm sure the Ethernet MAC address is correct. Nothing has worked. WOL to an Intel NUC sitting on the same network works as expected. What happens when I send the WOL packet is one of: - absolutely nothing: no lights, no activity, screen remains dark. - power LED comes on, Mac becomes "pingable", screen stays dark, but after 5-10 seconds, the Mac goes back to sleep. At no point during this sequence am I able to connect via VNC. Is this a hardware bug with the M1's? Anyone know of a solution?

I just tried updating my Mac mini to some version of macOS. I thought the update was finished as my Mac showed nothing on my monitor. I shut down my Mac with the power button and when I started it back up it allowed me to log in, but after I put my password in and the loading bar appeared, my Mac screen is now blank where as before it would take me to my desktop. Looks like I maybe accidentally forced-shut it down during an update. Tried restarting it a couple of different times and it’s done the same thing. There isn’t any loading indicator to show whether or not it’s finishing up the update. Is it just finishing up the update now that I’ve logged back in after restarting and that’s why my desktop isn’t loading?

The Mac mini (2018) Macmini8,1 is running Linux with rEFInd. The mini has 2 usb-a 10 Gb/s ports, and 4 usb-c 10 Gb/s ports **Problem:** On usb-c ports, "dangerous" devices are not recognized by the kernel, they are ignored on plugin like nothing happened > "dangerous" devices include storage Samsung T5/T7 or networking > Realtek 8153 > > "safe" devices like mouse, keyboard and display works Everything works on usb-a ports uname --kernel-release 5.8.0-36-generic to run with T2: * applesmc brcmfmac blacklisted * tg3 so buggy it is not used * csrutil disable * Startup Security Utility: No Security, Allow booting from external or removable media **How can any type USB device be made to work on usb-c ports?** February 1, 2021: it is discovered that only devices that decide to use 480 Mb/s or slower work. No device selecting 5 or 10 Gb/s will appear in dmesg --human --follow February 5, 2021: The usb ports that are capped at 480 Mb/s are off the Thunderbolt controllers:

lspci -knns7e:0
7e:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
    Subsystem: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:0000]
    Kernel driver in use: xhci_hcd
    Kernel modules: xhci_pci
lspci -knns8:0
08:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
    Subsystem: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:0000]
    Kernel driver in use: xhci_hcd
    Kernel modules: xhci_pci    ​ 

I've set up a Mac Mini Pro via a monitor, mouse and keyboard. After I log in via the monitor I can access remotely via AnyDesk or Screen Sharing, but if I reboot its not logged in to an account so AnyDesk isn't running. Its connected via wifi only so I don't seem to be able to ping it after reboot. What options do I have to log into and boot the GUI without a monitor so I can run it via AnyDesk or OS X screen sharing? Its intended to be a portable machine so it may change locations and thus wifi networks.

I just switched from a Windows PC to a Mac Mini M4. When I open a few apps, I notice the GPU temperature gets to around 80-90 degrees Celsius (seems to me pretty high). I saw people recommend using a fan control app (used to do it from the BIOS in Windows), but I'm not sure how it works in a Mac, so kind of scared to ruin something. For example, I don't see in the Mac's Fan Control app an option to define a curve, just a single temperature. Also, how does it affect the fans? If there is some recommended setting, I would love to hear =)

I have an iPhone 13 mini running 16.3.1 I recently purchased a Mac Mini (Apple M2) updated to 13.2.1. I transferred from my iMac to Mac Mini and have been setting it up and transferred my operations to this as my primary computer. This is using a Bluetooth keyboard & mouse. I wanted to setup Continuity camera, but without much success so I took one step back to setup Bluetooth first. The Mac Mini sees the iPhone 13 in nearby devices. The iPhone 13 mini sees the Mac Mini in nearby devices. After many failed attempts I eventually got both to see the same code number and paired, although they show as Not connected. When I try to connect I get a message "Connection Unsuccessful the Mac Mini is not supported" and the only option is to "Forget Device". One potential complication - clicking on the ⓘ on the Mac Mini shows 16.3.0 for the iPhone. I have Handoff & Continuity Camera enabled on the iPhone. I can successfully AirDrop from the iPhone 13 to Mac Mini. Any idea what might be going on to hinder the pairing?

Can I pair a new Bluetooth keyboard or mouse when I try to log into Catalina, when no other input device is available? Here is my situation: I have a MacMini with Catalina installed. It works perfectly with the Bluetooth mouse and keyboard that I have in apartment A. Now, I moved to apartment B. I took the Mac but not the mouse and keyboard. Instead, I have two BT keyboards (Logitech MX keys and Magic Keyboard gen1, **without** Lightning port) and two BT mice (Logitech MX Master and Apple TrackPad). None of these four devices have ever been paired with the Mac. Therefore, they are not recognized at log in. I have neither a USB keyboard nor a USB mouse. Being quarantined in a country where online shopping is slow and unreliable, I cannot get any new device quickly. Any suggestion on how to log in would be greatly appreciated. Thanks is advance.

I have a 3 monitor setup that uses DisplayLink for the 3th screen. The 3th monitor disconnects 1-10 times a day. It seems like it is caused by a minor difference in power; when I plug in my phone charger next to the Mac / docking station power, the connection is lost. Most of the times, just bumping into my desk is enough to disconnect the monitor (even the act of just standing up does the trick). After disconnecting, the DisplayLink manager says: No DisplayLink-enabled display detected To reconnect it, I have to repeatedly unplug the DisplayLink docking station, and restart DisplayLink manager, until the monitor is detected again. Sometimes the monitor is detected immediately, sometimes it takes a while. I'm not quite sure whether this problem is caused by power fluctuations, bad connection, or missing/bad config. All I know is that I am looking for a way to solve this issue, every suggestion is welcome; - power hardware to prevent power fluctuations, - a better docking station, - a bash script that re-establishes the connection without the need to unplug hardware, My setup is: - Mac mini M1 2020 - Dell DisplayLink d3100 - 3x Dell S2721HN

Starting Google Drive gives a popup with this message: "Google Drive has encountered a macOS File Provider error. This might be resolved by restarting your computer. For best results, ensure your computer is running the latest version of macOS." Restarting the machine makes no difference and 12.7.6 is the latest available for my hardware (Mac mini (Late 2014)), yes it is 10 years old and I can't afford to buy a new one : ( No errors in system logs. I was having problems with Google Drive not reflecting changes that I had made on another machine so I uninstalled GD deleted the directories (which I now suspect was a mistake) restarted, installed GD again and got the error on starting it. Searching for the first sentence of the message got lots of hits but nothing useful and applicable to my situation. I ran First Aid on the hard disk which reported no errors in case there were filesystem problems that might cause the error. Is there anyway of getting some more diagnostics about what is actually wrong?

Is it possible to connect two Bluetooth headphones to a Mac so both users can listen and talk? Both should be able to hear audio and speak into the Mac.