Re: Possible rust issue on -current

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On Thu, 20 Aug 2020 at 05:10, Tobias Nygren <tnn%netbsd.org@localhost> wrote:
>
> On Thu, 20 Aug 2020 05:04:37 +0200
> Tobias Nygren <tnn%NetBSD.org@localhost> wrote:
>
> > This doesn't sound like a rust problem but rather some crate is trying
> > to do something nonportable while attempting to fix a portability
> > issue. If it is really important to detect at run time if some code
> > runs on the main thread (doubtful) you should patch the code to mark
> > the main thread as such on startup with one of the available portable
> > thread local storage APIs. Alternatively you can patch out the entire
> > check from the offending create with a pkgsrc patch if you know for
> > sure it's initialization is running on the main thread.
>
> The upstream project created a tentative fix for this issue already.
>
> https://github.com/rust-windowing/winit/pull/1664/commits/b1a90fd5c52ac2aff45558ff932a61892859859e
>
> I added it to wip. The package seems to works fine for me now.
> Shows a terminal window.

This modification also solved the dynamic libraries problem. However,
I am still getting

thread 'main' panicked at 'Failed to open input method: PotentialInputMethods {
    xmodifiers: None,
    fallbacks: [
        PotentialInputMethod {
            name: "@im=local",
            successful: Some(
                false,
            ),
        },
        PotentialInputMethod {
            name: "@im=",
            successful: Some(
                false,
            ),
        },
    ],
    _xim_servers: Err(
        GetPropertyError(
            TypeMismatch(
                0,
            ),
        ),
    ),
}', /usr/pkgsrc/lang/rust/work/rustc-1.44.1-src/src/libstd/macros.rs:13:23
stack backtrace:
   0: <std::sys_common::backtrace::_print::DisplayBacktrace as
core::fmt::Display>::fmt
   1: core::fmt::write
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
             at
/usr/pkgsrc/lang/rust/work/rustc-1.44.1-src/src/libstd/panicking.rs:438
   6: winit::platform_impl::platform::x11::EventLoop<T>::new
             at
/usr/pkgsrc/lang/rust/work/rustc-1.44.1-src/src/libstd/macros.rs:13
   7: winit::platform_impl::platform::EventLoop<T>::new_x11_any_thread
             at
/usr/pkgsrc/wip/alacritty/work/vendor/winit-0.22.2/src/platform_impl/linux/mod.rs:594
   8: winit::platform_impl::platform::EventLoop<T>::new_any_thread
             at
/usr/pkgsrc/wip/alacritty/work/vendor/winit-0.22.2/src/platform_impl/linux/mod.rs:560
   9: winit::platform_impl::platform::EventLoop<T>::new
             at
/usr/pkgsrc/wip/alacritty/work/vendor/winit-0.22.2/src/platform_impl/linux/mod.rs:533
  10: winit::event_loop::EventLoop<T>::with_user_event
             at
/usr/pkgsrc/wip/alacritty/work/vendor/winit-0.22.2/src/event_loop.rs:129
  11: alacritty::main
             at alacritty/src/main.rs:81
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.


with

$  locale
LANG="en_GB.UTF-8"
LC_CTYPE="en_GB.UTF-8"
LC_COLLATE="C"
LC_TIME="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_ALL=""

No idea why; tested with xfce4 and xmonad.

>
> -Tobias

Chavdar


-- 
----