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

wf-shell-0.3.1: wf-background: symbol lookup error #20618

Closed
mamins1376 opened this issue Apr 3, 2020 · 20 comments
Closed

wf-shell-0.3.1: wf-background: symbol lookup error #20618

mamins1376 opened this issue Apr 3, 2020 · 20 comments
Labels
bug Something isn't working

Comments

@mamins1376
Copy link
Contributor

I'm using Wayfire as display server. Trying to utilize any executable provided by wf-shell results in symbol lookup error. Maybe a linking error?

  • xuname: Void 5.4.28_1 x86_64 AuthenticAMD notuptodate rrrmFFFFFFF
  • package: wf-shell-0.3.1

(notuptodate because I use a tier 2 mirror.)

Expected behavior

it should Just Work(TM).

Actual behavior

$ wf-background
wf-background: symbol lookup error: wf-background: undefined symbol: _ZN12wf_animation6circleE

Same also happens with both wf-panel and wf-dock.

Steps to reproduce the behavior

  1. # xbps-install wf-shell
  2. Use any binary provided by the package to see the results.
@mamins1376
Copy link
Contributor Author

Is there any relevant issue on the original repo?

@mamins1376
Copy link
Contributor Author

WayfireWM/wf-config@0.3...0.4.0diff-6bad5f24ce4d828f1c5cc76bacc23461L14

Thanks! but seem like this link is broken

@mamins1376
Copy link
Contributor Author

Would a simple patch version bump fix trigger that? Maybe landing the fix by upstream repo takes place after an actual release

@mamins1376
Copy link
Contributor Author

@xtraeme yea realized it a little bit late :) I'm confused, now wf-config should be bumped to 0.4.0._3 right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
@mamins1376 and others