Bug: node colors are black

[pwnter]

Description:

Node colors are black, i had this since few updates ago..

Are you intending to fix this bug?

"no"

Component(s) Affected:

• UI

Actual Behavior:

Node colors are black, i had this since few updates ago..

• I tried resetting the database docker-compose down -v, removed bloodhound .config files.
• Removed all the docker images & freshly installed bloodhound-ce but I still have same issues*

Screenshots/Code Snippets/Sample Files:

Environment Information:

BloodHound: [v7.0.1]

Collector: [SharpHound: v2.5.13] & [Python-BloodHound-CE by dirkjanm: Latest]

OS: [Kali: 6.11.2] & [Arch-Linux: 6.12.13-1-lts]

Browser (if UI related): [Kali: Mozilla Firefox 128.7.0esr] & [Arch: Mozilla Firefox 135.0]

Node.js (if UI related: [Kali: Node.js v20.18.1] & [Arch: Node.js v23.8.0]

Contributor Checklist:

• [ ] I have searched the issue tracker to ensure this bug hasn't been reported before or is not already being addressed.
• [ ] I have provided clear steps to reproduce the issue.
• [ ] I have included relevant environment information details.
• [ ] I have checked that any JSON files I am attempting to upload to BloodHound are valid.

[pwnter]

Nodes are fine in BloodHound-Legacy..

Edit: Used Python-BloodHound injestor by dirkjanm

[StephenHinck]

BloodHound CE and Legacy use completely different UI mechanisms. Can you please provide a screenshot of your browser console error log when loading the CE user interface?

[ScubaRoomba]

Not the OP, but I also have the same issue. Here are my browser's (Firefox) console error logs.

[exploide]

This happens for me only in a virtualized Firefox.

• Firefox in VM (QEMU/KVM): black
• Chromium in VM (QEMU/KVM): works
• Firefox on host: works

[pwnter]

BloodHound CE and Legacy use completely different UI mechanisms. Can you please provide a screenshot of your browser console error log when loading the CE user interface?

Firefox:

Its working in Chrome:

[exploide]

It appears to work again. With BloodHound 7.1.1 and Firefox 136.0.2, the node icons look as intended, even in a virtualized environment. The WebGL rendering errors are also gone.

Either it has already been fixed or something just changed on my end. Don't know if the other reporters still face the problem.

[StephenHinck]

Thank you for confirming, really glad this is working again!

[pwnter]

Its working on Firefox in VMs & Host.. Thank you.

[StephenHinck]

This has apparently reappeared on BloodHound v7.4.0 on Kali Linux FireFox. Chromium continues to work as expected.

[Skriep]

Same issue here with BloodHound v7.5.1 on Kali Linux 6.12.20 (VM), Firefox 115.1.0esr, Node.js v18.19.0.

[pwnter]

Its working on Firefox 140.0 ESR..

For anyone having the issue, switch to other browsers for now..

[rvazarkar]

I don't believe this is something we can control, this is either a bug in WebGL or its an upstream bug in sigma. The fact that the issue is mainly happening in virtualized envs makes me think its probably a bug in the webgl/gpu implementation in the virtualization. Either way, this isn't something we really have the capability to fix.