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

bbkeys seg fault #7

Closed
ghost opened this issue Feb 12, 2016 · 3 comments
Closed

bbkeys seg fault #7

ghost opened this issue Feb 12, 2016 · 3 comments

Comments

@ghost
Copy link

ghost commented Feb 12, 2016

I just pulled from git today and compile 0.71.2 and when I run bbkeys I get a seg fault at the command line. In the last version, 0.71.1 bbkeys was working ok.

bbkeys: ScreenHandler: in findSupportingWM.
bbkeys: ScreenHandler: first readSupportingWMCheck succeeded.
bbkeys: ScreenHandler: second readSupportingWMCheck worked.
bbkeys: ScreenHandler: first try at getting wmName failed.
bbkeys: ScreenHandler: couldn't get wm's name. letting it slide this time....
bbkeys: ScreenHandler: Found compatible window manager: [beats the heck out of me] for screen: [0].
bbkeys: ScreenHandler: Supported atoms: [45].

@bbidulock
Copy link
Owner

You have something seriously wrong. I get:

bbkeys: ScreenHandler: in findSupportingWM.
bbkeys: ScreenHandler: first readSupportingWMCheck succeeded.
bbkeys: ScreenHandler: second readSupportingWMCheck worked.
bbkeys: ScreenHandler: Found compatible window manager: [Blackbox 0.71.2] for screen: [0].
bbkeys: ScreenHandler: Supported atoms: [69].

@ghost
Copy link
Author

ghost commented Feb 13, 2016

Slackware has a build script, blackbox.SlackBuild that I'm using for compiling and I haven't changed anything with it.

http://mirrors.slackware.com/slackware/slackware64-current/source/xap/blackbox/

So I'm not sure how 0.71.1 could work find and then 0.71.2 doesn't... hmm

@ghost
Copy link
Author

ghost commented Feb 13, 2016

I originally ran git clone previously, then the other day ran git pull and compiled it, and ran into the problems. All I can assume is something in the pull somehow screwed up.

Because today I deleted the directory and ran git clone over and started fresh, compiled and it now works...

hmm odd

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant