-
Notifications
You must be signed in to change notification settings - Fork 8
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
Assertion running fuzzel #158
Comments
Hej Matt! Thank you for reporting the issue. Could you document what version of fuzzel you had been using, and what commandline you used? |
I'll grab the version tonight if I can - I used a package for Arch (pretty sure it's a first party one, likely just installed with I'm running the 0.4.1 AUR for wlmaker at the moment |
A quick test on the developer laptop I had at hand:
Gave me a Concluding:
=> A different version may have it not crash, but keyboard interactivity will be missing. @mattlacey -> highly interested in knowing your What to do:
|
I bet you feel like your todo list is growing rather fast right now!
|
😅 -- there's always more TODO than available time... Thanks for reporting the version! Curious that the more recent version has that behaviour. So we do have a disgreement between |
Yeah I know that feeling, never have enough time for all my side projects. I'll grab the source soon though and attempt to build from that, very keen to see this do well because I loved running WindowMaker back in the day and even though it's had some love recently (ish) I like the idea of going all-new as well with the switch to Wayland. |
Off to a great start with this! Will grab the source sometime and have a play at building and tinkering.
Anyway, installed fuzzel, and running it triggers an assertion, something to do with layout at a guess:
The text was updated successfully, but these errors were encountered: