When launching Writer in KDE Neon 6.0, a window opens momentarily which is blank apart from "soffice.bin" in the title bar. It is replaced a moment later by another window with a new Writer document. None of the other LibreOffice applications seem to do this, but if I open any application and select File->New->Text Document then the same thing happens. This doesn't impair functionality but it just looks a bit odd. Thanks and regards
I don't notice that but maybe it's just happening too fast. Is this on X11 or Wayland? If it's on Wayland: Does this also happen when you start LibreOffice with environment variable QT_QPA_PLATFORM=xcb set to force LibreOffice to use Qt's xcb/X11 integration instead? Can you please copy the version info from "Help" -> "About LibreOffice" here? If it's Wayland-only, this may be due to the hide/show cycle introduced in order to be able to use app-specific window icons, see commit commit cea0371ac77145ad1f3db7e558c279aeed6f4d00 Author: Michael Weghorn Date: Mon Feb 12 14:09:45 2024 +0100 tdf#125934 qt: Support module-specific window icons on Wayland I've mentioned that problem in [1] earlier: > It obviously has the side-effect that the window disappears for a short amount of time and it still feels a bit like a workaround to me. The way forward for a proper solution would IMHO require new API in Qt as mentioned in that Qt issue. [1] https://bugreports.qt.io/browse/QTBUG-77182?focusedId=774291&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-774291
Hi Michael, Thank you for your comment. I hope when you say it's happening too fast for you, you're not being rude about my computer! The version information from 'Help'->'About Libreoffice' is Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 4:24.2.2~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded The issue seems to arise with both Wayland and X11. I tried setting the environment variable - env | grep QT QT_ACCESSIBILITY=1 QT_EXCLUDE_GENERIC_BEARER=1 QT_QPA_PLATFORM=xcb QT_WAYLAND_RECONNECT=1 QT_AUTO_SCREEN_SCALE_FACTOR=0 - but it doesn't seem to make any difference, and I still briefly get the blank "soffice.bin" window. As I say, the issue is, of itself, utterly trivial, and I only mentioned it in case it is indicative of something more important being not quite right. Let me know if there's additional information I can provide. Thanks and regards
(In reply to p.wibberley from comment #2) > Hi Michael, > > Thank you for your comment. I hope when you say it's happening too fast for > you, you're not being rude about my computer! > > The version information from 'Help'->'About Libreoffice' is > > Version: 24.2.2.2 (X86_64) / LibreOffice Community > Build ID: 420(Build:2) > CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) > Locale: en-GB (en_GB.UTF-8); UI: en-GB > Ubuntu package version: 4:24.2.2~rc2-0ubuntu0.22.04.1~lo1 > Calc: threaded > > The issue seems to arise with both Wayland and X11. I tried setting the > environment variable - > > env | grep QT > QT_ACCESSIBILITY=1 > QT_EXCLUDE_GENERIC_BEARER=1 > QT_QPA_PLATFORM=xcb > QT_WAYLAND_RECONNECT=1 > QT_AUTO_SCREEN_SCALE_FACTOR=0 > > - but it doesn't seem to make any difference, and I still briefly get the > blank "soffice.bin" window. > > As I say, the issue is, of itself, utterly trivial, and I only mentioned it > in case it is indicative of something more important being not quite right. > Let me know if there's additional information I can provide. > > Thanks and regards Sorry, checked again and it DOES NOT happen with X11. (Not sure what I did wrong the first time.)
(In reply to p.wibberley from comment #3) > (In reply to p.wibberley from comment #2) > > Hi Michael, > > > > Thank you for your comment. I hope when you say it's happening too fast for > > you, you're not being rude about my computer! > > > > The version information from 'Help'->'About Libreoffice' is > > > > Version: 24.2.2.2 (X86_64) / LibreOffice Community > > Build ID: 420(Build:2) > > CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) > > Locale: en-GB (en_GB.UTF-8); UI: en-GB > > Ubuntu package version: 4:24.2.2~rc2-0ubuntu0.22.04.1~lo1 > > Calc: threaded > > > > The issue seems to arise with both Wayland and X11. I tried setting the > > environment variable - > > > > env | grep QT > > QT_ACCESSIBILITY=1 > > QT_EXCLUDE_GENERIC_BEARER=1 > > QT_QPA_PLATFORM=xcb > > QT_WAYLAND_RECONNECT=1 > > QT_AUTO_SCREEN_SCALE_FACTOR=0 > > > > - but it doesn't seem to make any difference, and I still briefly get the > > blank "soffice.bin" window. > > > > As I say, the issue is, of itself, utterly trivial, and I only mentioned it > > in case it is indicative of something more important being not quite right. > > Let me know if there's additional information I can provide. > > > > Thanks and regards > > Sorry, checked again and it DOES NOT happen with X11. (Not sure what I did > wrong the first time.) 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. I'm fairly certain that with Calc the soffice.bin window doesn't appear at all, not even for a fleeting moment.
Thanks for the additional information. (In reply to p.wibberley from comment #2) > I hope when you say it's happening too fast for > you, you're not being rude about my computer! Sorry, no offense at all intended. This might also just be myself being too slow to see the temporary window,... What I can reproduce is: * start LO start center * start a new Writer doc from there -> the start center window disappears, and shortly after that, a Writer window shows up With QT_QPA_PLATFORM=xcb, the existing window smoothly turns into the Writer window. Since the issue you're experiencing is also Wayland-only, let's assume it's the same root cause. [If you want, you can double-check this by trying an older LibreOffice version (e.g. 7.6, or 24.2.1): These don't contain the commit mentioned in comment 1 yet, so shouldn't show that behavior if it's actually the same root cause. (But then, the Writer icon isn't used for the Window icon, which I'd personally consider worse then an initial annoyance on startup.)] Setting to NEW for now. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0d82ddb39e0cdbfde428eb4da7268cac4176f1bd CPU threads: 32; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded
(In reply to Michael Weghorn from comment #5) > Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community > Build ID: 0d82ddb39e0cdbfde428eb4da7268cac4176f1bd > CPU threads: 32; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+xcb) > Locale: en-GB (en_GB.UTF-8); UI: en-US > Calc: threaded For clarification: The above (xcb) case is the good one (i.e. the one without the hide/show); the one that has the hide/show in between is with the wayland Qt QPA plugin: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0d82ddb39e0cdbfde428eb4da7268cac4176f1bd CPU threads: 32; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded
(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(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
(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.
[Automated Action] NeedInfo-To-Unconfirmed
(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.)
(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
Created attachment 193980 [details] Screencast with gtk3 VCL plugin (without and with --nologo)
(In reply to p.wibberley from comment #12) > 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". Is this also the case when starting with the "--nologo" argument mentioned earlier? I do see a temporary "LibreOffice" Window when starting without the "--nologo" argument. But I don't see that window when starting with "--nologo", which disables the splash screen. If you look at that screencast: Do you see any other difference in behavior between your system and mine? And is the issue you describe visible in a screencast? (If so, attaching one here could help in understanding what's going on.) > 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. Is that also with SAL_USE_VCLPLUGIN=gtk3 (and verifying that this is actually used in "Help" -> "About LibreOffice") or only with kf5 (in which case this could then be the aspect I mentioned in comment 1)?
Hi Michael, Sorry for the delay in replying. With SAL_USE_VCLPLUGIN=gtk3, I get a very brief window with "Libreoffice 24.2" in the title bar, replaced by "Untitled 1 - Libreoffice Writer", with the Version Information, Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 4:24.2.3~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded I think it's the same window that gets relabelled when the document is opened, rather than without SAL_USE_VCLPLUGIN=gtk3 when I definitely see a second window opening over the first (which then disappears) with the Version Information Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 4:24.2.3~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded Does that answer your question, or have I missed the point?
(In reply to p.wibberley from comment #15) > Does that answer your question, or have I missed the point? Thanks for testing and reporting back here. Could you please check whether starting from command line with the "--nologo" argument makes a difference and whether the behavior shown in screenshot attachment 193980 [details] is the same as what you're seeing or whether we're talking about 2 different things?
Created attachment 194119 [details] Screencast showing superfluous soffice.bin window. This is without SAL_USE_VCLPLUGIN=gtk3.
(In reply to p.wibberley from comment #17) > Created attachment 194119 [details] > Screencast showing superfluous soffice.bin window. > > This is without SAL_USE_VCLPLUGIN=gtk3. Thanks! This is indeed different from what I can see, but looks like it might be due to what I've mentioned in comment 1. Can you please check one more thing? Do you still see that window if you start LO with SAL_USE_VCLPLUGIN=gen ? (Please double-check that "Help" -> "About LibreOffice" shows "VCL: x11" then.)
(In reply to Michael Weghorn from comment #19) > (In reply to p.wibberley from comment #17) > > Created attachment 194119 [details] > > Screencast showing superfluous soffice.bin window. > > > > This is without SAL_USE_VCLPLUGIN=gtk3. > > Thanks! This is indeed different from what I can see, but looks like it > might be due to what I've mentioned in comment 1. > > Can you please check one more thing? Do you still see that window if you > start LO with SAL_USE_VCLPLUGIN=gen ? > > (Please double-check that "Help" -> "About LibreOffice" shows "VCL: x11" > then.) Screencast attached for SAL_USE_VCLPLUGIN=gen. Oddly, the SAL_USE_VCLPLUGIN=gen seems to affect the screen recording, so you don't see that there's no obvious sign of the initial window (regardless of whether or not we have the logo splash, using the --nologo switch). As you should be able to see in the screencast, with SAL_USE_VCLPLUGIN=gen, the Version Information is Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: x11 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 4:24.2.3~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded P
(In reply to p.wibberley from comment #20) > Screencast attached for SAL_USE_VCLPLUGIN=gen. Oddly, the > SAL_USE_VCLPLUGIN=gen seems to affect the screen recording, so you don't > see that there's no obvious sign of the initial window (regardless of > whether or not we have the logo splash, using the --nologo switch). > > As you should be able to see in the screencast, with SAL_USE_VCLPLUGIN=gen, > the Version Information is Thanks. There seems to be no actual screencast attached with this comment, but from reading, gen doesn't show the extra window, which supports the idea that comment 1 describes the root cause (window hide/show due to QTBUG-77182) for qt6/kf6 on Wayland. Setting to NEW again. Let's use this ticket to keep track of that aspect. (If there's anything else after that has been addressed, that can still be tracked in a separate bug report.)
Created attachment 194170 [details] Screencast showing Writer with SAL_USE_VCLPLUGIN=gen Doh! Yes, you are correct, in that the blank window doesn't appear. Interestingly, this isn't really visible from the screencast (now attached, hopefully). As you can see the recording shows the screen as being distorted while Writer is starting up. I did NOT see this distortion for real, and it is purely an artifact of the recording. Is this a separate issue? It appears also that the dark theme isn't used with SAL_USE_VCLPLUGIN=gen. I'm guessing you would expect that.
(In reply to p.wibberley from comment #22) > Yes, you are correct, in that the blank window doesn't appear. > Interestingly, this isn't really visible from the screencast (now attached, > hopefully). Thanks, yes, the attachment is indeed there now. > As you can see the recording shows the screen as being > distorted while Writer is starting up. I did NOT see this distortion for > real, and it is purely an artifact of the recording. Is this a separate > issue? If this is isn't seen when actually using LO, but only in the recording, I'd just ignore it for now. > It appears also that the dark theme isn't used with SAL_USE_VCLPLUGIN=gen. > I'm guessing you would expect that. Yes, that's expected. The "gen" VCL plugin is a very basic one that's mainly useful for testing, not really meant to be used for daily work.