Interface elements don't work when using secondary monitor

[rctaylor157]

Please include the following information.

1. Flowblade version (Help->About):
   Flowblade v2.10

2. MLT version (Help->Runtime Environment):
   MLT v7.17.0

3. Your distribution (Ubuntu, Debian, Mint etc.):
   Manjaro

4. If possible, try to provide step-by-step instructions on how to reproduce the issue. From developer point of view this is the easieast way to understand what is happening.:
   If I have Flowblade open on the secondary monitor of a dual-monitor system, text boxes and other interface elements will not work. If I move the window back to the primary monitor (without closing Flowblade) they will work again.

[jliljebl]

Thanks, will test. I don't normally use 2 monitors and the setup I have for testing 2 monitor issues is a bit annoying put together, so it might take 'till next week to get back on this.

[rctaylor157]

Okay! I've been using it more this morning and noticed a few other situations where it tends to happen:

1. after one or both of the windows have been minimized
2. occasionally it seems to happen if I spend a long time in another program like audacity or the browser (even if I didn't minimize Flowblade)

[jliljebl]

For the life of me I couldn't remember how I got the 2 monitor thing working last time with the cables I've got. I have a new laptop battery in order and after that comes (early November I think) I believe I can give this another go. I'll post more comments after that.

[rctaylor157]

Another theory: it might be related to using more than one workspace. The actual editor is on the screen which has workspaces, while the clip monitor is on the secondary screen which isn't tied to any one workspace.

[jliljebl]

Ok, got this tested but could not reproduce.

Which Desktop Environment you are using?

I'm running Gnome Shell. Manjaro seems to offer multiple Desktop Environments so if we know which DE you have we may be able to narrow the problem to either DDE or OS + DE combination.

[jliljebl]

Also I ported Flowblade to use Gtk.Application main loop since 2.10, and I did not test this Issue prior to that, so it is possible that this has been fixed by that. I'll ask for retest on 2.12.

[rctaylor157]

I am using GNOME. Let me know what I can do to help narrow down the cause!

[raphraph]

I seem to run into the same problem...

(My environment :
Flowblade version : v2.14
MLT version: MLT v7.23.0
Your distribution : Ubuntu 22.04 LTS)

I have a semi-freeze where some menus are working, but not others.
For example I can't interact anymore with the "media" window (no tab of this window respond) or with the tracks in the bottom window. If I open a media file via the Project menu it does not do anything.
However I can save the project in its "frozen" state, so I'm not loosing anything... but I need to restart flowblade.

I have two monitors but the problem occurs on both indifferently.
I'm running wayland (I saw an open isssue about that, but I didn't check before installing, and the software seemed to work fine except for this).

I'll be glad to give more input if needed.