Bible Analyzer 5.6 beta (Linux)

[Brother Mike]

Although I did not look too deeply into the matter when I was having the above issue, it seems to be more related to the WEBKIT having issues than anything else.

I did not try under Wayland, but all the articles I looked at seems to connect to NVIDIA GPUs.

I have just migrated over to Debian 12 from Ubuntu 24.04. After doing so, the same type of issues arose with BA, as well as the system "Accounts" dialog. Both were blank and black. When adding the above to the /etc/environment file, both issues were corrected. Otherwise, BTW BA has been performing quite well under Debian 12.

Now, whether Wayland has some of the same compositor issues, or if you are using NVIDIA, not sure where the issue lies. There are quite a bit of references to these online. Plus I do not know to what extent Tim wants to travel right now with Wayland compatibility in his development flow, or what he may have already been doing in that regard.

For my very humble opinion, Wayland is still just too immature to rely on from what I have experienced in logging on and experimenting. I am sure the time will come, but may be a while.

[Bink]

Thank you Tim and Brother Mike, that has provided clarity.

I am indeed using a Nvidia GPU, so I've tested again under X11, to try and isolate the issue to either Nvidia or Wayland.

I can confirm, that under X11, BibleAnalyzer launches without issue, and without the "WEBKIT_DISABLE_DMABUF_RENDERER" environmental variable defined, so in my case at least, it would seem to be an issue isolated to Wayland.

For my very humble opinion, Wayland is still just too immature to rely on from what I have experienced in logging on and experimenting. I am sure the time will come, but may be a while.

I agree, I frequently encounter issues with it. I feel like I'm constantly using beta software. However, Arch being a rolling release, it propels you along ready or not X11 is working again for me at the moment, but next update, it might stop working again, as it has very much been pushed to the back-burner of development. It's a difficult time of transition for Linux. The new is not yet ready for mainstream, the old is hanging on like a piece of sticky tape you can't get off your fingers.

[wmcdannell]

BA 5.6.5.04
Linux Mint Xia 22.1
Kernel 6.8.0-60-generic
GNOME 46
Ryzen 7 7730U Integrated graphics
Lenovo Yoga 6 2in1 touchscreen

Wayland:
It was easier to record a video rather than try to describe the menu problem (the menus are unusable but only on Wayland):
https://drive.google.com/file/d/1WY6x3a ... sp=sharing

I noticed 3 major problems right off the bat:
-Input menus are unusable
-occasional flashing of multiple sub-windows for different actions
-Using the touch screen to scroll any window causes flashing of multiple sub-windows and it scrolls too far every time

X11:
Menus are now usable, but touchscreen is still unusable (same issue as on Wayland). There's an additional problem only when using X11 when using the touchscreen to scroll: the on screen keyboard tries to pop-up when attempting to scroll any window (in laptop mode when that's not supposed to happen).

[Brother Mike]

from what you describe, it looks like either a compatibility issue. You are using some proprietary hardware most likely with the touch screen and on screen keyboard, as well as drivers. WebKit could enter into the mix as well.

It does not appear to be a BA issue, as the above discussed issues were not either. If you could take your touchscreen out of the mix and use a regular mouse and keyboard, that may shed some light on what id going on. Check the logs for BA as well to see if any unusual messages appear.

If you can try running BA with this on the CLI:

/opt/bibleanalyzer/ba-run.py

There may be some errors thrown by whatever is causing the problem. That is basically how I discovered mine, as well as some research in your favorite search engine.

Although my main issue above was different, I did encounter some menu issues that were resolved when I corrected the main problem. You could try putting this in your /etc/environment file:

WEBKIT_DISABLE_DMABUF_RENDERER=1

it is a work around, but for now, it does not appear the vendor is putting much effort into a perm fix. This will not cause any damage to the system, and can be removed if not needed.