You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I frequently use Shotcut to open and re-export portions of short video clips created by Xbox Game Bar. When closing Shotcut very quickly after doing this, Shotcut will reopen after it's closed, which is somewhat frustrating.
Inspecting the "Previous" application log after Shotcut restarts in this manner, the line [Warning] <qMain> child process failed, restarting in OpenGL mode seems important. The full application log is included below.
Environment:
OS: Windows 10 Education 22H2 (19045.4780)
Shotcut: 24.06.26
Steps to reproduce:
Launch Shotcut
Before 30 seconds have elapsed, close Shotcut with Ctrl+Q or by clicking the "X" button in the upper-right
Notes:
The issue occurs regardless of whether Shotcut is run by itself or used to open a video file. If Shotcut was used to open a video file, the same file will be opened when it launches the second time. Quickly closing Shotcut again after it has relaunched itself once does not produce the issue again.
Description:
I frequently use Shotcut to open and re-export portions of short video clips created by Xbox Game Bar. When closing Shotcut very quickly after doing this, Shotcut will reopen after it's closed, which is somewhat frustrating.
Inspecting the "Previous" application log after Shotcut restarts in this manner, the line
[Warning] <qMain> child process failed, restarting in OpenGL mode
seems important. The full application log is included below.Environment:
OS: Windows 10 Education 22H2 (19045.4780)
Shotcut: 24.06.26
Steps to reproduce:
Notes:
The issue occurs regardless of whether Shotcut is run by itself or used to open a video file. If Shotcut was used to open a video file, the same file will be opened when it launches the second time. Quickly closing Shotcut again after it has relaunched itself once does not produce the issue again.
The text was updated successfully, but these errors were encountered: