GodinRaider Comments - Answer Overflow

GodinRaider

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

PS C:\Users\Godin\AppData\Roaming\HotSpot\elgato-streamdeck\examples\simple> cargo run
   Compiling elgato-streamdeck v0.8.0 (C:\Users\Godin\AppData\Roaming\HotSpot\elgato-streamdeck)
   Compiling simple v0.0.0 (C:\Users\Godin\AppData\Roaming\HotSpot\elgato-streamdeck\examples\simple)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.21s
     Running `target\debug\simple.exe`
Akp153E B1D3D40E374D 4128
thread 'main' panicked at src/main.rs:20:124:
called `Result::unwrap()` on an `Err` value: HidError(HidApiError { message: "Get Input/Feature Report DeviceIoControl: (0x00000001) Неверная функция." })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\simple.exe` (exit code: 101)

PS C:\Users\Godin\AppData\Roaming\HotSpot\elgato-streamdeck\examples\simple> cargo run
   Compiling elgato-streamdeck v0.8.0 (C:\Users\Godin\AppData\Roaming\HotSpot\elgato-streamdeck)
   Compiling simple v0.0.0 (C:\Users\Godin\AppData\Roaming\HotSpot\elgato-streamdeck\examples\simple)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.21s
     Running `target\debug\simple.exe`
Akp153E B1D3D40E374D 4128
thread 'main' panicked at src/main.rs:20:124:
called `Result::unwrap()` on an `Err` value: HidError(HidApiError { message: "Get Input/Feature Report DeviceIoControl: (0x00000001) Неверная функция." })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\simple.exe` (exit code: 101)

Its after I reupload elgato-streamdeck and change PID

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

Great! I'll be looking forward to it!

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

Compiling elgato-streamdeck v0.7.1 (C:\Users\Godin\AppData\Local\OpenDeck\elgato-streamdeck)
   Compiling simple v0.0.0 (C:\Users\Godin\AppData\Local\OpenDeck\elgato-streamdeck\examples\simple)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.55s
     Running `target\debug\simple.exe`
Akp153 3257D40E374D 4128
thread 'main' panicked at src/main.rs:20:124:
called `Result::unwrap()` on an `Err` value: HidError(HidApiError { message: "Get Input/Feature Report DeviceIoControl: (0x00000001) Неверная функция." })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\simple.exe` (exit code: 101)

Compiling elgato-streamdeck v0.7.1 (C:\Users\Godin\AppData\Local\OpenDeck\elgato-streamdeck)
   Compiling simple v0.0.0 (C:\Users\Godin\AppData\Local\OpenDeck\elgato-streamdeck\examples\simple)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.55s
     Running `target\debug\simple.exe`
Akp153 3257D40E374D 4128
thread 'main' panicked at src/main.rs:20:124:
called `Result::unwrap()` on an `Err` value: HidError(HidApiError { message: "Get Input/Feature Report DeviceIoControl: (0x00000001) Неверная функция." })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: process didn't exit successfully: `target\debug\simple.exe` (exit code: 101)

This is when I inserted 0x0300 and 0x1020. And what showed without errors last time is not what we need? Or should there be a different result on the command line?

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.12s
     Running `target\debug\simple.exe`

    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.12s
     Running `target\debug\simple.exe`

That's what happened after I started the command accepting the changes. The running/restarted OpenDeck was not affected. The device itself behaves the same way with the screensaver

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

/// Vendor ID of Ajazz Stream Deck
pub const AJAZZ_VENDOR_ID: u16 = 0300;

/// Product ID of Ajazz Stream Deck AK153
pub const PID_AJAZZ_AKP153: u16 = 1020;

/// Vendor ID of Ajazz Stream Deck
pub const AJAZZ_VENDOR_ID: u16 = 0300;

/// Product ID of Ajazz Stream Deck AK153
pub const PID_AJAZZ_AKP153: u16 = 1020;

Like this? I saved the file, then executed the "cargo run" command in examples/simple again. This is the result that came out

warning: variable does not need to be mutable
  --> src/main.rs:18:21
   |
18 |                 let mut device = StreamDeck::connect(&hid, kind, &serial).expect("Failed to connect");
   |                     ----^^^^^^
   |                     |
   |                     help: remove this `mut`
   |
   = note: `#[warn(unused_mut)]` on by default

warning: `simple` (bin "simple") generated 1 warning (run `cargo fix --bin "simple"` to apply 1 suggestion)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.11s
     Running `target\debug\simple.exe`

warning: variable does not need to be mutable
  --> src/main.rs:18:21
   |
18 |                 let mut device = StreamDeck::connect(&hid, kind, &serial).expect("Failed to connect");
   |                     ----^^^^^^
   |                     |
   |                     help: remove this `mut`
   |
   = note: `#[warn(unused_mut)]` on by default

warning: `simple` (bin "simple") generated 1 warning (run `cargo fix --bin "simple"` to apply 1 suggestion)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.11s
     Running `target\debug\simple.exe`

No changes. I see that in the code above it is suggested to run with the command "cargo fix --bin "simple"". Is it worth trying to do it?

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

VID_0300&PID_1020 Isn't that it?

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

Yeah.

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

The screen saver with the Ajazz logo is still displayed. If you press any button, the screens go off. If you press again, the screensaver appears. In the OpenDeck, it also writes "No devices detected"

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

 warning: variable does not need to be mutable
  --> src/main.rs:18:21
   |
18 |                 let mut device = StreamDeck::connect(&hid, kind, &serial).expect("Failed to connect");
   |                     ----^^^^^^
   |                     |
   |                     help: remove this `mut`
   |
   = note: `#[warn(unused_mut)]` on by default

warning: `simple` (bin "simple") generated 1 warning (run `cargo fix --bin "simple"` to apply 1 suggestion)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.11s
     Running `target\debug\simple.exe`

 warning: variable does not need to be mutable
  --> src/main.rs:18:21
   |
18 |                 let mut device = StreamDeck::connect(&hid, kind, &serial).expect("Failed to connect");
   |                     ----^^^^^^
   |                     |
   |                     help: remove this `mut`
   |
   = note: `#[warn(unused_mut)]` on by default

warning: `simple` (bin "simple") generated 1 warning (run `cargo fix --bin "simple"` to apply 1 suggestion)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.11s
     Running `target\debug\simple.exe`

31 replies

OOpenDeck

•Created by was on 10/4/2024 in #forum

Segmentation fault using an Ajazz AKP153

31 replies

Gaming

Programming