Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] When RightLibPaletteBoardModeIsCollapsed=true the main Window stays invisible. #1164

Open
qqqqqqqqq9 opened this issue Nov 17, 2024 · 6 comments
Labels

Comments

@qqqqqqqqq9
Copy link

Describe the bug

I use OpenBoard on Plasma/Wayland. For me the main window stay invisible. It shows in the pager and the window list.

To Reproduce

  1. Start OpenBoard.
  2. Close the right tab.
  3. Close OpenBoard.
  4. Start OpenBoard.

Expected behavior

OpenBoard should start.

Actual behavior

OpenBoard started but the window was invisible.

Workaround:
Open the config and set

RightLibPaletteBoardModeIsCollapsed=true

Context

  • reproducibility : systematic
  • OpenBoard version :
    • bug happens with : 1.7.1
      - didn't check : 1.6.4 1.7.0
  • OS :

Additional context

- Linux : `openSuSE Tumbleweed `
@qqqqqqqqq9 qqqqqqqqq9 added the bug label Nov 17, 2024
@letsfindaway
Copy link
Collaborator

Did you know that there is an official package for OpenBoard 1.7.1 in the openSUSE repositories?
https://software.opensuse.org/package/OpenBoard?search_term=Openboard

And I could not reproduce the problem here. Could you try it with the official package? Have you any other information about the problem?

@qqqqqqqqq9
Copy link
Author

Hi,
yes I know about the official package but I wanted to try a qt6-version.

When I run from a terminal it spit's out the following:

libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
Persisting document; path is "... edited custom path .../OpenBoard Document 2024-11-17 20-40-15.767/metadata.rdf"
eglSwapBuffers failed with 0x300d, surface: 0x0

@qqqqqqqqq9
Copy link
Author

The official version works find.

@letsfindaway
Copy link
Collaborator

eglSwapBuffers failed with 0x300d, surface: 0x0

When searching for this error message on the web I find quite some hits, e.g.

I did not analyze all of them thoroughly, but they seem to be similar to your bug. The KDE people say it might be Qt or NVIDIA. At least it is nothing OpenBoard can do much about.

Recommendations:

  • Try it on a X11 session
  • Try it using xwayland by setting the environment variable QT_QPA_PLATFORM=xcb

BTW: I'm the maintainer of the OpenBoard package on openSUSE. I have also experimental packages built using Qt6 with the current release candidate of 1.7.2 here: https://build.opensuse.org/package/show/home:letsfindaway:experimental/OpenBoard-Qt6. And I plan to build the next release version also with Qt6. So I'm interested in your experiences and possible problems for a Qt6 version.

Note also that OpenBoard has some known issues on Wayland. E.g. the screen configuration dialog in the preferences crashes OpenBoard when you click in the screen list. And screenshots and screen mirroring in Desktop mode don't work due to the Wayland restrictions on screen grabbing. We at least recommend to set the environment variable mentioned above. It avoids the crash.

@qqqqqqqqq9
Copy link
Author

Hi,
thanks, using QT_QPA_PLATFORM=xcb works fine.
It might well be a QT-Problem. (My QT is 6.8) I was confused because the invisibility was so not random and can be trigger by hiding the right tab.

I tried the qt6-Build of 1.7.2.
It opens in Desktop mode. When I switch to Board mode the window disappears.
When the right tab is shown in the beginning, it works fine.

@letsfindaway
Copy link
Collaborator

Thanks for testing. I have created a PR to set this environment variable automatically when OpenBoard starts.

I see that Tumbleweed currently uses Qt 6.8.0. If it is indeed the problem described in https://bugreports.qt.io/browse/QTBUG-129403, then it did not occur on previous Qt versions and it might be fixed in Qt 6.8.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants