Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not Changing Desktop Names #102

Open
Sciccorz opened this issue Aug 26, 2024 · 14 comments
Open

Not Changing Desktop Names #102

Sciccorz opened this issue Aug 26, 2024 · 14 comments

Comments

@Sciccorz
Copy link

Sciccorz commented Aug 26, 2024

Describe the bug
A clear and concise description of what the bug is.

SImply has not changed the desktop names at all

Versions

  1. MySIMBL version - idk if i have it or how to check, but i have latest macforge update: 1.2.2
  2. Spaces Renamer version - 1.11.1
  3. MacOS version - 14.6.1

Command Outputs
Please paste the output of running these commands in Terminal:

  • ps aux | grep -v grep | grep -i macforge
  • sciccorz 1775 0.7 6.2 414743040 1045568 ?? S 6:44PM 0:14.83 /Applications/MacForge.app/Contents/MacOS/MacForge
    sciccorz 1782 0.0 0.2 411510512 32352 ?? S 6:44PM 0:00.20 /Applications/MacForge.app/Contents/Library/LoginItems/MacForgeHelper.app/Contents/MacOS/MacForgeHelper
  • ps aux | grep -v grep | grep -i spacesrenamer
  • sciccorz 1565 0.0 0.3 35525068 46912 ?? S 6:34PM 0:02.35 /Applications/SpacesRenamer.app/Contents/MacOS/SpacesRenamer
  • csrutil status
  • System Integrity Protection status: disabled.
@dado3212
Copy link
Owner

If you try the older builds from https://github.com/dado3212/spaces-renamer/releases (specifically the spaces-renamer bundle for v1.10.1 and v1.11.0) do either work?

@Sciccorz
Copy link
Author

still no change

@dantab66
Copy link

Sciccorz, have you tried the Terminal command "pkill -9 Dock" after you restart?

I need to do this every time I restart my Macbook M3 in order for the names to get set. Not sure why this is happening but it takes me a few seconds each time I reboot.

@Sciccorz
Copy link
Author

Yep, do it every time after I restart

@SeikaYuki
Copy link

Same things happened in M1 Sonoma 14.4.1. With MacForge 1.2.2(3), SpacesRenamer, and the bundle(1.11.1). After the Renamer has moved itself into the Application folder, it added itself automatically to the login items. The SIP and Library validation is closed. Here may be some question about the bundle as the MacEnhance folder has a different path as described in the readme file. However I still try to copy the bundle to the \Users\Shared\macenhance file and try to run it by clicking or dragging it into the Macforge interface. I notice that the bundle maybe working, but not as designed. Finally, after run the "killall -9 Dock", and try to give new names in the renamed, but nothing changed after the Update Name choice is selected. Is there any problems with the bundle running method? Thanks for any advice available :)

@tacomania
Copy link

Same problem - everything seemed to install correctly, the icon is visible, but when I rename and click the button, there is no change. I'm in the newest Sequoia 15.1, but this happened in my last few versions as well. Every year or so I try all over again and the same outcome. I feel like it must be user error but I don't know what I'm doing wrong.

@dantab66
Copy link

I've been using spaces-renamer for quite some time successfully. Ever since my Mac upgraded to Sequoia changing the names of desktops has doesn't work. Exact same symptoms that tacomania posted above. Is there a compatibility issue with Sequoia? (I am also on the latest version 15.1)

@localjo
Copy link

localjo commented Nov 15, 2024

Same issue with Sequoia 15.1, MacForge 1.2.2, spaces-renamer.bundle (1.11.1)

@dado3212
Copy link
Owner

Which MacForge 1.2.2 bundle do people have? It needs to explicitly be 1.2.2 (3). I'm on Sequoia 15.1 and it's working correctly.

This was a problem that was reported where MacForge was "updating" itself to a downgrade. See https://github.com/dado3212/spaces-renamer?tab=readme-ov-file#debugging-common-issues for how to resolve it, by fully uninstalling MacForge, running purge.sh, restarting, and reinstalling.

@dantab66
Copy link

Here's a screen shot of my MacForge. I am on an M3 chip that was working prior to upgrading to Sequoia.
Are you saying that event hough it says I am on 1.2.2. (3), I should still go through the uninstall/reinstall process?

Screenshot 2024-11-19 at 8 15 41 AM

@localjo
Copy link

localjo commented Nov 30, 2024

I'm on 1.2.2 (3) as well. Just went through the whole process again, and it worked! I managed to rename my spaces! But then I restarted and it stopped working again. I checked and MacForge is still on 1.2.2 (3), it didn't update, so I don't know what the problem might be.

@dado3212
Copy link
Owner

dado3212 commented Dec 8, 2024

After a restart you have to do pkill -9 Dock, let me figure out a way to automate that.

@dantab66
Copy link

@dado3212...I am happy to report that after doing a full uninstall again and reinstalling it worked on my M3, Sequoia 15.1.1 macbook pro. I still need to do a killall -9 Dock each reboot and would be great to figure out how to automate that on startup each time! Thanks Alex!

@dantab66
Copy link

@dado3212, I found a simple way to automate the killall -9 Dock and sharing in case anyone wants to do the same. (I am on Sequoia 15.1.1)

Using the Automator utility app on the Mac, I created an application (not a workflow) called “LaunchSpacesRenamer”that:
Step 1: Launches the spacesrenamer app
Step 2: Runs the shell script "killall -9 Dock".

Here is a screenshot:
Screenshot 2024-12-13 at 7 31 40 AM

Then in Login Items in System Preferences:

  1. Remove “spacesrenamer” (gets replace with my app)
  2. Add the app “LauchSpacesRenamer”.
    Now reboot and you should see it work.

NOTE: The reason I didn’t just create an automator app that only runs the killall -9 Dock, is that in MacOS Sequoia you cannot set the launch order of Login Items in the system preferences. I.e. It is possible that my "killall -9 Dock" Automator app might run too early in the login process before spacesrenamer launches. So the solution was to create a script that launches spacesnamer, and then runs the killall command to ensure that things run in order and spacesrenamer is already loaded.

Hope this is helpful and works for anyone else who tries it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants