You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run redshift as either; redshift-gtk or redshift-gtk -m randr
message appears
Expected behavior
A clear and concise description of what you expected to happen.
I've used Redshift since the project started with Slackware, and since that time I have never seen this message before, in fact I've never had any messages, it's always run perfectly.
So I'm assuming with a newer updated system, newer gtk, X, libs, dependencies, etc., is the reason for this message, and Redshift needs to be updated.
Error output/logs/screenshots
n/a
Software versions (please complete the following information):
OS: Linux
Redshift version: 1.12
Distribution: Slackware
Redshift installed from: [e.g. "using apt-get", "built from source"]
Built from source
Is there anyway I can fix this issue?
THANKS
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
When I run redshift as either; redshift-gtk or redshift-gtk -m randr I see this message.
(redshift-gtk:6420): Gdk-CRITICAL **: 19:39:11.806: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
I've used Redshift since the project started with Slackware, and since that time I have never seen this message before, in fact I've never had any messages, it's always run perfectly.
So I'm assuming with a newer updated system, newer gtk, X, libs, dependencies, etc., is the reason for this message, and Redshift needs to be updated.
Error output/logs/screenshots
n/a
Software versions (please complete the following information):
Built from source
Is there anyway I can fix this issue?
THANKS
The text was updated successfully, but these errors were encountered: