I have to run the skip 1s configuration app in a Debian 12 container because AppImage does terrible things for a package thing that claims to "run anywhere". Anyways, it fails with this panic message:

 

[clayton@debian Downloads]$ ./skip-app_0.9.968_amd64.AppImage --appimage-extract-and-run
Gtk-Message: 16:14:44.057: Failed to load module "canberra-gtk-module"
Gtk-Message: 16:14:44.058: Failed to load module "canberra-gtk-module"
Panicked: PanicInfo { payload: Any { .. }, message: Some(`APPDIR` or `APPIMAGE` environment variable found but this application was not detected as an AppImage; this might be a security issue.), location: Location { file: "/root/.cargo/git/checkouts/tauri-9dcc2f9152472c1a/8c5fcf4/core/tauri-utils/src/lib.rs", line: 205, col: 11 }, can_unwind: true, force_no_backtrace: fntalse }

 

This Tauri bug mentions a similar failure that was apparently fixed in 1.5.0: https://github.com/tauri-apps/tauri/issues/7736

Are you using Tauri >=1.5.0 to package this app?

8 minutes ago, clayton said:

I have to run the skip 1s configuration app in a Debian 12 container because AppImage does terrible things for a package thing that claims to "run anywhere". Anyways, it fails with this panic message:

 

[clayton@debian Downloads]$ ./skip-app_0.9.968_amd64.AppImage --appimage-extract-and-run
Gtk-Message: 16:14:44.057: Failed to load module "canberra-gtk-module"
Gtk-Message: 16:14:44.058: Failed to load module "canberra-gtk-module"
Panicked: PanicInfo { payload: Any { .. }, message: Some(`APPDIR` or `APPIMAGE` environment variable found but this application was not detected as an AppImage; this might be a security issue.), location: Location { file: "/root/.cargo/git/checkouts/tauri-9dcc2f9152472c1a/8c5fcf4/core/tauri-utils/src/lib.rs", line: 205, col: 11 }, can_unwind: true, force_no_backtrace: fntalse }

 

This Tauri bug mentions a similar failure that was apparently fixed in 1.5.0: https://github.com/tauri-apps/tauri/issues/7736

Are you using Tauri >=1.5.0 to package this app?

Are you able to run it at all in the container? Is the error in the host os?

Have you tried the release candidate?

4 minutes ago, jason said:

Are you able to run it at all in the container? Is the error in the host os?

This error is from the shell in the container, not the host OS.

I'm not able to run this at all on the host OS because AppImage dynamically links to glibc and I'm using a Linux distro that uses a different libc (musl). Normally I'd work around this by either 1) finding (or packaging) the app in Flatpak, or 2) running it manually in a Debian container.

#1 seems hard to do since it would involve deconstructing your appimage thing and stuffing it into a flatpak, #2 is where I get the above failure.

 

> Have you tried the release candidate?

Yeah, it still fails, and the panic still references the same Tauri commit (9dcc2f9152472c1a). Which version of Tauri are you using? Did you happen to see the upstream Tauri bug I linked to earlier?

3 hours ago, clayton said:

This error is from the shell in the container, not the host OS.

I'm not able to run this at all on the host OS because AppImage dynamically links to glibc and I'm using a Linux distro that uses a different libc (musl). Normally I'd work around this by either 1) finding (or packaging) the app in Flatpak, or 2) running it manually in a Debian container.

#1 seems hard to do since it would involve deconstructing your appimage thing and stuffing it into a flatpak, #2 is where I get the above failure.

 

> Have you tried the release candidate?

Yeah, it still fails, and the panic still references the same Tauri commit (9dcc2f9152472c1a). Which version of Tauri are you using? Did you happen to see the upstream Tauri bug I linked to earlier?

Tauri 1.4, I did see it the link. I don't know how to solve the issue. I'm stuck with Tauri because the entire app is written in react native desktop. No other way to have a linux app without it. Tauri says they will have flatpak support in the future, and I agree, the apppack is garbage if it doesn't do the one job it's supposed to do. 

 

3 hours ago, jason said:

Tauri 1.4, I did see it the link. I don't know how to solve the issue. I'm stuck with Tauri because the entire app is written in react native desktop. No other way to have a linux app without it. Tauri says they will have flatpak support in the future, and I agree, the apppack is garbage if it doesn't do the one job it's supposed to do. 

 

Thanks for the response. Regarding Tauri, can you specify the newer version (1.5) somewhere? It should fix this bug I hit, unless there's some other new failure that looks the same.

That's good news about Tauri supporting flatpak some day, I hope they make it happen.

If there was a library or even just some very basic docs from you about how to communicate with the remote over USB (I assume HID?), then I bet other people would create alternative UIs for your remote that run natively on systems you don't want to support. The skip 1s is a really great-looking remote, at least the hardware is. The software required to use it has been really really (really) rough for me over the last year, it's easily the 1 thing I dislike about the Skip1s. Every time I want to change a button, I basically have to go on a multi-hour/day adventure like this to get the app running on my system. I'd honestly rather spend that time making a new open source app for this remote.

22 hours ago, craftyguy said:

Thanks for the response. Regarding Tauri, can you specify the newer version (1.5) somewhere? It should fix this bug I hit, unless there's some other new failure that looks the same.

That's good news about Tauri supporting flatpak some day, I hope they make it happen.

If there was a library or even just some very basic docs from you about how to communicate with the remote over USB (I assume HID?), then I bet other people would create alternative UIs for your remote that run natively on systems you don't want to support. The skip 1s is a really great-looking remote, at least the hardware is. The software required to use it has been really really (really) rough for me over the last year, it's easily the 1 thing I dislike about the Skip1s. Every time I want to change a button, I basically have to go on a multi-hour/day adventure like this to get the app running on my system. I'd honestly rather spend that time making a new open source app for this remote.

Oh that's awful and I'm so sorry it's so frustrating. Yes Linux has taken a backseat and honestly, everything has taken a backseat because of windows dumb bullshit. The amount of crap I've dealt with recently has been horrible.

But yes, of course, I have an SDK, internal documentation for all HID communication, etc. What's your architecture you're running it on. I'm behind, I need to post all the libs, but I'm going to help you first.

Hi @jason.

 

I am also having this issue. When I first bought 2 of your remotes (to go with 2 of my Flirc USB dongles) I did some terrible hacks that I can't recall to get the Skip app to work. Unfortunately I lost those hacks and I realized I want to add one extra button of functionality to my Flirc products! I'm on Linux as well and I'm under the impression all my problems would be solved if you could upgrade Tauri... Is there any chance you can update Tauri and put a new testing build out at some point?

 

As a quick aside - all my wildest HTPC dreams have come true thanks to this remote + dongle :D

Thanks for making it.

I had planned to do this but got far behind in getting manufacturing tests updated before a family trip. I killed myself so that I can get inventory again and things moving along. Work was at nearly a standstill on this while I was off. Came back with Covid, finished covid, 30 minutes later, kidney stone. Jesus christ. 

I'm trying to catch up and it's on my list of things to do shortly. I would kill to know what you did to get it to work previously.

Hey man... health first! We've had some Olympics on the TV via Firefox and I thought it would be nice to bind alt+F4 to one of the buttons on the remote I'm not using, so no big rush on my side.

 

I can't recall exactly... but it was a pretty terrible list of things. I can't promise anything but I will see if I can find some more detail in my shell + other histories.

 

Good luck with everything. Thanks again.

Oh no! I found how I got the app to run... but I think I just wiped out all my settings -_-

 

Is there a way to have the Skip app import settings from a remote?

 

I use a weird linux package manager called "nix" which is supposed to make things super reproducible. I'm not sure how easily the environment I'm working in will be for troubleshooting, though... Let me know what I can do to help you out on this.