https://bugs.documentfoundation.org/show_bug.cgi?id=160697
--- Comment #12 from p.wibber...@btinternet.com --- (In reply to Michael Weghorn from comment #11) > (In reply to p.wibberley from comment #8) > > Also, I've clearly been confused by the scope of environment variables here, > > as > > > > (a) I can set QT_QPA_PLATFORM in one terminal window and start Writer from > > there, and I get the extremely brief soffice.bin window - so it's not my > > computer! - but > > > > (b) if I open a second terminal then QT_QPA_PLATFORM isn't set and I get a > > slow soffice.bin window. > > Yes, an `export QT_QPA_PLATFORM=xcb` only applies for the current terminal, > i.e. processes started from there. > > > Moreover, About Libreoffice shows "VCL:kf5(cairo+xcb)" with QT_QPA_PLATFORM > > set but "VCL:kf5(cairo+wayland)" without. I think this is what you suggest > > I should see. > > Yes. > > > I also see that the terminal window without QT_QPA_PLATFORM > > gives error messages, > > > > "qt.qpa.wayland: Wayland does not support QWindow::requestActivate()" > > "This plugin supports grabbing the mouse only for popup windows" > > This warning is expected and unrelated. > > > So, presumably, when I'm starting Writer from the launcher menu, it's simply > > not seeing QT_QPA_PLATFORM that I set in the first terminal window. > > Yes, exactly. > > > Another observation is that if I open Writer from the first terminal window, > > and *leave it open* while I start Writer from the second terminal window, > > then the second instance of Writer behaves as if QT_QPA_PLATFORM *is* set, > > even though running env in the second terminal window shows that it isn't. > > May be we should expect that, but I thought it worth noting. > > Yes, that's expected. LibreOffice doesn't start a new process/"session", but > reuses the existing one if it's already running. > > (In reply to p.wibberley from comment #9) > > Oh, and "--nologo" doesn't seem to make any difference. > > Thanks. > > So to summarize: There's an "soffice.bin" window showing up temporarily when > starting Writer, that then disappears and the actual Writer window shows up. > This happens when either running LO as a native Wayland application > (starting LO without QT_QPA_PLATFORM=xcb set) and when run with Qt's xcb > platform, i.e. on XWayland (starting LO with QT_QPA_PLATFORM=xcb set). > For the Wayland case, that "soffice.bin" window is shown much shorter than > for the xcb case, but it's still shown. > > Is that correct? > > Could you please try whether you see the same when you start LO with > environment variable SAL_USE_VCLPLUGIN=gtk3 to force the use of the > so-called gtk3 VCL plugin? (Please double-check that "Help" -> "About > LibreOffice" shows "VCL: gtk3" then.) Hi Michael, Your summary is correct. Yes, a "soffice.bin" opens and disappears, to be replaced by the Writer window. This happens with X11 and Wayland, with or without QT_QPA_PLATFORM=xcb. And, yes, for Wayland, the soffice.bin windows is visible for a much shorter time when QT_QPA_PLATFORM=xcb (as I think is also the case with X11 - I can recheck that later this afternoon). I've tried SAL_USE_VCLPLUGIN=gtk3. I still get an initial window, but it is now labelled "Libreoffice 24.2", and is visible for about the same duration as with QT_QPA_PLATFORM=xcb. And I can confirm that do get "VCL: gtk3". I should say, where the window is visible only very briefly, I can't be sure whether the Writer window is a separate window that replaces the first window, or whether the title bar of the first window is simply re-labelled. In contrast, with Wayland and no environment variables set, it's definitely the case that the first window closes, to be replaced by the second. Regards P -- You are receiving this mail because: You are the assignee for the bug.
