Weasis icon indicating copy to clipboard operation
Weasis copied to clipboard

Weasis shuts down immediately after launch

Open rlcolburn opened this issue 2 years ago • 12 comments

Describe the bug. What happened?

Windows 11 home 22h2 2261.2283

installed weasis version 4.2.0 from the microsoft store When i try to launch, it seems to do so before automatically closing a split second later (before any chance to even load files).

Additional detail: weasis launch logo shows, then the plug-ins loader/launch box appears to run, shows "completed 41 of 41 plug-ins", and the program itself launches as well (icon in the taskbar too) , then subsequently closes everything.

What version of Weasis are you running?

4.2.0

On which system the problem occurs?

Windows

Relevant log output

it doesnt stay open long enough to retrieve the logfiles given these instructions (very possibly user error on following the instructions)

Additional contextual elements

No response

rlcolburn avatar Sep 28 '23 04:09 rlcolburn

This problem cannot be reproduced. It is absolutely necessary to provide the log files, which certainly contain the cause of the problem.

Have you tried reinstalling the application?

nroduit avatar Sep 28 '23 17:09 nroduit

I have the same problem on a MacBook running Mojave 10.14 (32 bit). Weasis was installed today using the latest version. When Weasis is launched, it crashes without showing any screen.

I am not familiar with locating and sending the log files, as requested of the Original Poster.

Doxxie avatar Sep 28 '23 18:09 Doxxie

Not sure if this is related, but I experience the same on Fedora 38, using flatpak.

flatpak run io.github.nroduit.Weasis produces the following output:

weasis.log

The problem seems to be something related to X11 and Wayland:

java.awt.HeadlessException: No X11 DISPLAY variable was set, or no headful library support was found, but this program performed an operation which requires it,

I found this issue: https://github.com/dbeaver/dbeaver/issues/21299 that is also very recent and could be related.

julKali avatar Sep 29 '23 09:09 julKali

Please don't post new problems here, but open a new issue so that readers can follow up on a single topic.

@julKali See https://github.com/nroduit/Weasis/issues/449#issuecomment-1655036360, https://github.com/nroduit/Weasis/issues/462#issuecomment-1691661673 and https://github.com/nroduit/Weasis/issues/303#issuecomment-1689986225

@Doxxie Please take a look at the package specifications for download. There are no more updates for this system since 2019. The majority of libraries no longer offer 32-bit builds and this is also the case for Weasis.

image

nroduit avatar Sep 29 '23 17:09 nroduit

This problem cannot be reproduced. It is absolutely necessary to provide the log files, which certainly contain the cause of the problem.

Have you tried reinstalling the application?

The instructions provided for getting the logfiles appear to be steps to take within the app - which i'm not able to do beacuse it doesnt stay open long enough to do anything. Is there another way to get the requested information?

I have tried reinstalling multiple times, both from microsoft store and from weasis site itself.

rlcolburn avatar Sep 30 '23 23:09 rlcolburn

Be careful not to install both versions at the same time.

The log file is located in <user.home>/.weasis/log, where <user.home> is the path of the current user (e.g. C:\Users\user1).

nroduit avatar Oct 01 '23 07:10 nroduit

boot-0.0.log

Thanks. boot log attached. note: did not install both at the same time.

rlcolburn avatar Oct 01 '23 07:10 rlcolburn

According to the logs, the application starts up correctly. As the window is not visible, try manually activating the application log (default.log) by following these instructions:

  1. Close the application (verify in Task Manager that no Weasis process is running)
  2. Edit the text file "C:\Users\ryanl.weasis\preferences\ryanl\default\weasis.properties"
  3. Replace org.apache.sling.commons.log.file.activate=false with org.apache.sling.commons.log.file.activate=true and save it
  4. Run again the application
  5. Get the default.log file

nroduit avatar Oct 01 '23 14:10 nroduit

i followed steps 1-4 and got the same behavior (it appears to start up, and once its done launching it immediately quits/disapears).
step 5: default log file - default.log

rlcolburn avatar Oct 02 '23 06:10 rlcolburn

According to the logs, the application starts up normally and does not crash. The application window should be visible.

Is there some kind of hidden screen or workspace management? I've never seen a similar situation.

Is there any other particular element? virtualization context, antivirus blocking the application...

nroduit avatar Oct 05 '23 06:10 nroduit

It does open, and is visible as it loads and opens, but then when it seems to be done opening, <1s later, it disapears (with out any interaction from me, or any indication why). I'm just as confused as you.

rlcolburn avatar Oct 13 '23 06:10 rlcolburn

Has Weasis ever worked on this operating system? Do you have or have you had several screens?

Please check the file <user.home>/.weasis/data/weasis-core/persistence.properties for properties starting with last.window or screen.

You can also try deleting the folder <user.home>/.weasis.

nroduit avatar Oct 14 '23 07:10 nroduit

Due to the lack of recent activity, we are closing this issue for now. However, if you have any new information or updates related to this bug, please feel free to reopen it.

nroduit avatar Mar 16 '24 07:03 nroduit