Re: [dev] tabbed should not touch the child window until it has the _XEMBED_INFO property

2018-09-25 Thread Dimitrios Semitsoglou-Tsiapos
On 25/09/18 11:38, Quentin Rameau wrote:
> On Tue, 25 Sep 2018 11:21:27 +0200
> Dimitrios Semitsoglou-Tsiapos  wrote:
> 
>> Hello everyone,
> 
> Hello Dimitrios,
> 
>> I have been hunting a bug where zathura windows do not get rendered
>> inside tabbed. It seems that the issue boils down to both Gtk+ and tabbed.
> 
> And X11 embedding alltogether, I think.
> Let's hope you'll have more luck than I [3].
> 
>> To avoid repeating too much content here, you can see the list of bugs I
>> have opened so far linked here [1]. Most relevant to you should be
>> psychon's debugging work on the AwesomeWM bug [2], where he explains how
>> tabbed is involved in the issue.
>>
>> [1] https://gitlab.gnome.org/GNOME/gtk/issues/1358
>> [2] https://github.com/awesomeWM/awesome/issues/2385#issuecomment-420172264
> 
> But it looks the issue has been better localized, so maybe.
> Thanks!
> 
> [3] https://gitlab.gnome.org/GNOME/gtk/issues/757
> 

Hi Quentin,

Thanks a lot for taking a look. I had failed find this report earlier,
but I have just linked my issue to yours on their tracker. Let's see
what happens.

Cheers!



Re: [dev] tabbed should not touch the child window until it has the _XEMBED_INFO property

2018-09-25 Thread Quentin Rameau
On Tue, 25 Sep 2018 11:21:27 +0200
Dimitrios Semitsoglou-Tsiapos  wrote:

> Hello everyone,

Hello Dimitrios,

> I have been hunting a bug where zathura windows do not get rendered
> inside tabbed. It seems that the issue boils down to both Gtk+ and tabbed.

And X11 embedding alltogether, I think.
Let's hope you'll have more luck than I [3].

> To avoid repeating too much content here, you can see the list of bugs I
> have opened so far linked here [1]. Most relevant to you should be
> psychon's debugging work on the AwesomeWM bug [2], where he explains how
> tabbed is involved in the issue.
> 
> [1] https://gitlab.gnome.org/GNOME/gtk/issues/1358
> [2] https://github.com/awesomeWM/awesome/issues/2385#issuecomment-420172264

But it looks the issue has been better localized, so maybe.
Thanks!

[3] https://gitlab.gnome.org/GNOME/gtk/issues/757