I apologize if this has been covered elsewhere; I’ve searched the forums and haven’t found this exact problem yet.
I’ve got Luban 3.12.3 downloaded on a new iMac (purchased about a year ago), which is running Mac OS Catalina 10.15.7. When I try to start Luban, it does not appear in the dock and never displays any screens. It does, however, show up in Activity Monitor. It seems like it’s hanging at some point during bootup. According to Activity Monitor, it encounters nearly 200 faults in a brief period then just sits there. The only way to shut it down is to force quit from Activity Monitor.
I’d tried this a while back with a previous version (3.9.3, I think? I’m honestly not sure) and I was getting the same result. I’ve been slicing with Cura but I’d like to get going with Luban now that my A350 is up and running.
I’ve tried rebooting, uninstalling and reinstalling, and nothing seems to change. Any advice would be greatly appreciated. If it helps, I can pull more details from Activity Monitor as well.
It sounds like a corrupted preference file. This is what worked for me.
Quit luban.
Do a search (finder window, not spotlight) for luban. Click on the “+” in the upper right of window and turn on the option for “include system files”. There’s a folder called “snapmaker-luban” Delete the two “cookies” files and empty the “cache” folder. Empty trash. Then restart.
The one warning is that any time you mess with a preference folder it might wipe out settings. So if you have any saved you might want to take screenshots and/or export them. (this is good general practice anyway).
Let me know if this works for you.
Otherwise you can also do searches for luban and snapmaker and delete everything you find. Then restart and do a clean install but then you’ll definitely lose any settings you’ve saved.
-S
I got rid of all Luban files (preferences and everything), emptied the trash, and restarted. I installed 3.13.0 but unfortunately, it seems like I’m still hitting the same problem. It shows up in Activity Monitor but nowhere else and just sits.
Don’t know what else to suggest.
Try the same thing with 3.12.3 maybe.
Could also try opening and holding down control or option.
Sometimes that forces programs to start in their default mode.
I’m still running 10.15.6
-S
Tried control and option with both versions, unfortunately no luck. Still just hangs.
Thanks so much for taking the time to help, though. If nothing else I’ll keep checking on upcoming versions and do the whole clean install bit on each one.
I’m using Luban on Mac OSX Catalina as well on two Apple devices. I did ran into an issue of not showing settings on one machine. I’ve fixed that by doing the following:
Delete the application from the Applications folder
Delete the preference file that is located in your personal library (replace the [your login name]):
/Users/[your login name]/Library/Preferences/com.snapmaker.luban.plist
Delete (or copy for backup and then delete) the following directory (replace the [your login name]):
/Users/[your login name]/Library/Application Support/snapmaker-luban
That should give you a complete fresh start. Download the latest version and copy it to the Applications folder.
Hope that helps. If not you can also try to test if it’s an account issue. The best way to test that, is to create an extra test account on your mac, login with that account and see if the application is starting now.
Thank you guys so much for your suggestions. I tried a couple older versions (including 3.8) but I kept running into the same problem. I’d tried completely ridding my system of all the preferences and such associated with Luban and doing fresh installs a few times too. I had two other accounts on my computer which I also tried to no avail, but then I finally bit the bullet and created a new test account.
That did it! And here’s the kicker – not only did Luban boot on the test account, it then started up without a hitch on my original user account once I’d launched it on the test account. So apparently there was something deep down in my user settings that was preventing that initial boot. Once it got past that it was okay.
In the interest of completeness, I did try bypassing Gatekeeper temporarily just in case this was an “unidentified developer” situation. I guess I didn’t really think it was, otherwise I’d be hearing from a lot of other people with the same issue. These were the instructions that I followed:
However, as noted, that didn’t actually fix anything on my end.
I wish I had a better idea of what exactly in my system was preventing the launch, but for the time being, if anyone down the road is reading this, creating a new test account and running the app on that account was what worked for me. Thanks again, @MarkG, for that tip!!
You folks completely rock.
Dan
P.S. If I somehow can determine what was causing the issue in my user settings, I’ll come back and post it here as well.
P.P.S. Probably the wrong place to post this, but I was simultaneously trying to get Simplify3D running on my system (long story). I was getting the EXACT SAME behavior with the installer for S3D, and this fix took care of that as well.