Greetings, I have the V4 version of this board (several of them actually) and am experiencing the same issue. As suggested above, I built from master (commit 0242407) and see the same result as tobymurray:

Error: flash chip not supported, flash id: 0xff

Why are you running this on windows server? Windows server should natively support all the features of this program.

Hi! I'm having some issues getting OrbTk to behave. I'm trying to build a front-end for a program which will "encrypt" files. (Ok, it's not planned to be excellent encryption; this is meant to be a class project demonstrating things in Rust, so this isn't meant to be a super robust encryption system. That's all beside the point, though.)

I'm struggling with getting the text to update in my program in response to a message. I'm really confused because otherwise, everything seems to be working. I've gotten almost the exact same logic working in a watered-down example program, but... that hasn't helped much.

At the moment, when I run it, I get this after dragging and dropping the highlighted file in. I want the "No file" text to change to the file's path. (Ultimately it will change to the file's name, but that comes later.)

This is the simplified example which does work. It's based on the OrbTk example with multithreading, except I played with it some.

This is the project I am working on. In retrospect I should have just uploaded my repo to GitHub; I'll do that if I keep having issues.

Describe the bug I cannot run the cargo-node versions with the commands provided in the Readme.md. I have following error message:

[luminouslizard@lumi orbtk-develop]$ cargo node run --target android --example showcase     

install wasm2js
npm WARN checkPermissions Missing write access to /usr/lib/node_modules
npm ERR! code EACCES
npm ERR! syscall access
npm ERR! path /usr/lib/node_modules
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, access '/usr/lib/node_modules'
npm ERR!  [Error: EACCES: permission denied, access '/usr/lib/node_modules'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/lib/node_modules'
npm ERR! }
npm ERR! 
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR! 
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/luminouslizard/.npm/_logs/2020-11-26T21_42_19_959Z-debug.log

If I run the command with sudo (to give the permission), following message is displayed: error: no override and no default toolchain set

To Reproduce The native desktop version works perfect. Following the steps provided in the Readme.md. I installed cargo-node, NodeJS and npm.

Desktop:

• OS: Linux 5.9.10 Manjaro KDE
• Browser Firefox 83.0
• rustc 1.48.0 (7eac88abb 2020-11-16)
• rustup 1.22.1 (b01adbbc3 2020-07-08)
• NodeJS 15.2.1-1
• npm 6.14.8-2

Seems there is a PR already that allows disabling this feature #61

hi running on windows server 2019, 10.0.17763.1613 version of DLL is not supported... Any help please ? thx !

Hello to all. I'm windows insider on release preview channel and i received silently an update to 19042.662. So the last rdpwrap.ini stopped working. I thought i'd let everybody know.

I have found a potential workaround for this problem.

<Layout on realize=|l| { l.connect_draw(draw_layout); Message::None } />

I just added a dummy message because the update function isn't supposed to do anything with it I think.

I think the downside of this is that the draw callback can't send a message to the update function. So the procedural Cairo drawing code will just live in its own little bubble. Coming to think of it, it also can't access the state, which makes it kind of useless beyond drawing hello world?

Patching vgtk as follows removes the documentation stuff. No idea what the implications of that are, but fixes my immediate problem.

[dependencies.gtk]
version = "0.9.0"
features = ["v3_20"]

I'm going completely nuts over this one. How to reproduce:

cargo generate --git https://github.com/bodil/cargo-template-vgtk
cd somewhere
# optionally update to vgtk to 0.3
cargo build

error: failed to run custom build command for `gdk-pixbuf v0.9.0`

Caused by:
  process didn't exit successfully: `/home/pepijn/code/asic/tester/target/debug/build/gdk-pixbuf-6ab202b0be096025/build-script-build` (exit code: 101)
  --- stderr
  thread 'main' panicked at 'Doc comments cannot be written everywhere', /home/pepijn/.cargo/registry/src/github.com-1ecc6299db9ec823/rustdoc-stripper-0.1.16/src/strip.rs:670:38
  stack backtrace:
     0: std::panicking::begin_panic
               at /home/pepijn/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:505
     1: stripper_lib::strip::strip_comments
               at /home/pepijn/.cargo/registry/src/github.com-1ecc6299db9ec823/rustdoc-stripper-0.1.16/src/strip.rs:670
     2: lgpl_docs::purge::{{closure}}
               at /home/pepijn/.cargo/registry/src/github.com-1ecc6299db9ec823/gtk-rs-lgpl-docs-0.1.18/src/lib.rs:91
     3: stripper_lib::utils::check_path_type
               at /home/pepijn/.cargo/registry/src/github.com-1ecc6299db9ec823/rustdoc-stripper-0.1.16/src/utils.rs:95
     4: stripper_lib::utils::do_loop_over_files
               at /home/pepijn/.cargo/registry/src/github.com-1ecc6299db9ec823/rustdoc-stripper-0.1.16/src/utils.rs:52
     5: stripper_lib::utils::loop_over_files
               at /home/pepijn/.cargo/registry/src/github.com-1ecc6299db9ec823/rustdoc-stripper-0.1.16/src/utils.rs:31
     6: lgpl_docs::purge
               at /home/pepijn/.cargo/registry/src/github.com-1ecc6299db9ec823/gtk-rs-lgpl-docs-0.1.18/src/lib.rs:91
     7: build_script_build::manage_docs
               at ./build.rs:13
     8: build_script_build::main
               at ./build.rs:2
     9: core::ops::function::FnOnce::call_once
               at /home/pepijn/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:227

I'd just report a bug with gdk-pixbuf, but if I only add gdk-pixbuf = "0.8.0" to my Cargo.toml it works fine. I did have this working a couple of days ago, so I have absolutely no clue what is going on. I updated to vgtk = "0.3.0" which in some weird order of operations made it work earlier today, but can't reproduce.

The bug seems to be related to some weird documentation generation thing deep in the bowels of gtk. I'd be more than happy to just not have it do any documentation stuff...

Does anybody have ini file for this build 10.0.17763.1577 that works?

Thanks! I used one of the ini you've send! now its working!

That is a windows version. Most of the ini files should support that, like asmtrons and affinityv's files below. But to be sure, run rdpconf.exe and look at the version number listed to the right of the 'Service State: running' label. Then search through your chosen .ini file to make sure it is there.

https://github.com/asmtron/rdpwrap/blob/master/res/rdpwrap.ini https://github.com/affinityv/INI-RDPWRAP/blob/master/rdpwrap.ini

On Wed, 25 Nov 2020 at 21:49, shanialisar [email protected] wrote:

Does anybody have ini file for this build 10.0.17763.1577 that works?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/stascorp/rdpwrap/issues/1214, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMCGIV76OVIBT7WFIG4I6DSRTVK3ANCNFSM4UCJI5KA .