[Trisquel-users] Redshift and Mouse Cursor
I'm looking into installing Trisquel 8 on my MBP (mid-2009). One of the programs that I consider indispensable is Redshift. The issue is that Redshift doesn't affect the colour of my mouse cursor. The reason for this seems to be that the graphics driver is configured to use hardware cursors. According to the Redshift website, some graphics drivers have an option to disable hardware cursors in xorg.conf. Could you please explain to me how to test this solution?
Re: [Trisquel-users] Redshift and Mouse Cursor
So, I read that the SW cursor may be enabled by creating a .conf file with the following code: Section "Device" Identifier "Nvidia 9400" Driver "nouveau" Option "SWCursor" "true" EndSection and placing it in /etc/X11/xorg.conf.d. I attempted to do this via Pluma; the issue is that, as I'm running a live instance of T8, Pluma does not allow me to save the file because I don't have the necessary permissions. How do I get them?
Re: [Trisquel-users] Redshift and Mouse Cursor
I did this, and I managed to create the necessary file. At this point, rebooting would be appropriate, but I cannot do so because it's a live image and logging in and out made no difference. So, I'm not sure whether the SW cursor is enabled or not.
Re: [Trisquel-users] Redshift and Mouse Cursor
Any ideas, anyone? It's an annoying issue, whose solution may not be that complicated; I'd just like for someone to guide me through some possible workarounds.
Re: [Trisquel-users] Redshift and Mouse Cursor
> At this point, rebooting would be appropriate, but I cannot do so because it's a live image and logging in and out made no difference. Given what you are trying to do, I suspect that you do not need to reboot. I think you just need to restart X. Logging out doesn't do this, but I think restarting LightDM might. Try $ sudo systemctl restart lightdm
Re: [Trisquel-users] Redshift and Mouse Cursor
> Try > $ sudo systemctl restart lightdm I did this, but nothing changed regarding the original issue. I'm not sure whether that is because the software cursor was not successfully enabled or because it was enabled, in which case this was not the solution. I suppose the next step would be to verify whether the SW cursor is enabled. Would you know how I could find that out?