Starting Rocks'n'Diamonds when redshift program is running causes R'n'D to crash.

[filbo]

If the above does work, it sounds like too much trouble to get working.

Problem solved by deleting Kwin config files in ~/.config and /.local/share and a reconfiguration afterwards.

Hmmm, sounds like just 'save and delete the relevant files in ~/.config and ~/.local/share; log in to KDE and see if the problem persists; put the files back'. With difficult details (1) what are 'the relevant files' and (2) need to carefully do the file manipulation while *NOT* logged in via KDE; e.g. on text console login (Ctrl+Alt+Fn, value of n varies on different distros -- there should be around 4-6 different text consoles available).

But that's actually the wrong approach. Right approach:

1. create a new test user
2. login with that user under KDE (X11)
3. test RnD (works)
4. configure `redshift` or `gammastep`
5. test RnD
6. if it still works, there's some difference between this 'blank' KDE setup and whatever your regular account has, figure out what it is...

[BryanFRitt]

If the above does work, it sounds like too much trouble to get working.

Problem solved by deleting Kwin config files in ~/.config and /.local/share and a reconfiguration afterwards.

Hmmm, sounds like just 'save and delete the relevant files in ~/.config and ~/.local/share; log in to KDE and see if the problem persists; put the files back'. With difficult details (1) what are 'the relevant files' and (2) need to carefully do the file manipulation while *NOT* logged in via KDE; e.g. on text console login (Ctrl+Alt+Fn, value of n varies on different distros -- there should be around 4-6 different text consoles available).

But that's actually the wrong approach. Right approach:

1. create a new test user
2. login with that user under KDE (X11)
3. test RnD (works)
4. configure `redshift` or `gammastep`
5. test RnD
6. if it still works, there's some difference between this 'blank' KDE setup and whatever your regular account has, figure out what it is...

Agreed, although I'd call things a worse/better instead of wrong/right.

[BryanFRitt]

I managed to get redshift to do a transition when I set it to using a config file. But this isn't causing rocks'n'diamonds to crash at startup during the sunrise/sunset periods like the way I had done Redshift before.

Code: Select all

[redshift]
dawn-time=HH:MM-HH:MM
dusk-time=HH:MM-HH:MM
temp-day=6500
temp-night=2200

in ~/.config/redshift.conf replacing HH:MM-HH:MM with a transition period, with one usually sometime around the current time for the transition that is being tested.
Kill all running redshift programs.
`ps aux | grep -i redshift | grep -v grep`
kill thePID(s) found, if any
`kill -15 thePID(s)`
Then start redshift with
`/usr/bin/redshift-qt`