Tor Browser minimize/maximize/close buttons are invisible

[pillmuncher]

Please confirm there isn't an open report for this issue

• I have searched through bug reports

Summary

Tor Browser minimize/maximize/close buttons are invisible until I move the mouse over the place where they should be, then they're displayed as grey circles. I've tried several widget themes and it's the same in all of them.

Steps to reproduce

1. Start Tor Browser.
2. Don't see the minimize/maximize/close buttons.

Expected result

The minimize/maximize/close buttons should be visible and display the expected symbols.

Actual result

The minimize/maximize/close buttons are invisible.

Environment

• Is system up to date?

Repo

Polaris (stable)

Desktop Environment

Budgie

System details

System:
Host: niteowl Kernel: 6.17.8-324.current arch: x86_64 bits: 64
Desktop: Budgie v: 10.9.4 Distro: Solus 4.8 opportunity
Machine:
Type: Desktop Mobo: ASUSTeK model: E3M-ET V5 SERIES v: Rev X.0x
serial: Firmware: UEFI vendor: American Megatrends
v: 2606 date: 02/23/2018
CPU:
Info: quad core Intel Xeon E3-1270 v6 [MT MCP] speed (MHz): avg: 800
min/max: 800/4200
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Lexa XT [Radeon PRO WX 2100]
driver: amdgpu v: kernel
Device-2: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9 driver:
gpu: amdgpu resolution: 1: 1920x108060Hz 2: 1920x108060Hz
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.1 renderer: AMD
Radeon Pro WX 2100 (radeonsi polaris12 ACO DRM 3.64 6.17.8-324.current)
Info: Tools: api: eglinfo, glxinfo, vulkaninfo gpu: amdgpu_top, lact,
radeontop x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
Drives:
Local Storage: total: 1.42 TiB used: 643.52 GiB (44.2%)
Info:
Memory: total: 32 GiB available: 31.29 GiB used: 11.5 GiB (36.7%)
Processes: 403 Uptime: 7d 21h 21m Shell: Zsh inxi: 3.3.40

Other comments

No response

[Jaredy899]

I could not replicate it. I tested on KDE and a fresh Budgie install and they both showed up.

[TraceyC77]

Can you create a brand new user, with default settings, and see if the bug occurs with that login? There may be a specific setting in your normal user contributing to this.