Public bug reported: This is the same error that was reported to Debian. However, I am encountering this issue when using Ubuntu.
OS Version: Ubuntu 24.04 LTS Package: kwin-bismuth Version: 3.1.4-4build2 https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1970982.html Following is a direct copy from the other bug report by Petr Gajdůšek, which matches my own experience for what the syslog contains. I have not tried his mentioned solution of recreating the package using dpkg- buildpackage ---- Justification: renders package unusable X-Debbugs-Cc: petr.gajdu...@egston.com Dear Maintainer, After upgrade to 3.1.4-4+b1 kwin-bismuth no more works with following error in syslog: kwin_x11[3514]: kwin_scripting: Component failed to load: (file:///usr/share/kwin/scripts/bismuth/contents/ui/main.qml:5:1: Script file:///usr/share/kwin/scripts/bismuth/contents/code/index.mjs unavailable kwin_x11[3514]: import "../code/index.mjs" as Bismuth kwin_x11[3514]: ^, file:///usr/share/kwin/scripts/bismuth/contents/code/index.mjs:795:10: Unexpected token `{' kwin_x11[3514]: static { kwin_x11[3514]: ^, file:///usr/share/kwin/scripts/bismuth/contents/code/index.mjs:796:9: Expected token `(' kwin_x11[3514]: this.id = "MonocleLayout"; kwin_x11[3514]: ^) The resulting JS oviously uses ES2022 features despite the project's tsconfig.js has target set to es2016. After rebuilding the kwin-bismuth package locally on my system (just dpkg- buildpackage), it works just fine. Thank you, Petr ** Affects: bismuth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072165 Title: Bismuth fails when using binary installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bismuth/+bug/2072165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
