Bismuth fails when using binary installation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bismuth (Debian) |
New
|
Unknown
|
|||
bismuth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
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://<email address hidden>
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: <email address hidden>
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:/
file://
kwin_x11[3514]: import "../code/index.mjs" as Bismuth
kwin_x11[3514]: ^,
file://
Unexpected token `{'
kwin_x11[3514]: static {
kwin_x11[3514]: ^,
file://
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
tags: | added: noble |
Changed in bismuth (Debian): | |
status: | Unknown → New |