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.

Sign up for GitHub

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

Jump to bottom

Koodo Blank Window: Video Sandbox Error #658

Closed
3 tasks done
gryphonB-2 opened this issue Dec 11, 2022 · 1 comment
Closed
3 tasks done

Koodo Blank Window: Video Sandbox Error #658

gryphonB-2 opened this issue Dec 11, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@gryphonB-2
Copy link

I've already installed the latest developer version of Koodo Reader, this problem still exsits

  • Yes

There are no similar issues on the issue list

  • Yes

I've already read the document, still can't solve it.

  • Yes

Operating system or browser

Ubuntu

App Version

1.3.9

Bug Detail

koodo-reader opens. Briefly, the interface is seen as in the web demo, then the window blanks. Opening koodo from command line displays this error:

libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
[87731:1212/082756.625400:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

The error occurs in both the .deb and the .appimage versions

My details:
OS: Linux Mint 20 , kernel version 5.4.0-135-generic
Video Driver: nvidia 390

Screenshots (Optional)

No response

Files (Optional)

No response
@gryphonB-2 gryphonB-2 added the bug Something isn't working label Dec 11, 2022
@troyeguo
Copy link
Collaborator

Is this bug reproducible in 1.5.0 version?

troyeguo added a commit that referenced this issue Jan 25, 2024
@troyeguo
close #258, close #318, close #367, close #664, close #661, close #658,
f6d1fe3 
close #651, close #634, close #628, close #616, close #615, close #604, close #564, close #539, close #533, close #512, close #474, close #466, close #459, close #460, close #670, close #674
troyeguo added a commit that referenced this issue Jan 25, 2024
@troyeguo
close #258, close #318, close #367, close #664, close #661, close #658,
a005d91 
close #651, close #634, close #628, close #616, close #615, close #604, close #564, close #539, close #533, close #512, close #474, close #466, close #459, close #460, close #670, close #674
troyeguo added a commit that referenced this issue Jan 25, 2024
@troyeguo
close #258, close #318, close #367, close #664, close #661, close #658,
7fe73f6 
close #651, close #634, close #628, close #616, close #615, close #604, close #564, close #539, close #533, close #512, close #474, close #466, close #459, close #460, close #670, close #674

Former-commit-id: a005d91
troyeguo added a commit that referenced this issue Mar 2, 2024
@troyeguo
close #258, close #318, close #367, close #664, close #661, close #658,
f8dc153 
close #651, close #634, close #628, close #616, close #615, close #604, close #564, close #539, close #533, close #512, close #474, close #466, close #459, close #460, close #670, close #674

Former-commit-id: a005d91
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@troyeguo @gryphonB-2