Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XDamage support breaks SIGUSR1 support on macOS #536

Closed
npyl opened this issue Jul 9, 2018 · 2 comments
Closed

XDamage support breaks SIGUSR1 support on macOS #536

npyl opened this issue Jul 9, 2018 · 2 comments
Assignees
Labels
bug related to incorrect existing implementation of some functionality Stale requires attention because it hasn't been updated in a long time

Comments

@npyl
Copy link
Collaborator

npyl commented Jul 9, 2018

Hi!
I decided to bring this up here -not only in the fork of conky for macOS- in order to gain some more attention and thankfully more experienced developers.

Problem is, that if you compile conky with XDamage support ON, for some reason SIGUSR1 causes conky to crash (or Xquartz -not quite sure which of the two crashes first-) before reloading (as it should).

The problem disappears only when you compile conky with BUILD_XDAMAGE set to OFF, but that obviously is not a very positive solution. Could anyone check this out?

This is a follow-up to this.

I opened an issue in XQuartz's Bugzilla: link

@npyl npyl self-assigned this Sep 1, 2018
@lasers lasers added the bug related to incorrect existing implementation of some functionality label Sep 1, 2018
@github-actions
Copy link

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment, or this issue will be closed in 30 days.

@github-actions github-actions bot added the Stale requires attention because it hasn't been updated in a long time label Sep 18, 2023
@github-actions
Copy link

This issue was closed because it has been stalled for 30 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug related to incorrect existing implementation of some functionality Stale requires attention because it hasn't been updated in a long time
Projects
None yet
Development

No branches or pull requests

2 participants