FS#76833 - [meld] 3.22.0-1 cannot be resized when called via X11 forwarding

Attached to Project: Arch Linux
Opened by Klaus (klaeuser) - Thursday, 15 December 2022, 10:41 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 17 January 2023, 20:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
when calling meld via X the window opens in the lower right corner and cannot be moved or resized.
If there is already a window in the lower right corner of the screen, the meld window is placed to the left of it. Strangely, all other functions work. For example, the menu can be called using the mouse and closing the window using (x) also works - only the size and position of the window can neither be changed with the mouse, nor with the keyboard.


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Toolybird (Toolybird)
Tuesday, 17 January 2023, 20:59 GMT
Reason for closing:  None
Additional comments about closing:  It's uncertain but an upstream issue seems likely. Please request task re-open if an Arch packaging bug is identified.
Comment by Toolybird (Toolybird) - Friday, 16 December 2022, 01:31 GMT
When you say "via X" do you mean it was launched by the menu entry in your desktop environment? I can't repro what you're seeing. It sounds like an issue with your window manager. What Desktop/WM environment are you running?
Comment by Klaus (klaeuser) - Friday, 16 December 2022, 06:27 GMT
Oh ... excuse me, I really should explain that better!

What I Do is:

from my Desktop (Manjaro-Linux) I open a ssh session (with X-forwarding) to the Arch Linux machine. There I call meld from the command line (after setting the DISPLAY variable and configuring that xauth stuff).

This works very well for machines running other Linux distributions (e.g. Debian, PiOS) and it used to work with Arch Linux as well. Therefore I don't think it is a problem with the window manager (I use LDM). Unfortunately I cannot say, when (at which version of meld) the problem started ...
I tried to diagnose this a bit ... e.g. with strace, but I cannot see, what the problem is. The strange thing is, that only the (mouse) events for resizing and moving the window don't seem to get through, while all other events work.
Comment by Klaus (klaeuser) - Friday, 16 December 2022, 08:17 GMT
just double-checked this, just to see if it was a general problem with X windows over ssh.
When e.g running xclock that way, every thing works well.
Obviously we see a problem of meld itself here, or a problem of the underlying graphic library/framework (Qt or whatever).

It is noticeable that the two windows of xclock and meld have quite different designs.
... and if I run meld (via ssh/X forwarding) on a Debian system, the design of that window looks like the design of the xclock window on the Arch Linux machine.
This could explain, why meld works on Debian but has some issues on Arch Linux?
Comment by Klaus (klaeuser) - Friday, 16 December 2022, 08:21 GMT
.
   meld_window_arch_linux.png (21.2 KiB)
   meld_window_debian.png (28.6 KiB)
   xclock_window_arch_linux.png (4.5 KiB)
Comment by Toolybird (Toolybird) - Friday, 16 December 2022, 22:31 GMT
Ok, X11 forwarding. meld is a gtk3 application. Instead of xclock, please try another gtk3 app. I still can't repro when X11 forwarding from a VM to my main desktop (but it's running i3). BTW, what is LDM?
Comment by Klaus (klaeuser) - Saturday, 17 December 2022, 06:56 GMT
Hmmm ... do you have any idea which other applications use gtk3?

LDM (also often called LightDM) is the display manager that came with LXDE

Comment by Toolybird (Toolybird) - Sunday, 18 December 2022, 01:56 GMT
Um, I asked what DE/WM you were running and you responded with LDM. LightDM is a "Display Manager" [1] and essentially nothing to do with the problem at hand. If you're running LXDE then your Window Manager is likely to be openbox which is part of the "lxde" installation group. Please confirm what Window Manager you are running.

> do you have any idea which other applications use gtk3?

Really? This is assumed basic knowledge for a bug reporter. Please look here [2] and see the "Required By" section. Try something simple like "geany".

Anyway, it's becoming clear this is actually a support request, and the bug tracker is not for support. You're best advised to use the proper support channels (forum/IRC/etc) to seek helping debugging the problem and trying to identify if there is an Arch packaging issue.

[1] https://wiki.archlinux.org/title/Display_manager
[2] https://archlinux.org/packages/extra/x86_64/gtk3/
Comment by Klaus (klaeuser) - Sunday, 18 December 2022, 08:27 GMT
Excuse me for using the wrong channel!
I was not aware there are different ones ...

Yes openbox is the window manager.

Again ... excuse me for mixing up DM and WM, I'm no specialist for graphical stuff and from the guidelines of bug tracking I could not recognize, this was required.

But I'm not sure, if openbox is the cause for the problem.
Just did another test with a VM running another Desktop (LXQt). This desktop uses openbox too, but there meld works as expected - even via ssh/X forwarding.

Furthermore I tried geany - but this also works as expected.
This could mean the problem is related to other stuff.

Anyway - I'll try to find support at other places.
Thank you for your suggestions!

Loading...