Wayland: No autocompletion in Payee and Category

[Fiodin]

In my Installation under Ubuntu there is no autocompletion for Payee and Category anymore.

OS: Ubuntu 22.04
Version: 5.6.2

I'am missing this feature very much.

[Richard Sutton (rsutton43)]

Jens,
I am running:
 Windows 10
 Windows 11
 Ubuntu 22.04
 Mint 21
 Arch linux
 Homebank 5.6.2

I am not experiencing any of the problems you describe. I might point out that I am using Xorg on all my machines. I have never tried Wayland as I don't think it is ready for prime time.
Perhaps removing/re-installing might help.

Richard

[Maxime DOYEN (mdoyen)]

have you tried the suggestion on the bug report instruction (for wayland)

+ see 1999699

[Fiodin (dingens)]

First I uninstalled homebank and reinstalled it: no change
Second I purged it and reinstalled it: no change
Third: I started it with the GDK_BACKEND=x11 option: it worked

Now I have Wayland disabled and it is working fine. But now my calibrated monitor has weird colours...

[Fiodin (dingens)]

So,... Thank you for your help!

[Maxime DOYEN (mdoyen)]

BTW: I still do reproduce the bug reported into 1999699
but testing for auto completion with Wayland I do not have problem.

what is your case usage sequence ?

[Fiodin (dingens)]

I don't know exactly what you mean with case usage of auto completion? Do you mean something different for case usage?

The auto completion is a feature inside homebank so that a known Payee is suggested while typing in columns. This is easier than selecting it from a big list.

[Maxime DOYEN (mdoyen)]

I was asking for a complete description of what you do to reproduce exactly.
But no matter.

I think I have found a workaround I will apply.

[Maxime DOYEN (mdoyen)]

Or not finally.

So from which window you don't have autocompletion, please describe step by step what you do.

Thanks,

[Fiodin (dingens)]

OK.... I will try to do a complete description.

In Homebank and, for example, for the fields "Payee" and "Posting text", there is an auto-complete function, so that in the case of a known payee or text, everything does not have to be entered again, so a known one can be selected from a list when you start to type.

Under Wayland this function wasn't working. So, e.g. when I started to type in the first three letters of a known Payee there wasn't a list of the known Payee where I can select the right one.

I then disabled Wayland and did the same thing and there was the list of known Payee.

Does this makes it any clearer? Because it seems to me that you don't know the auto-complete function.

[Maxime DOYEN (mdoyen)]

Not ok... When you report a problem to someone, it is now behind your shoulder to see what you have doen, do you really think I don't know how autocompletion works ?!!...

So a "complete description of what you do to reproduce" is:

(and please also try to do those actions with the example file so that I can do the same action as you)

- I open HB
- I load the example file
- I open that window
- I open the XXX dialog
- I click on payee input
- I input abc
- this happen, not happen
- I expected this not that
- etc.

Thanks in advance.
Maxime.

[Fiodin (dingens)]

Yes, you are right. I didn't write a proper description, because for me some things are obvious to get to the point where you enter the payee.

Apparently I had written enough above though, as you were the one who could give the solution with the given data:
https://bugs.launchpad.net/homebank/+bug/2006456/comments/2
So my information cannot have been so incomplete.

I will now try it one more time so you hopefully can reproduce it and I am not making a joke out of it:
- Install a proper UBUNTU 20.04 and GRUB2 - probably don't use a VM -
- Then Upgrade it to 22.04 with Wayland over the shell
- (re)Start the machine, let GRUB2 do the magic for the OS selection
- Don't do anything on the Log-In Screen for selecting the window manager or another desktop, so you get UBUNTU 22.04 with Gnome and Wayland
- Log in to the OS
(- Install Homebank - Must I describe how I did that?)
- Start Homebank - and I have configured it that it uses the last file opened -
- Go into any bank account or credit card account
- settle up a new booking
- enter the first letters of a payee
- I expected to get a list of the known payee to select one
- The same (does not) happen when I enter a text at the "Posting Text" field or category

If I read this bug report from my amateurish point of view up to post 3, the problem may not be in Homebank but rather in Wayland. Because as described in post 3:
https://bugs.launchpad.net/homebank/+bug/2006456/comments/3
the problem was gone when I deactivated Wayland.

I don't know now what else I can describe or do. On my machine the problem was there when Wayland was enabled and it is gone when Wayland is disabled. So in case you can't reproduce it now it is possible that it has to do within my installation, or to be precise within my upgraded version, of Ubuntu 22.04 with Wayland.

[Jeff Fortin Tam (kiddo)]

Bonjour Maxime,

I have encountered this issue with GNOME Shell 44 on Wayland on Fedora with Homebank 5.6.3 (GTK 3.24.37), and I believe I know what is the trigger for this. In my case, it is 100% related to the fact that I am running multiple monitors connected to my computer, and then Homebank's autocompletion popup will be misplaced *depending on which screen the window is on*.

If I put the transaction window onto monitor 1 (on the left), the autocompletion popup shows up in the correct place position underneath the form field. However, if I put the window on the right (monitor 2), the autocompletion pop-up is shifted to the right by 1790 pixels (at least that's what I measured in my screenshot) which means the autocompletion popup ends up off-screen entirely in most cases (unless the window is on the left side of the right screen), hence why other reporters thought the popup was missing / disappearing.

What does 1790 pixels represent? I'm not sure. My monitors are 1920px and 2560px wide respectively, so ~1790px does not match any of those two widths. Summing them up and dividing by two, (1920+2560)/2 = 2240, which is "somewhat" close but far from exactly representing the offset 🤷

In any case, here is a screenshot that shows you my total screens surface area (and thus their layout, including how it looks like in GNOME Control Center too), and how the autocompletion popup gets offset when the window is positioned on my primary monitor (monitor no.2, that is physically on the right of monitor no. 1).

Others here can confirm if they have similar monitors setups to mine or not. I hope this helps.

[Jeff Fortin Tam (kiddo)]

OK, I'm reasonably sure this is not actually a Homebank bug now, as I've encountered the bug with Evolution's mail composer as well.

Testing with the "gtk4-demo" app, and going to Entry -> Completion and running that demo, it seems to work fine no matter which screen the window is on. So it is a GTK3-specific issue that doesn't occur with GTK4 (and presumably won't be fixed in GTK3).

I did not find an existing bug report about it in GTK, but Matthias told me it's "a known issue with GTK3's Wayland implementation and it does not happen in GTK4".

So this bug will go away once Homebank is ported to GTK4. I did not find a ticket about this here, but I presume it's in the plans, implicitly...

[Maxime DOYEN (mdoyen)]

@kiddo:
Yes I do have plan for swith to GTK4 and opened #2030099 wish: migrate to GTK4

[hyperspeed1313 (hyperspeed1313)]

This only started happening to me today once I set up automatic payee rules. Before I had any automatic payee rules the autocomplete worked fine but now that I have rules, I don't get the autocomplete prompts on either Payee or Category.

[hyperspeed1313 (hyperspeed1313)]

I do get autocomplete prompts when setting up more automatic payee rules but not when editing transactions.

[hyperspeed1313 (hyperspeed1313)]

A bit more testing and I think I've isolated the cause (at least for my situation). Some of the payee rules I set up include an asterisk (*) in the payee name. By deleting all of those rules and keeping the rest I got autocomplete prompts back when editing transactions. Adding a single rule with an * broke autocomplete prompts again.

[hyperspeed1313 (hyperspeed1313)]

CORRECTION: my rules are all reading the Memo field, not the Payee field.

CLARIFICATION: I was not using * as a wildcard in my search terms - it actually appears in the memo field on transactions from some vendors (e.g. GOOGLE *YouTubePremium g.co/help GOOGLE *YouTubePremium g.co/help)

[hyperspeed1313 (hyperspeed1313)]

I'm now unable to reproduce the issue even with * in the search phrase for memo rules. I have no idea what changed.

[hyperspeed1313 (hyperspeed1313)]

I have a new update - the autocomplete works when any portion of the Edit Transaction window is on the primary monitor, including just the popup's drop-shadow. If the entire window is off the primary monitor, then autocomplete doesn't work.

[hyperspeed1313 (hyperspeed1313)]

Clarification: I run a 2-monitor setup with the primary monitor on the left and the other monitor to the right of it. The monitors are both of the same model and running at the same resolution & refresh rate.

If any portion of the Edit Transaction window is on the left-hand (primary) monitor, I get autocomplete popups. If the entire Edit Transaction window, including drop-shadow, is on the right (not primary) monitor, then no autocomplete prompt appears.

[Maxime DOYEN (mdoyen)]

as we discussed with Jeff Fortin Tam (kiddo) in
https://bugs.launchpad.net/homebank/+bug/2006456/comments/12
https://bugs.launchpad.net/homebank/+bug/2006456/comments/13

It seems this is pure GTK feature = nothing I can do
If you can reproduce this with gtk3-demo then please open a GTK bug.

[hyperspeed1313 (hyperspeed1313)]

Alas, the issue has been documented for a few years with multiple open merge requests but none of them have gotten merged. All we can do is make noise but it sounds like anything that's not GTK4 related won't be getting fixed.

https://gitlab.gnome.org/GNOME/gtk/-/issues/2794#note_1678177

[Maxime DOYEN (mdoyen)]

Waste of time to try convince GTK team to fix this in 3.x

They act a bit like despots by denigrating developers or users, anything that does not correspond to their vision or is NOT useful to Gnome ecosystem is doomed to a categorical refusal. GTK is it still a general UI toolkit or is it just a support of Gnome only ecosystem ? that is a question.

Meanwhile, about time and regression, it's completely understandable not to want to spend time on a stable and obsolete branch when the current version is free of the problem, I will do the same.

Anyway, beside this, we developpers have to move to GTK 4 and is not a piece of cake, as like in previous GTK 3 they have again broken/removed a lots of things, and this requires to rewrite/refactor/change large part of the code.

With their future plan with GTK 5, and path more oriented to move GTK to a gnome specific support toolkit I can also understand decision of other project to move to QT.

For now #2030099 wish: prepare and migrate to GTK4 is in progress

But when you compile even after preparation, you feel like been an ant at the foot of Everest...