Sometimes the "File Open" dialog refuses to work
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
No source file, test, or reliable reproduction steps are identified. Start by reproducing Cmd+O on macOS 15.2 arm64 with Binary Ninja 4.3.6766-dev, then inspect the reported stderr messages and the file-open dialog behavior. Done means identifying a reproducible cause and keeping the dialog open so a file can be selected.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Version and Platform (required):
- Binary Ninja Version: 4.3.6766-dev
- OS: macOS
- OS Version: 15.2
- CPU Architecture: arm64
Bug Description:
Sometimes trying to use Cmd+O to open a file refuses to work. Every time the dialog opens, it just closes itself. This persists across binja restarts until I reboot my entire computer or until some mystery amount of time has passed and then it just decides to work again. I haven't been able to reliably reproduce it or figure out why it happens when it does.
Steps To Reproduce:
- ???
- Try to open a file
- Window closes before i can pick a file
Expected Behavior:
I expected the window to stay open
Screenshots/Video Recording:
https://github.com/user-attachments/assets/e21502bf-313b-4a50-b259-f84bc60c5a71
Additional Information:
Every time this happens, I get the following errors in stderr:
2025-01-28 17:38:31.307586-0500 binaryninja[64556:6802532] [OpenSavePanels] Ignoring NSSavePanel method sent to NSOpenPanel: setNameFieldStringValue:
2025-01-28 17:38:31.424366-0500 binaryninja[64556:6802532] [availability] Can't find or decode accessNotGrantedUseCases
2025-01-28 17:38:31.425739-0500 binaryninja[64556:6802532] [availability] Can't find or decode accessNotGrantedUseCases
This might be a Qt bug but it's hard to tell.
- Lenguaje dominante
- C++
- Estrellas
- 1.3k
- Forks
- 298
- Merge medio
- 5 d 5 h
- PR fusionados (30 d)
- 19
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Vector35/binaryninja-api
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
Vector35/binaryninja-api#8540 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Vector35/binaryninja-api#8516 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
Vector35/binaryninja-api#8503 ·
-
normalize time logs from WARP Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Vector35/binaryninja-api#8446 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Vector35/binaryninja-api#8444 ·
Todos los issues de Vector35/binaryninja-api
Issues similares
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 92/100
autowarefoundation/autoware_universe#13413 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
automated-analysis bug memory-safety
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
gazebosim/gz-sensors#662 · 1 comentario ·