Zebra2 settings are unclickable (on Wayland)

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS
Zebra

Post

I recently purchased Zebra2 in the Bitwig u-he Promotion and I'm quite happy with the synthesizer, at least in terms of performance and sound design capabilities.
But there is an annoying issue, I can't click on the GUI settings (eye symbol) or on any of the entries in the settings menu (gear symbol).

I attached a screen recording that demonstrates the issue (webm extensions are not allowed :neutral: ). Here are the links:
- Zebra2 with unclickable settings https://i.fluffy.cc/hNn4jBsN3JCrJ6PZBLN ... Rhc3n.webm
- Zebra2 where everything is fine: https://i.fluffy.cc/d2MkhcT7LgsjDCthd5C ... T7WXw.webm

The strange thing is that the same Zebra2 build works fine on my desktop but not on my laptop. Both machines are running the same Linux kernel and distribution as well as the same Bitwig Version.

Here are some details:
- Zebra2 build 4458
- Arch Linux Kernel 4.13.2
- Bitwig 2.2-Beta8
- Gnome 3.24.3

I also started bitwig from the terminal in order to see some debug output but there is nothing shown. Any ideas how to solve this issue?

TL;DR Installed Zebra2 on two machines with nearly identical setup but can only change (click on) Zebra's GUI settings in one of the two.
Last edited by klingt.net on Thu Oct 05, 2017 8:28 pm, edited 1 time in total.

Post

It looks like others are having Linux-related menu problems. I know you're not running Ubuntu but maybe some of the underlying library versions are the same. Here's part of that thread.

http://www.kvraudio.com/forum/viewtopic ... 8#p6866418

Is it possible you don't have exactly the same libraries and X11 configuration? It's possible the drm for your desktop doesn't aggravate the underlying issue here.
Feel free to call me Brian.

Post

@bmrzycki Thanks for the link, I will take a look into the thread.
> Is it possible you don't have exactly the same libraries and X11 configuration?
Yeah, this is possible but at least the GUI stuff is up to date and in the same verison.
I should also mention that both (not true) machines are running Gnome on Wayland.

Solved: The machine where the GUI settings are working runs Gnome on Xorg and *not* on Wayland. So, the wayland x11 bridge causes the problem.

Post

Yay! I'm not surprised it was related to a bridge. :) Happy Zebra-ing!
Feel free to call me Brian.

Post Reply

Return to “u-he”