-
Notifications
You must be signed in to change notification settings - Fork 295
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
Weasis 4.0.1 cannot open any images, throws NPE #303
Comments
Thank you for reporting this problem. It is surprising that this value is null because it seems to come from the default screen position. It could be a driver graphic problem. According to the stacktrace, I don't understand why it tries to open on an external window. |
Thanks for taking a look @nroduit! I have 4 QHD monitors, all running on an RTX 3060 running NVIDIA driver 510.73.05. I did switch from an AMD RX 480 to this RTX 3060 when I changed my OS, so maybe that's why it was working before? Maybe this is an NVIDIA compatibility problem? |
Can you share the whole stacktrace in debug mode? I want to see the cause of the exception. What type of installer do you use for Weasis (deb, snap, flatpack)? |
I'm using |
To configure and access the logs please visit this page. If you can transmit the complete error (usually there is a stack of errors). |
Please reopen this issue if it has not been resolved in the current version. |
@nroduit I'm experiencing the exact same problem -- v. 4.2.0 (Flatpak), Arch Linux, Sway.
Nope, I'm afraid, this is the output from an entire Weasis "session" exhibiting the problem:
Reviving the issue as suggested! :) Thanks! |
Installations with Flatpak or Snap are in sandbox mode with an intermediate Runtime which can lead to various types of problems, see also #449. My recommendation is to use deb or rpm packages instead. |
@nroduit Roger that, thanks. FWIW, I can inform that the Weasis extracted from the .deb file is non-functioning as well -- however, starting a Fluxbox session, suddenly both the Flatpak version as well as the .deb version works. I'm guessing it has to do with Xwayland somehow. Just in case that rings a bell on your end. I'm good here! |
I opened a new issue and will provide a fix to better handle the consequence of this problem. |
Issue of using the latest nvidia driver 535 and wayland: |
Describe the bug
Cannot open any images. This worked previously on Pop_OS! 20.04. On this fresh install of Zorin 16.1 (see details below), Weasis installs properly and opens, and even imports the DICOMs, but it will not actually load the image. The thumbnails appear in the DICOM Explorer, but they cannot be opened (by right-clicking and open or double-clicking). I get a stack trace with a Null Pointer Exception when opening the DICOM files. These DICOM files previously worked in Weasis. Using previous versions of Weasis back to 3.6.0 does not fix this. Is there something on the OS or Kernel level that is missing in Zorin 16? Is there a library needed? I couldn't find a lot of info about this aside from glibc which is present at version 2.31.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The image opens when opened.
Desktop (please complete the following information):
Traces
The text was updated successfully, but these errors were encountered: