Won't install on Asahi Linux

[pablo03v]

OS version: Fedora Linux Asahi Remix 39 (Thirty Nine)
Browser version: 119.0 (64-bit)
Extension version: 0.3.1
Bridge version: 0.3.0 rpm

Description
Opens the Software program but then won't install it.

Steps to reproduce

1. Install Asahi Fedora 39 Gnome
2. Download the rpm version for Fedora
3. Click it
4. Opens the software program and errors

Expected behaviour
Describe the expected behaviour here.

Logs
Could not depsolve transaction; 1 problem detected:
Problem: conflicting requests

• package fx_cast_bridge-0.3.0-1.x86_64 from @commandline does not have a compatible architecture
• nothing provides ld-linux-x86-64.so.2()(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides ld-linux-x86-64.so.2(GLIBC_2.2.5)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.10)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.14)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.16)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.2.5)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.3)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.3.2)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.3.4)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.4)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.6)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.7)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libc.so.6(GLIBC_2.9)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libdl.so.2(GLIBC_2.2.5)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libm.so.6(GLIBC_2.2.5)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libpthread.so.0(GLIBC_2.2.5)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libpthread.so.0(GLIBC_2.3.2)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline
• nothing provides libpthread.so.0(GLIBC_2.3.3)(64bit) needed by fx_cast_bridge-0.3.0-1.x86_64 from @commandline

[brad]

This is because the architecture is incorrect. I managed to build the correct architecture in Asahi after making these changes

diff --git a/bridge/bin/build.js b/bridge/bin/build.js
index 88dd9ed..96784e5 100644
--- a/bridge/bin/build.js
+++ b/bridge/bin/build.js
@@ -43,7 +43,7 @@ const argv = await yargs()
 const supportedTargets = {
     win32: ["x86", "x64"],
     darwin: ["x64", "arm64"],
-    linux: ["x64"]
+    linux: ["x64", "arm64"]
 };
 if (!supportedTargets[process.platform]?.includes(argv.arch)) {
     console.error(
@@ -498,7 +498,7 @@ function packageLinuxRpm(
         mustache.render(fs.readFileSync(specPath).toString(), view)
     );
 
-    const rpmArchMap = { x86: "i386", x64: "x86_64" };
+    const rpmArchMap = { x86: "i386", x64: "x86_64", arm64: "aarch64" };
 
     spawnSync(
         `rpmbuild -bb ${specOutputPath} \

The package installs, but I'm still troubleshooting the extension's connection to the bridge

EDIT: The bridge connection works, but it doesn't see my chromecast with Google TV 😞

[pablo03v]

thanks for taking a look tho!

[fx-chun]

@brad This patch works for me! I'm able to see my display device as well. Maybe something was misconfigured with your mDNS resolution?

I haven't gotten anything actually streaming yet however; I believe the third-party casting dongle I'm testing with doesn't support anything other than the default media playback app judging from the LAUNCH_ERRORs I'm seeing in the browser console (and so YouTube doesn't cast). I'll probably try with an HTML5 video element later today.