Category: Uncategorised

Benjamin,

I share Ignatius’s perspective on this matter. Given that file renaming has been activated, it suggests that a drag action is being misinterpreted as a simple click.

This could potentially stem from an unreliable Bluetooth device that is experiencing intermittent connectivity issues. Additionally, the fact that Quick Look is opening sporadically indicates the possibility of unintended inputs being generated, whether from a keyboard, another device, or even from the main pointing device, which may have custom buttons programmed.

Unfortunately, we currently lack information on the specific type of main pointing device in use, adding a layer of uncertainty to the situation. It might be beneficial to investigate the settings of the Bluetooth device in question and check if there are any customization options on the main pointing device that could be adjusted to prevent these stray inputs.

Monitoring the behavior of the devices could provide further insight into what is causing this issue. Overall, there seems to be a combination of factors at play, and a thorough examination of both the hardware and software settings might help in resolving these unusual occurrences.

It seems that a potential solution didn’t work for you as expected. I’m using Safari version 18.4 with Sequoia version 15.4, and it’s functioning properly on my end. One suggestion would be to clear Safari’s cache. You can do this by navigating to the Develop menu or by manually deleting the cache files located at ~/Library/Containers/com.apple.Safari/Data/Library/Caches.

Have you identified the source of the issue yet? I suspect it might be related to an extension, but despite disabling all of them and rebooting my device, I’m still experiencing the problem of Safari opening a blank private window. As a temporary fix, I’ve created a BetterTouchTool (BTT) action that copies the URL, opens a new private window, pastes the URL, and hits enter. It appears you are experiencing similar challenges.

You mentioned having an AdGuard application, but disabling it didn’t resolve the issue, which aligns with the experience of others facing this problem. I’m curious to know which extensions you are currently using. Is it AdGuard or perhaps Wipr? If there’s a common extension among users with this issue, it could potentially be the root of the problem.

Like you, I’ve also encountered the same blank private window issue. Could you share more details about the workaround you’ve implemented? As of now, I’m still relying on my BTT action as a temporary fix to navigate around this bug.

The Royal National Institute of Blind People in the UK has developed synthetic voices in Welsh. However, these voices are currently only available for Windows systems. This situation raises a couple of questions regarding the potential for third-party developers to offer additional language options for macOS.

Although Welsh may not be a high priority for Apple, the fact that a synthetic voice already exists prompts some curiosity. Specifically, how challenging would it be to adapt this Welsh voice for macOS? Additionally, does Apple allow third-party developers to integrate additional languages into their operating system?

Even though I am not visually impaired, there are occasions when having Welsh text read aloud would be incredibly helpful for me. The ability to hear the language spoken could significantly aid in comprehension and engagement. Furthermore, I would also appreciate access to Welsh translation services alongside the voice functionality.

This inquiry is not limited to Welsh; it extends to any languages that currently lack support but have synthetic voices available. There is a clear need for greater accessibility and inclusiveness in language options across different platforms, especially for those of us who wish to engage more deeply with diverse languages without being visually impaired. It would be beneficial to see the development of such features, allowing for a richer experience in understanding various languages.

The new local network access layer in macOS Sequoia has become quite frustrating for users. The inability to reset permissions or remove applications is a significant drawback. Even after granting an app access to the local network, it often ceases to function correctly after a reboot or some time has passed. On my iMac with macOS 15.2, I have found a few temporary solutions: disabling and then re-enabling the Ethernet adapter, logging out and back in, or disabling local network access and re-enabling it.

However, these fixes are cumbersome and do not offer a long-term solution. I primarily use Microsoft Edge as my browser. Recently, after an internal update, I was prompted to grant Edge local network access again. This situation led to the appearance of two distinct entries for Edge in the local network access permissions, both pointing to /Applications/Microsoft Edge when viewed in Finder.

To make matters worse, even after completely uninstalling Edge from my Mac, one entry for the browser remained in the permissions list. This glitch is incredibly frustrating and highlights significant bugs in the system. It seems perplexing why Apple would implement such restrictive access layers that hinder user experience. Many users are left wondering why they are being penalized with a complicated and error-prone system instead of being given a straightforward way to manage local network access.

The overall experience with this new layer is disappointing and in need of urgent improvement.

If you have a 2012 iMac and need to reinstall the operating system, I recommend using Internet Recovery. To access this, hold down Command + Option + R while booting up your iMac. This will enable you to reinstall macOS from Apple’s servers.

If you’re not sure how to initiate Internet Recovery, please don’t hesitate to ask for assistance. It’s important to note that you cannot use the standard recovery mode for erasing the internal drive. To perform this function, you must utilize Internet Recovery or boot from an external drive or USB flash drive.

Once you’ve booted into Internet Recovery and the utilities have loaded, follow these steps: open Disk Utility, and ensure that you select “Show All Devices” from the view menu, if available. You’ll see your internal drive listed at the top; this is the drive that needs to be erased. After erasing it, exit Disk Utility and proceed to open the installer.

According to Everymac.com, the most recent compatible macOS version for your iMac is macOS 10.15, known as Catalina. I recommend installing Catalina rather than High Sierra for better stability and performance. If you’re planning to sell your iMac, it’s wise to complete the OS installation up to the initial setup screen where you select your language.

At that point, you can exit the installer. If you face any difficulties quitting, simply press and hold the power button on the back of the iMac until the screen turns dark and the device shuts off. Your iMac will be prepared for its next owner after this.

Good luck!

Your question about responsiveness highlights an interesting debate surrounding perceived speed versus actual performance. I understand that you don’t use Geekbench for real-world tasks, so let’s delve into what is considered “responsive” or unresponsive on Intel systems.

Many users commonly describe their experience as “snappy,” but this term lacks clear definition. Often, it seems to stem from a psychological perspective, as users may convince themselves that their new hardware justifies the expense, rather than relying on concrete performance metrics.

While I do find my Mac to have its slow moments—like Swift Playgrounds, which I attribute to Catalyst technology rather than the Xeon processor—other elements are less about hardware and more about the overall ecosystem. For example, I experience longer sleep and wake cycles on my current system compared to my old machine, taking about 31 seconds for sleep.

This isn’t necessarily a reflection of the processor, but rather the operating system and the number of connected peripherals. While I acknowledge the limitations of synthetic benchmarks, it’s clear that the M1 Pro outperforms my 5,1 model in these tests.

More importantly, it consistently proves faster in real-world applications, resulting in a more responsive feeling overall. My older system, while capable, often falls short in tasks when compared to the M1’s processing power.

For instance, as I type this, my M1 is encoding video in Handbrake seamlessly while utilizing minimal CPU resources. The difference is staggering, especially when considering how much more gradually the older system would respond under similar workloads.

Boot times and software updates also favor the newer models, making them feel significantly faster and more efficient compared to the 5,1. Even if your 7,1 system holds up for now, any future replacement is likely to deliver a distinctly snappier experience.

I recently acquired a used Mac Pro from late 2013 (MacPro 6,1), and so far, the machine seems to be in excellent cosmetic condition. All internal hardware appears to be functioning well, except for a peculiar issue with the port lights located on the rear panel.

When I power on the machine, the lights flicker on briefly; however, they do not illuminate if I move or turn the system. This has raised concerns about a possible fault with the internal accelerometer sensor.

Despite my worries, the overall condition of the Mac Pro suggests that it hasn’t endured significant physical abuse by the previous owner. I’ve also noted that the seller utilized OpenCore Legacy Patcher to install macOS Sequoia on the device, which raises the possibility that this problem could be software-related.

Unfortunately, I have not been able to find any information online regarding troubleshooting the port lights issue. Furthermore, the seller claimed that the machine has all stock components and has never undergone any servicing.

As I no longer have contact with them for additional insights or support, I’m reaching out for guidance. If anyone has encountered a similar issue or has experience troubleshooting this type of problem, I would greatly appreciate any helpful steps or suggestions.

Understanding whether this is primarily a software conflict, an accelerometer sensor issue, or something else entirely would be invaluable in addressing this concern. Thank you in advance for any assistance you can provide.

I’ve noticed that this Mac Mini forum is currently filled with discussions about the new M4 model, and understandably so, as it has generated a lot of excitement. However, I want to shift the focus back to the 2012 Mac Mini, which I own and have made some upgrades to, specifically an SSD and an increase to 8GB of RAM. This machine continues to run smoothly on Mac OS 10.15 with a web browser that remains supported.

I’m curious if anyone in the forum has experience with the same 2012 Mac Mini model regarding the installation of newer operating systems like Big Sur using OpenCore Legacy Patcher. I would like to know how it performs if anyone has taken that route. Additionally, I’m also interested in the performance of OS Sequoia when using OCLPatcher on the same hardware.

I appreciate any insights or experiences shared by other users who have experimented with these updates. It’s great to see how older models can still be relevant with the right software tweaks, but I want to ensure that those of us with the 2012 model can continue to have a solid user experience. Thank you in advance for your input.

Hey everyone! I have a quick question for you — how is your MacBook Air M2 performing? I’ve had mine since March, and it has been running flawlessly without any problems so far.

However, I recently stumbled upon a discussion about the “sleep bug” on Reddit, and it got me a bit anxious. I feel like I might be letting myself get a little worried, even though my device is functioning perfectly at the moment. Should I genuinely be concerned about this issue, or is it just my mind going into “panic mode”?

It’s easy to get caught up in online discussions and worry about potential problems, especially when everything has been going so smoothly. If anyone has had experience with this “sleep bug” or has any insights, I’d love to hear your thoughts. It’s always reassuring to know that I’m not alone in this, and other users might have faced similar concerns.

Thank you for sharing your experiences, and let’s discuss how our MacBooks are holding up!

I have a Superdrive that functions well with my 2019 Intel MacBook Pro, which I am planning to sell. However, it fails to operate with the new M3 MacBook Pro that I have acquired.

I have been connecting the Superdrive directly to both computers, avoiding hubs, by using a third-party USB-A to USB-C adapter. Despite trying multiple Thunderbolt ports on the M3 MacBook, the drive does not respond—it makes no noise and does not accept a disk when I attempt to insert one.

Both MacBooks recently received updates to macOS 15.5, which leads me to question whether the issue stems from a hardware limitation with the Superdrive and the M3 MacBook. It’s unclear if the problem is with the Superdrive itself or if there are compatibility issues with the M3 model.

If this is strictly a hardware limitation, then the Superdrive may not work with the newer MacBook, and I might need to consider alternative solutions for my disc reading and writing needs. I would appreciate any insights into whether this issue can be resolved or if it is a permanent incompatibility.