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`

[BryanFRitt]

Ops... I think I may have been wrong when I attributed this to Redshift, and it was just luck that it happened that way. The only thing that remained constant was that after reboots, starting R'n'D would cause a crashes, but after some point the crashing after trying to start R'n'D would stop, well that is until the next reboot. Never figured out what the event was that caused R'n'D to start working again without crashing.

I just switched KDE themes and, at least it seems that, after reboots starting R'n'D no longer causes crashes. So maybe there's something going on between R'n'D and KDE themes that doesn't/didn't work right?, or something else fixed it?, that or I've just gotten lucky these last few (re)boots?

[filbo]

I guess you could A/B test by switching back to the previous theme and seeing if RnD gets sick again. And then, if proven, state what the 'bad' and 'good' themes are, which would give a basis for others to try to reproduce it...

[Holger]

I really would like to see what a debugger would show when such a crash happens!

Just by chance, do you happen to run R'n'D on Mac or Linux maybe? And have somebody around who can set up a development system to build R'n'D? (Which should be relatively easy on Mac or Linux, maybe with some AI support, but seems to be more tricky on a Windows system, although I did that once using Cygnus and MinGW.)

Then you could just start R'n'D using "make gdb" and see what happens when it crashes...

[filbo]

Bryan used `gdb` in the first post about this, and it's all under KDE, so `make gdb` should be well in hand :)

[Holger]

Bryan used `gdb` in the first post about this, and it's all under KDE, so `make gdb` should be well in hand

Oops, I totally forgot about it, and didn't look again at the first page of this topic, so I missed it!

But yes, I remember that I studied the gdb output, and wasn't able to find what might have caused this.

[BryanFRitt]

I guess you could A/B test by switching back to the previous theme and seeing if RnD gets sick again. And then, if proven, state what the 'bad' and 'good' themes are, which would give a basis for others to try to reproduce it...

Unfortunately, I don't remember what the theme was set to before.

But I do remember [?with the old theme], whenever the R'n'D was running [sometimes?] the window boarders of Firefox and [other windows?] would disappear, [, or turn black?], then go back to normal after R'n'D was exited.

I've gone back and tried other themes, etc..., and the problems all seem to be gone[no crash, no window boarder errors] no matter which theme is selected, and haven't been able to recreate the issue(s). Although, I haven't retried rebooting again to get the problem to reshow.

[filbo]

> Unfortunately, I don't remember what the theme was set to before.

Hmmm. If you have old backups of your account, you could probably extract and find it. But it's getting to be a more advanced project :)