No access to file-menue in full-screen
After I change to full-screen, and i click on "file", nothing happens. It works in debug-mode and in normal mode without full-screen. This issue happens only with the Linux-Version. In the Windows-Version it works.
Expected behavior A clear and concise description of what you expected to happen.
System Details
- OpenShot Version: 3.2.1-dev
- libopenshot Version: 0.3.3
- Platform: Linux-6.8.0-47-generic-x86_64-with-glibc2.4
- Processor: x86_64
- Machine: x86_64
- Python version: 3.8.10
- Qt5 version: 5.12.8
- PyQt5 version: 5.14.1
- Qt Detected Languages: ['de-DE']
- LANG Environment Variable: de_DE.UTF-8
- LOCALE Environment Variable:
- Daily Build: Verified issue still exists in daily build: http://github.com/OpenShot/openshot-qt/releases/download/OpenShot-v3.2.1-dev-daily-12980-09ca2ced-23713d3a-x86_64.AppImage
Log Files
- openshot-qt.log (42 KB)
- libopenshot.log (8 KB)
Exception / Stacktrace
No stacktrace found in log files
Screenshots (Optional) If applicable, add screenshots to help explain your problem. You can include screenshots by copy/pasting them on GitHub or dragging-and-dropping into the GitHub page. All images are public, so please don't post screenshots containing personal information.
Hello @jackup53 I just tested this in Ubuntu 24.04 lts and I am not experiencing the issue. However, my Ubuntu is running as a guest in Oracle Virtualbox with my host being Windows 11 Pro.
I wonder if this is related to hardware (GPU, display drivers, desktop)?
Any update @jackup53?
Not yet. I will try, but at the moment there is no time.--Gesendet mit der WEB.DE Mail AppAm 03.11.24, 19:53 schrieb Colorjet3 @.***>:
Any update @jackup53?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Thank you so much for submitting an issue to help improve OpenShot Video Editor. We are sorry about this, but this particular issue has gone unnoticed for quite some time. To help keep the OpenShot GitHub Issue Tracker organized and focused, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.
This issue will be closed, as it meets the following criteria:
- No activity in the past 180 days
- No one is assigned to this issue
We'd like to ask you to help us out and determine whether this issue should be reopened.
- If this issue is reporting a bug, please can you attempt to reproduce on the latest daily build to help us to understand whether the bug still needs our attention.
- If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.
Thanks again for your help!
I am still unable to reproduce this issue in Windows or any of my Linux environments (Ubuntu 25.10, Fedora 43 and Mint 22.2).
Closing for now but feel free to reopen if issue is reproduceable.