Aufschlauer

Well, between ewmh 0.1.4 and 0.1.5 there is at least a change in return value: When you call ``` self.ewmh.getWmName(l_window) ``` you get with 0.1.4 a string like ``` "Window...

> Have you solved it? I use the work around: Open link the same window.

It seems to be a question related to [ungoogled-chromium-debian](https://github.com/ungoogled-software/ungoogled-chromium-debian).

Well, on Debian 11 it is just working fine so far: ``` [194/194] LINK gn + ./out/Default/gn gen out/Default --fail-on-unused-args Done. Made 16654 targets from 2784 files in 6294ms +...

Well, all succeed: ``` 1 warning generated. [49906/49906] LINK ./chrome ``` ``` $ ./package.sh +++ readlink -f ./package.sh ++ dirname /root/ungoogled-chromium-portablelinux/package.sh + _root_dir=/root/ungoogled-chromium-portablelinux ++ cat /root/ungoogled-chromium-portablelinux/ungoogled-chromium/chromium_version.txt + _chromium_version=98.0.4758.80 ++ cat...

Well, for steps 1 and 2 I can't help then: I've reused a docker container from a previous build. Regarding docker package: It *is* a recent version, but not the...

The linker error can be fixed by adding to `build.sh`: ``` +export LDFLAGS+="-resource-dir=${_llvm_resource_dir} -B${LLVM_BIN}" ```

Since I still can not build, I tried to get closer: ```bash $ file make_top_domain_list_variables make_top_domain_list_variables: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for...

> @Aufschlauer is this issue still relevant or may i close it? @clickot No, just go ahead and close this one.

> @Drugoy , @Aufschlauer may i close this issue or is it still relevant somehow? @clickot No, just go ahead and close this one.