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

Blank page when starting the stand alone clinet #834

Closed
2 of 3 tasks
schiessle opened this issue Nov 8, 2022 · 12 comments · Fixed by #846
Closed
2 of 3 tasks

Blank page when starting the stand alone clinet #834

schiessle opened this issue Nov 8, 2022 · 12 comments · Fixed by #846
Assignees
Labels
App Issue affects the standalone application bug

Comments

@schiessle
Copy link

schiessle commented Nov 8, 2022

Prerequisites

  • Tried the most recent nightly build
  • Checked if your issue is already reported.
  • Answered all the questions in this template (Or provide a working crystal ball).

What happened?

I use the AppImage of the stand-alone Sieve editor, version 0.6.1 on Fedora 36

When I start the client I get following error in the terminal:

[30984:1108/125843.879887:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

and the client starts with a empty windows:

grafik

I had this issue from the beginning, in the past restarting it multiple time solved the problem in the sense that at some point in time the complete UI was shown and I could use it. But since some weeks now I can restart it as often as I want, I have always the same result

If I use version 0.6.0 it works (with the same error message, so this should not be the root of the issue).

What did you expect to happen?

Sieve client starts with all UI elements and I can use it.

Logs and Traces

That's the only thing I see in the terminal when I start the client:

[30984:1108/125843.879887:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

If there are additional log files I'm happy to provide them. Just let me know where I can find them.

Screenshots

see above

Which Version

Include information about your system, server and most important if it is about the app or webextension.

  • Standalone app version 0.6.1 (latest version from the download page)
  • Operating system: Fedora 36
@shardrunner
Copy link

I have the same issue with Win 11 for some time now.
I always have to start it multiple times to actually show anythin.

@hlinden
Copy link

hlinden commented Nov 28, 2022

I have the same issue with Debian bookworm/sid right now. The AppImage starts, outputs this to the console:

[harald@dreiraumrakete sieveeditor]$ ./sieve-0.6.1-linux-x64.AppImage 

(AppImageLauncher:3337729): GLib-CRITICAL **: 13:41:46.070: g_file_test: assertion 'filename != NULL' failed

(AppImageLauncher:3337729): GLib-CRITICAL **: 13:41:49.480: g_dir_read_name: assertion 'dir != NULL' failed

(AppImageLauncher:3337729): GLib-CRITICAL **: 13:41:49.481: g_dir_close: assertion 'dir != NULL' failed

** (AppImageLauncher:3337729): WARNING **: 13:41:49.487: No icons found in AppDir/usr/share/icons. Using .DirIcon as fallback
gtk-update-icon-cache: The generated cache was invalid.
[3337842:1128/134154.583019:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[3337794:1128/134154.630835:ERROR:backend_impl.cc(2028)] Invalid file version or magic
[harald@dreiraumrakete sieveeditor]$ 

and that's that, then it just sits there:

Bildschirmfoto vom 2022-11-28 13-45-41

@davemosk
Copy link

davemosk commented Dec 2, 2022

I'm having the same issue on Ubuntu 20.04

@stale
Copy link

stale bot commented Dec 17, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 17, 2022
@rhansen
Copy link

rhansen commented Dec 17, 2022

ditto (unstale)

@thsmi thsmi self-assigned this Dec 18, 2022
@stale stale bot removed the stale label Dec 18, 2022
@thsmi thsmi added bug App Issue affects the standalone application labels Dec 18, 2022
@thsmi thsmi linked a pull request Dec 18, 2022 that will close this issue
@thsmi
Copy link
Owner

thsmi commented Dec 18, 2022

Looks so far as if there are at least two issues with the same effect.

The electron in the release is rather old and has known incompatibilities with some graphics card drivers. Which is fixed in newer releases, thus I updated the dependencies.

Further more I stumbled upon a race when initializing the window. The iframe containing the account data could be loaded before the outer window hosting the tabs was completed. Thus the initial handshake between the two windows get out of sync. It is fixed in this branch, the account windows will now be loaded earliest after the main window is initialized.

The nightly build for this branch can be found here for the next ten days:

Please give it a try and check if the it resolves your issues.

@schiessle
Copy link
Author

Thanks for looking into it! Sounds promising, I will give the nightly build a try during the next few days.

@shardrunner
Copy link

The nightly build seems to have fixed it for me.
It just started correctly 4/4 for times.
Thanks a lot for the great software!

@anatoli26
Copy link

@thsmi do you have plans to release a new version with all recent changes included?

@CRCinAU
Copy link

CRCinAU commented Aug 7, 2023

Yeah, I just came across this too after having the same happen on Fedora 38...

@davemosk
Copy link

davemosk commented Aug 7, 2023

@CRCinAU This fixed it for me: https://github.com/thsmi/sieve/files/10269440/sieve-0.6.1-build_by_VS.xpi.zip (see #763 for more details) - but note that TB115 seems to break it again.

@dennym
Copy link

dennym commented Jan 25, 2024

Also happening for me and the nightly artifacts are not available anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App Issue affects the standalone application bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants