Bug 1443620
| Summary: | Add patches to allow integration with sway under Wayland | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Pokorný [poki] <jpokorny> | ||||
| Component: | redshift | Assignee: | Miloš Komarčević <kmilos> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 30 | CC: | fale, kmilos, oliver | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-05-26 14:41:41 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jan Pokorný [poki]
2017-04-19 14:49:29 UTC
Created attachment 1272662 [details]
Proposed solution to get Redshift working with sway under Wayland
Then, users can have following in their ~/.config/redshift.conf
for this integration to work:
> [redshift]
> adjustment-method=wayland
To be completely honest, it looks like exiting redshift triggers a segfault
(at least with that new adjustment method):
src/redshift.c:
1652│
1653│ /* Clean up gamma adjustment state */
1654├> method->free(&state);
1655│
1656│ return EXIT_SUCCESS;
#0 0x00007f038f14f9b9 in wl_map_insert_at
(map=<optimized out>, flags=flags@entry=0, i=<optimized out>,
data=<optimized out>)
at src/wayland-util.c:249
#1 0x00007f038f14bafe in proxy_destroy
(proxy=0x5626ecf6dff0)
at src/wayland-client.c:411
#2 0x00007f038f14bafe in wl_proxy_destroy
(proxy=0x5626ecf6dff0)
at src/wayland-client.c:442
#3 0x00005626ecd413c9 in main
(argc=<optimized out>, argv=<optimized out>)
at redshift.c:1654
Hard to say if the problem is on redshift (#3) or wayland (rest) side.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Still applicable and still no response. Moving to Rawhide. Also can confirm it will stay applicable when sway gets updated to 1.0. This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle. Changing version to '30. This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |