-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
The display compositor is frequently crashing. Goodbye. #1025
Comments
does it work with older versions? Did it work before? |
Workaround for now: This started happening to me as well, although I'm not sure when (haven't opened Lossless-Cut in a week or two until tonight). The same version previously worked with the same setup (in the same location, same files. Nothing has changed about my lossless-cut files to my knowledge) The same error happens on the .AppImage version as well as on older versions (3.39.0) Edit: it works using Edit 2:
|
Thanks for researching. Seems like it’s fixed in newer versions of electron, but losslesscut’s still stuck on an old version due to a serious bug in >v8 #714 |
Same issue. LossLess cut version 3.43.0
Operating System: openSUSE Tumbleweed 20220218 And, like Mojavve wrote, it works with "losslesscut --no-sandbox" |
version 3.44 output just when launched and immediately crash:
|
Same error with Arch package & Appimage versions. Work with |
Just had the same issue on a fresh install of Ubuntu 22.04 using the AppImage (and also needed to install libfuse2) , using |
I think this problem will be fixed in the future when upgrading electron #714 - i will close this because there seems to also be a working workaround for the current version. |
I don't understand why this thread was closed. From my point of view, "no-sandbox" parameter is a workaround, not a fix. |
need to keep issue count down. it will probably be fixed in the future when i upgrade electron. the issue is still here for reference, but currently there's nothing actionable that i know of in order to fix it, so i closed it |
At last, it's fixed in 3.48.2 (beta!) , you must know it. Thanks |
Losslesscut 3.42.0 on Arch Linux crashes on startup.
To Reproduce
$ losslesscut Current version 3.42.0 Newest version 3.42.0 [4267:0210/232603.554463:FATAL:gpu_data_manager_impl_private.cc(1034)] The display compositor is frequently crashing. Goodbye. Trace/breakpoint trap (core dumped)
Expected behavior
Losslesscut starts up normally
Desktop (please complete the following information):
Additional context
` PID: 3857 (losslesscut)
UID: 1000 (user)
GID: 1000 (user)
Signal: 5 (TRAP)
Timestamp: Thu 2022-02-10 23:21:23 EST (2min 25s ago)
Command Line: /usr/share/losslesscut/losslesscut
Executable: /usr/share/losslesscut/losslesscut
Control Group: /user.slice/user-1000.slice/[email protected]/app.slice/app-org.kde.konsole-3e20afe2602348e098cd472b8e1ea2d4.scope
Unit: [email protected]
User Unit: app-org.kde.konsole-3e20afe2602348e098cd472b8e1ea2d4.scope
Slice: user-1000.slice
Owner UID: 1000 (user)
Boot ID: 9aceb332c9ec47adadb66429ba6e9524
Machine ID: 102328bf726a468f80bbc31305b6e509
Hostname: host
Storage: /var/lib/systemd/coredump/core.losslesscut.1000.9aceb332c9ec47adadb66429ba6e9524.3857.1644553283000000.zst (present)
Disk Size: 6.6M
Message: Process 3857 (losslesscut) of user 1000 dumped core.
The text was updated successfully, but these errors were encountered: