James Cuzella

> Could it be that you are using the `next` branch? Yes, in effect I'm using the Wayland forked version of `rofi` that was based on the `next` branch of...

From the perspective of user-friendly per-display configuration, the use-case behind this PR is a great idea. It would unify the configuration matching behavior of output specifiers for `swaylock` with `sway`,...

> you are not using this repository. you are using @lbonn his fork. Yes, the fixes will have to be merged into the [`lbonn/rofi`][1] fork from this repo (`git merge...

> How can I ensure that dragon-drop is always started under X11? It should be possible for any GTK/GDK-based app to use: export GDK_BACKEND=x11 # Run your app in this...

Related / duplicate issue: #1010

Same issue on MacOS Monterey `12.7.6`. This is an overly pessimistic version constraint issue, due to the dependencies specified in the `.gemspec`, so it will affect any OS with versions...

> So are you saying this cannot be fixed here and needs an upstream fix? Ideally, yes upstream Vagrant should update their version of `excon` gem to avoid straddling the...

> It seems that now (with Vagrant 2.4.3) the plugin installs properly again. I can verify this is the case also on **macOS Monterey**: ```console vagrant plugin install vagrant-libvirt Installing...

Issue still present in Electron `33.0.0` with Chromium `v130.0.6723.59` on macOS `12.7.6` Monterey. Can reproduce also in Google Chrome version `130.0.6723.59`: ```console [32323:259:1018/011918.672903:ERROR:gl_display.cc(497)] EGL Driver message (Error) eglQueryDeviceAttribEXT: Bad attribute....

This may be fixed in newer versions of RVM / Ruby. Closing as stale, also due to Ruby `2.3.x` being [End of Life (EoL) as of 31 Mar 2019][1]. (Also,...