“smb big sur”

I just upgraded my Mac Book Pro to Big Sur. After installing, I tried to login and it showed a loading bar (normal). However, someone in the loading bar, the screen goes black and then a new screen appears and says, “the computer restarted because of a problem. Press a key or wait a couple seconds for the computer to restart”. I have tried going into safe mode, recovery mode, Diagnostics, literally you name it, and I just cannot get anything to work. Please help

On a Big Sur host bound to Active Directory, I am seeing some hosts with an empty /Library/Preferences/OpenDirectory/DynamicData directory. Output of dsconfigad -show seems to be good and consistent with other hosts that have data inside the DynamicData directory. The directory at /Library/Preferences/OpenDirectory/Configurations is never empty for any host and data looks okay. I am not able to reproduce this on a local Big Sur host I have that is also bound to Active Directory using Directory Utility. My question is: Are there scenarios in which the DynamicData directory would be empty?

My app display an icon on the menu bar, and the icon source file is white. I want the icon color to follow the menu bar background color, so I set the template property of NSImageview.image to YES, like this: NSImageView *logo = [[NSImageView alloc] init]; logo.image = [[NSBundle mainBundle]; imageForResource:@LOGO_16_white]; [logo.image setTemplate:YES]; In most Big Sur and below macOS11, the icon color changes with the menu bar background color, If the menu bar has a light background, the icon color is black, If the menu bar has a dark background, the icon color is white. But on a few MacBooks, the icon color is always gray and does not change. So is this a bug of Big Sur? What should I do ? Thanks!

Is there a trick to successfully installing macOS Big Sur on an ext. drive and the drive not getting corrupted when switching back to Catalina on the internal drive? I understand the issue (64411484), about being on the same APFS container, but don't the internal and external drives each have their own container? Everything is fine until I try to switch over to Catalina, either on a T2 Mac or a non-T2 Mac. Then the entire Big Sur volume is corrupted. Are there more explicit install instructions available from Apple given the known bugs? I would really like to be able to have a stable setup that isn't corrupted each time I need to switch back to Catalina. Any tips or suggestions are appreciated.

I'm not asking anything, I just wanted to share my feedback, as I'm sure there's a lot of people struggling with this same thing. As a UI designer, I find very difficult to adapt to this new positioning of back button in Finder on Big Sur. Since it has always been under exit button and after years of using it, I keep clicking on that place and I end up closing my Finder every time, because back button is moved towards the middle now. Moving a button is not a terrible thing, but it is kinda upsetting if it involves a chance to accidentally close something.

Big Sur 8 automatically started to update this am. update got as far as progress bar on full then 5 hours and no progress. rebooted in safe mode. what can I do?

I trie to download lates beta of macOS Big Sur. But loading never stops. It reaches 9.56 GB of 9.56 GB but sill shows loading - for 12 hours now. Anyone knows what problem this is and how to slove it?

I have an app that is working correctly on macOS Catalina but in Big Sur it doesn't have access to iCloud. CKContainer containerWithIdentifier:accountStatusWithCompletionHandler: returns CKAccountStatusNoAccount and [[NSFileManager defaultManager] ubiquityIdentityToken] returns nil In System Preferences it is not even listed in the apps that use iCloud. Signing & Capabilities is properly configured and is working on macOS Catalina. On the computer with Big Sur I have verified that I have iCloud on and I have exchanged files through iCloud Drive with my iPhone. The only peculiarity of the app is that it is a Mac Catalyst app. Something similar is happening to someone? Anyone know how I could solve it? Thanks!

Hi Team, After upgrading my Mac OS to Big Sur version 11.4. IOS simulator is crashing. I have tried this with Xcode version 12.2 and 11.7 but the results are same. This started happening since the Big Sur update. Attached the crash log for your reference. Crash logs

Big Sur refuses to download. Why do these devs even have a job..... I have updated all my Adobe apps, made sure my Canon drivers are up to date, everything. I, like MANY MANY OTHERS the devs seem to enjoy ignoring, cannot download the Big Sur update. Hit the button Error So this $2,300+ machine is now essentially a web browsing tool until Apple decides to fix their own damn product. I cannot access any 3rd party apps (thousands of dollars right there alone) and cannot operate BASIC ADOBE FUNTIONS. This is outright absurd. You want to play a big game with a new update? Make sure your freaking servers can handle it. People have work to do, unlike the Mac devs apparently. Carefully looking into switching away from Apple, this is completely unacceptable for people who have work to do on their apple computers.

Can any one send me the macOS 11.0 Big Sur setup ?

I installed Big Sur, but my MacbookPro won't start up today. My MacbookPro has no space to install it again. Currently MacbookPro can't start and it seems black screen. How do I start the initialization? Or how can I fix this problem?

I am trying to mark-up a document in finder and since this update ( Big Sur 11.4) its asking me for my password but won't accept the password I put in. I have tried what others have written on here to no avail. Help Please!

Anyone had issues with running scripts on Big Sur? I get a command not found error and I’m guessing its a toggle or a command or a back age that needs to be added to enable it or its blocked by default for security reasons?

Since I switched to Big Sur I am unable to use the search function on Mail and, subsequent to a recent update, I have now lost the 'All Mailboxes' option and mail seems confused. It also seems that attachments are being stripped from incoming emails. HELP!