https://bugs.documentfoundation.org/show_bug.cgi?id=160697

--- Comment #9 from [email protected] ---
(In reply to p.wibberley from comment #8)
> Doh(In reply to Michael Weghorn from comment #7)
> > (In reply to p.wibberley from comment #4)
> > > And it gets more confusing (at least, for me).  In Wayland, setting the
> > > QT_QPA_PLATFORM=xcb does make a difference.  If I run libreoffice --writer
> > > from a terminal window, the soffice.bin window opens and closes but only
> > > very briefly, and much quicker than before the QT_QPA_PLATFORM is set. 
> > > However, if I run Writer from the launcher menu, which (as I understand 
> > > it)
> > > has the %U parameter, the soffice.bin window persists for much longer, 
> > > much
> > > the same as before QT_QPA_PLATFORM is set. 
> > 
> > Do I understand correctly that even with QT_QPA_PLATFORM=xcb set, the
> > temporary window *does* still appear on Wayland (event if it's shorter)? If
> > so, this is a different issue than for the scenario I describe in comment 5.
> > Could you please double-check that "Help" -> "About LibreOffice" actually
> > has "VCL: kf5 (cairo+xcb)" in that case, and not "kf5 (cairo+wayland)"
> > (which should be shown when running on Wayland and not setting
> > QT_QPA_PLATFORM=xcb).
> > 
> > Does the "--nologo" argument to disable the splash screen make any
> > difference (i.e. starting as `libreoffice --nologo --writer`)?
> 
> Doh!  I copied the About Libreoffice information before I set
> QT_QPA_PLATFORM.  
> 
> 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.   
> 
> 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.  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"
> 
> 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.     
> 
> 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.   
> 
> Thanks and regards
> 
> P

Oh, and "--nologo" doesn't seem to make any difference.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to