Hi Aleix, zero in xdg_toplevel.set_*_size just means the client doesn't care about the size
>From xdg-shell.xml: > If never set, or a value of zero in the request, means that the > client has no expected minimum size in the given dimension. > As a result, a client wishing to reset the minimum size > to an unspecified state can use zero for width and height in the request. Can you paste the full logs? The ones you pasted just include the point where the client starts destroying surfaces... At least we know that the client does destroy it's own surfaces, but we still need to understand why, or in reaction to what. Also, it could be worth trying if https://codereview.qt-project.org/c/qt/qtwayland/+/263974 fixes the issue. That bug has been the cause of windows closing in other issues. It seems that there are some special kde extensions (org_kde_kde_plasma_window) involved here... If it happens with vanilla Qt as well, that would make it much easier (for me at least) to debug. Br, Johan Helsing ________________________________ From: Aleix Pol <aleix...@kde.org> Sent: Tuesday, June 11, 2019 12:54:06 PM To: Johan Helsing Cc: plasma-devel@kde.org; kwin Subject: Re: Plasma dialogs (and others?) disappearing on wayland + Qt 5.13 I forgot to CC you: https://mail.kde.org/pipermail/plasma-devel/2019-June/098775.html This doesn't look very well: [1743961,992] -> xdg_toplevel@28.set_min_size(0, 0) [1743962,023] -> xdg_toplevel@28.set_max_size(0, 0) Aleix On Tue, Jun 11, 2019 at 9:29 AM Johan Helsing <johan.hels...@qt.io> wrote: > > Hi Aleix, > > I would try reproducing it with one of the Qt examples, try the ones in > qtbase/examples/widgets for instance. > > Otherwise, WAYLAND_DEBUG logs might have some clues as to what's happening. > > Br, > > Johan Helsing > > ________________________________ > From: Aleix Pol <aleix...@kde.org> > Sent: Monday, June 10, 2019 7:58:23 PM > To: plasma-devel@kde.org; kwin > Cc: Johan Helsing > Subject: Plasma dialogs (and others?) disappearing on wayland + Qt 5.13 > > Hey, > Since I switched to a Qt 5.13 build, I'm seeing that some dialogs > eventually stop showing up. > > It happens randomly and I'm not even sure that it's Qt's fault > anymore, but I wouldn't discard it either. Initially I thought it > would be [1] but it got fixed and I still get it. > > An easy way to trigger the problem is by using krunner. Just open it, > type something until you get some results, press Escape. Sometimes it > needs doing a couple of times. > > With yakuake it can be done as well by pressing its key combination a > couple of times not even that quickly. > > Any ideas what this could be? > Aleix > > [1] https://bugreports.qt.io/browse/QTBUG-76124
