retitle 977977 libreoffice: a large part of the window might appear off-screen if resultion/monitor config changes
Hi, Am 23.12.20 um 20:34 schrieb Vincent Lefevre: > On 2020-12-23 19:53:09 +0100, Rene Engelhard wrote: >> Am 23.12.20 um 18:59 schrieb Vincent Lefevre: >>> A large part of the window appears off-screen, including the menu >>> and window controls. Basically, the only thing I can do is to type >>> Ctrl-Q to quit Libreoffice! >> And why is that? Obviously works on one-monitor setups. > My machine is a laptop, sometimes with only its screen, sometimes > with 2 external 4K monitors, depending on where I am. Aha. I have none of these. (Besides that my laptop has a sane graphics card.) >> And given you apparently use the nvidia driver (see below).... No way to >> reproduce this here. > The nouveau driver is unusable with an external monitor (even when > used in mirror mode). The nvidia driver is the only solution with > such a configuration. In Germany we have an idiom amongst IT people: "Augen auf beim Hardwarekauf" (which roughly translates to "open your eyes when buying hardware"). You got into this situation yourself. > I did not set anything special. I rarely use LibreOffice (only when I > need to). And I don't think I have ever changed anything explicitly in > the preferences. In short, I let LibreOffice handle the config on its > own. OK, but I believe it saves it's dimensions when closed, I at laest get this when williy-nilly dragging the window. It probably also saves the location.. This would explain your problem. I don't think there is a senseful way to fix this though. Always start maximized (and automatically on the current monitor/display)? Probably not. In any case, this is something for upstream - not Debian to change. And for that there's reportbug mentioning that upstream bugs should go upstream. > That's the default for unstable, except that I added experimental. No, it's not. Adding stable and testing is not. (unstable-debug is understandable, but also not default.) > Currently everything has been installed > from unstable Sure. > (or testing or stable, when this was the latest package > version). But there's no need for stable or testing here. >>> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, >>> TAINT_UNSIGNED_MODULE >> Try with a sane system? > AFAIK, that's just due to the nvidia driver, for the reason explained > above. Which proves my point. (I do not care about nvidia.) Regards, Rene
