Would it be possible for you to share a screenshot of the "Security & Privacy" pane?
Spacemouse driver not working in Ventura
Moderator: Moderators
Re: Spacemouse driver not working in Ventura
Re: Spacemouse driver not working in Ventura
Re: Spacemouse driver not working in Ventura
cjadams, what is the output of the following command (used to check the SIP status) when run in Terminal?
Code: Select all
csrutil status
Re: Spacemouse driver not working in Ventura
ngomes wrote: ↑Wed Jul 13, 2022 11:42 am cjadams, what is the output of the following command (used to check the SIP status) when run in Terminal?Code: Select all
csrutil status
Re: Spacemouse driver not working in Ventura
Thanks, cjadams. SIP is enabled, the driver installation succeeds but you never see the "allow" button in the "Security & Privacy" pane in System Preferences.
I'll have a word with my colleagues.
I'll have a word with my colleagues.
Re: Spacemouse driver not working in Ventura
incorrect... - sip enabled or disabled does't seem to matter..
i get 1 and only 1 "Allow".. not 2 which i think i remember getting before on earlier os's - one for the helper and one for something else 3dc..
'm guessing that only part of the 2 drivers are loading!
NOTE also a bug probably the uninstall program doesn't kill the 3dc helper process and therefore hangs on uninstall
i had to kill it in activity monitor before the uninstall process would finish.. just fyi
i get 1 and only 1 "Allow".. not 2 which i think i remember getting before on earlier os's - one for the helper and one for something else 3dc..
'm guessing that only part of the 2 drivers are loading!
NOTE also a bug probably the uninstall program doesn't kill the 3dc helper process and therefore hangs on uninstall
i had to kill it in activity monitor before the uninstall process would finish.. just fyi
Re: Spacemouse driver not working in Ventura
I also get this
Last login: Wed Jul 13 15:26:19 on console
cjadams@Phoenix ~ % csrutil status
System Integrity Protection status: disabled.
cjadams@Phoenix ~ % /Applications/3Dconnexion/3DconnexionHelper.app/Contents/MacOS/3DconnexionHelper
2022-07-13 15:34:11.571 3DconnexionHelper[1755:21757] Line -> * * 9D93Y2RD6L com.3dconnexion.dext (1.2.296/1.2.296) com.3dconnexion.dext [activated enabled], -> arr=(
"*",
"*",
9D93Y2RD6L,
"com.3dconnexion.dext (1.2.296/1.2.296)",
"com.3dconnexion.dext",
"[activated enabled]"
)
2022-07-13 15:34:11.571 3DconnexionHelper[1755:21757] VERSION: (
"",
"1.2.296",
"1.2.296",
""
), ver=1.2.296, short=1.2.296
2022-07-13 15:34:11.571 3DconnexionHelper[1755:21757] STATUS: [activated enabled]
2022-07-13 15:34:11.571 3DconnexionHelper[1755:21757] Error (DEXT): DEXT can't be installed !!!
2022-07-13 15:34:11.572 3DconnexionHelper[1755:21757] Error (DEXT): Please check status (systemextensionsctl) and permissions of DEXT ('Security & Privcay')!
2022-07-13 15:34:11.572 3DconnexionHelper[1755:21757] Attention: This instance will now terminate - another 3DconnexionHelper process is already running!
cjadams@Phoenix ~ %
Re: Spacemouse driver not working in Ventura
BUT i still only see this
cjadams@Phoenix ~ % ps aux | grep 3dconnexion
cjadams 1842 0.0 0.0 34261852 736 s000 R+ 3:36PM 0:00.00 grep 3dconnexion
cjadams@Phoenix ~ %
The 3dc items are in both launch items and launch daemons..but it never did regenerate that locked symlink.. fyi.. that is still gone
cjadams@Phoenix ~ % ps aux | grep 3dconnexion
cjadams 1842 0.0 0.0 34261852 736 s000 R+ 3:36PM 0:00.00 grep 3dconnexion
cjadams@Phoenix ~ %
The 3dc items are in both launch items and launch daemons..but it never did regenerate that locked symlink.. fyi.. that is still gone
Re: Spacemouse driver not working in Ventura
May be unrelated but criticized in another thread.
Blue LED Ring arbitrarily switches on on my Space Navigator
although deactivated in Driver.
In this case it helps to just open Ventura System Settings.
Not even needed to switch to 3DCon Driver Tab - and LED
will go off again.
Blue LED Ring arbitrarily switches on on my Space Navigator
although deactivated in Driver.
In this case it helps to just open Ventura System Settings.
Not even needed to switch to 3DCon Driver Tab - and LED
will go off again.
Re: Spacemouse driver not working in Ventura
On macOS 12, you were likely using v. 10.7.2 (or older) of 3DxWare 10. When you updated to "Ventura", you installed v. 10.7.3, the version where the bug with the LEDs was introduced.
You can confirm by uninstalling 10.7.3 and trying v. 10.7.2. The older version is available in the archive.
Re: Spacemouse driver not working in Ventura
No, I already had 10.7.3 on macOS 12 before.
And I upgraded/migrated from macOS 12 to Ventura Public Beta,
therefore I did not need to install the Driver from scratch.
And therefore I did not had the Driver installation troubles which
other users described in this thread.
And I upgraded/migrated from macOS 12 to Ventura Public Beta,
therefore I did not need to install the Driver from scratch.
And therefore I did not had the Driver installation troubles which
other users described in this thread.
Re: Spacemouse driver not working in Ventura
You may want to check 10.7.2 just to confirm that the LED issue that you're seeing is indeed MAC-343.
The only issue related to macOS 13 "Ventura" that we are aware is the weird dialogue with only the "Security & Privacy" icon and an "OK" button. That dialogue appears to have been fixed in macOS 13 Beta 13.And therefore I did not had the Driver installation troubles which
other users described in this thread.
All other issues (cannot allow DriverKit extension, driver does not recognise device) appear to be unrelated to macOS 13. In the case of the "allow" issue with the DriverKit extension, we have seen customers unable to find the "allow" button in the "Security & Privacy" pane since macOS begun to force users to acknowledge the installation of system extension, both kernel and DriverKit extensions. We do not know what causes it.
Re: Spacemouse driver not working in Ventura
can you guys confirm that there should be two allow items not just one? Are there two sides of the driver one driver for the device and one driver for the function keys? If so that might explain a lot because the puck always seems to work for me it's always the function keys that don't if that helps
what is the case that there are two drivers that need accepting that might explain a lot one driver is loading and one is not can you confirm?
what is the case that there are two drivers that need accepting that might explain a lot one driver is loading and one is not can you confirm?