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

Display Issue on Linux #52

Closed
Chappy59711 opened this issue Sep 24, 2016 · 6 comments
Closed

Display Issue on Linux #52

Chappy59711 opened this issue Sep 24, 2016 · 6 comments

Comments

@Chappy59711
Copy link

When Bloodhound is started, the initial screen tries to load, but turns black and hangs. In the command window, the following errors appear:

user@linux:/opt/BloodHound-linux-x64# ./BloodHound
[3065:0923/202117:ERROR:buffer_manager.cc(438)] [.DisplayCompositor-0xb19c6e9500]GL ERROR :GL_INVALID_ENUM : glBufferData: <- error from previous GL command
[3065:0923/202118:ERROR:gles2_cmd_decoder.cc(2210)] [.Offscreen-For-WebGL-0x25e11a897e00]GL ERROR :GL_INVALID_ENUM : BackFramebuffer::Destroy: <- error from previous GL command
[3065:0923/202118:ERROR:gles2_cmd_decoder.cc(2210)] [.Offscreen-For-WebGL-0x25e11a897e00]GL ERROR :GL_INVALID_ENUM : BackFramebuffer::Destroy: <- error from previous GL command
[3065:0923/202120:ERROR:texture_manager.cc(2942)] [.RenderCompositor-0x25e11a990800]GL ERROR :GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command
[3065:0923/202120:ERROR:gles2_cmd_decoder.cc(2210)] [.RenderWorker-0x25e11a897000]GL ERROR :GL_INVALID_ENUM : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command

A ^C will end the session in the command window which shuts down Bloodhound.

Thanks

@rvazarkar
Copy link
Contributor

Can you give any more details on what version of linux etc you're running? I just tested this on a debian image and it works fine.

Also, those errors look like they have more to do with your underlying OS/Display than BloodHound.

@Chappy59711
Copy link
Author

Good day,

I agree with the display issue. I am running the latest version of Kali
with all updates on the latest version of VirtualBox.

Thanks

On Mon, Sep 26, 2016 at 8:57 AM, Rohan Vazarkar notifications@github.com
wrote:

Can you give any more details on what version of linux etc you're running?
I just tested this on a debian image and it works fine.

Also, those errors look like they have more to do with your underlying
OS/Display than BloodHound.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#52 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUSW_imDB9BsuKATxSF3NnHL0kbMfIoyks5qt91jgaJpZM4KFh2K
.

@rvazarkar
Copy link
Contributor

I'm unable to recreate this issue as of now. Are you still experiencing the same problem?

@rvazarkar rvazarkar reopened this Oct 26, 2016
@rvazarkar
Copy link
Contributor

Closing since theres been no response

@cptMustard
Copy link

Ran into same issue and was able to reproduce with same context (up-to-date Kali in up-to-date Virtualbox), the problem can be solved by making sure that VirtualBox 3D acceleration feature is disabled for the Kali VM.
Not a problem with Bloodhound.

@allfro
Copy link

allfro commented Nov 12, 2024

This destroys performance of other tools such as Burp's chrome browser. Disabling 3d acceleration should not be considered a fix.

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

4 participants