https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Alain Baste changed:
What|Removed |Added
CC||alain.ba...@gmail.com
--- Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #71 from Raju ---
Comment on attachment 197115
--> https://bugs.documentfoundation.org/attachment.cgi?id=197115
Image of said issue on a multi-monitor setup
The image is one of the screen on one of the 2 external monitors t
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #70 from Raju ---
Created attachment 197115
--> https://bugs.documentfoundation.org/attachment.cgi?id=197115&action=edit
Image of said issue on a multi-monitor setup
This is a screenshot of Libre Office when it's redrawn af
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #69 from Kira Backes ---
I can confirm what Peter wrote: I have one display (4k) at 150%, and one
display (2560x1440) at 100%. When I open LibreOffice the toolbars are MUCH too
small, unusable on the 4k display. It doesn’t mat
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Michael Weghorn changed:
What|Removed |Added
Blocks||145734
Referenced Bugs:
http
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #68 from Peter Levart ---
A can confirm the findings of Tim Hamilton in comment 26:
https://bugs.documentfoundation.org/show_bug.cgi?id=141578#c26
If neither of the scaling factors of different (both in my case) monitors is
1
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #67 from Luiz Angelo Daros de Luca ---
I still get the same issue
Version: 24.8.0.3 (X86_64) / LibreOffice Community
Build ID: 480(Build:3)
CPU threads: 20; OS: Linux 6.10; UI render: default; VCL: kf6 (cairo+wayland)
Locale:
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #66 from
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #65 from Stéphane Guillou (stragu)
---
Two videos showing behaviour with kf6, from duplicate bug 161852:
- attachment 195061
- attachment 195062
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Stéphane Guillou (stragu) changed:
What|Removed |Added
CC||mokaz...@disroot.org
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Buovjaga changed:
What|Removed |Added
CC||pavel.uru...@gmail.com
--- Comment #6
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #62 from Stéphane Guillou (stragu)
---
*** Bug 161257 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #61 from Michael Weghorn ---
(In reply to typingcat from comment #58)
> In my case, I have two monitors: 1080p (secondary) and 4K (main), and LO
> looks normal on the 1080p, and looks tiny on the 4K. So, "moving the window
> t
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #60 from htspa...@gmail.com ---
(In reply to htspamky from comment #59)
Hello! (Sorry for double comment, using Bugzilla for the first time :) )
I have found an interesting case regarding this issue depending on when
external
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #59 from htspa...@gmail.com ---
Created attachment 193920
--> https://bugs.documentfoundation.org/attachment.cgi?id=193920&action=edit
Scale depending on when the monitor is plugged in (recording)
Version: 24.2.2.2 (X86_64)
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #58 from typing...@gmail.com ---
(In reply to Michael Weghorn from comment #45)
> * The LO window is displayed properly on one of the screens at least, so
> moving the window to that screen should be a functioning workaround.
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #57 from lrdarkne...@yahoo.de ---
Thanks @Martin for you hint.
The combination
> WAYLAND_DISPLAY= SAL_USE_VCLPLUGIN=kf5 /usr/bin/libreoffice
also shows good results on my end.
Even tho I would prefer a native Wayland window
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Stéphane Guillou (stragu) changed:
What|Removed |Added
See Also|https://bugs.documentfounda |https://bugs.document
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #56 from Michael Weghorn ---
(In reply to typingcat from comment #55)
> Came here to report a similar issue. I am using 2 monitors with different
> DPI/scalings (100% and 150%) and Arch Linux. There was no scaling issue
> unde
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #55 from typing...@gmail.com ---
Came here to report a similar issue. I am using 2 monitors with different
DPI/scalings (100% and 150%) and Arch Linux. There was no scaling issue under
Wayland Gnome fractional scaling. Now that
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #54 from Michael Weghorn ---
(In reply to Ferdinand Bachmann from comment #53)
> I'm having a possibly related issue (reported as
> https://bugs.documentfoundation.org/show_bug.cgi?id=160268 here), which
> happens on single mo
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #53 from Ferdinand Bachmann ---
I'm having a possibly related issue (reported as
https://bugs.documentfoundation.org/show_bug.cgi?id=160268 here), which happens
on single monitor setups with fractional scaling, but only with t
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #52 from Martin ---
Still present in LO 24.2.1.2 running on Plasma 5.27.8.
After trying all the different combinations of WAYLAND_DISPLAY and
SAL_USE_VCLPLUGIN, the one that works the best for me is (uses XWayland):
WAYLAND_
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Stéphane Guillou (stragu) changed:
What|Removed |Added
CC||stephane.guillou@libr
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Stéphane Guillou (stragu) changed:
What|Removed |Added
See Also||https://bugs.document
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Michael Weghorn changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #50 from Michael Weghorn ---
(In reply to Michael Weghorn from comment #48)
> > 5. I may be wrong, but I am getting the impression that either: the issue is
> > not easily fixable (...)
>
> From how I understand it (reading J
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #49 from Michael Weghorn ---
(In reply to aldo-pub...@laposte.net from comment #47)
> SAL_USE_VCLPLUGIN=gtk3 is not even an option in my case, since global menu
> won't work...
> I do not know if it is due to another bug in li
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #48 from Michael Weghorn ---
(In reply to Callegar from comment #46)
> All your points are indeed valid. As a matter of fact, I used a conditional
> precisely because cons might outweight pros, but I thing that an evaluation
>
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #47 from aldo-pub...@laposte.net ---
SAL_USE_VCLPLUGIN=gtk3 is not even an option in my case, since global menu
won't work...
I do not know if it is due to another bug in libreoffice, but the result is
here: none of the availa
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #46 from Callegar ---
All your points are indeed valid. As a matter of fact, I used a conditional
precisely because cons might outweight pros, but I thing that an evaluation
thereof can be useful.
- On one hand:
for anyone e
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #45 from Michael Weghorn ---
(In reply to Callegar from comment #44)
> Might be a good idea to default to gtk3 even on KDE, at least temporarily.
My personal take is that the issue discussed here should not be reason enough
f
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #44 from Callegar ---
Might be a good idea to default to gtk3 even on KDE, at least temporarily.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #43 from pieter kristensen ---
I installed LO 24.02, downloaded from the site of the Document Foundation, as
second version on my Neon Unstable computer.
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #42 from jonathan.nach...@mail.de ---
Update: using QT_QPA_PLATFORM=xcb makes it work for me, but is of course still
a nasty hack which can not be expected by a regular end-user.
--
You are receiving this mail because:
You ar
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #41 from jonathan.nach...@mail.de ---
Can confirm.
My situation:
- KDE Plasma, Wayland, LO 7.5
- build-in 4K monitor, set to 200% scaling
- external FullHD monitor, set to 100% scaling
Dragging a LO app to built-in monitor:
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #40 from Michael Weghorn ---
(In reply to Callegar from comment #38)
> Here it seems to help, possibly because the compositor is set to make
> XWayland applications deal with the scaling themselves. Similarly it helps
> to use
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #39 from Callegar ---
While it is easy to work around this issue when invoking LibO from the shell or
a desktop icon (it is enough to have a "regular" launcher and one forcing
either the GTK3 VCL or the xcb mode), the thing be
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #38 from Callegar ---
> Sure, forcing to run on XWayland via this env var or QT_QPA_PLATFORM=xcb is a
> valid workaround for Wayland-specific problems. But does this actually help
> with the problem described here?
Here it
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #37 from Michael Weghorn ---
(In reply to Callegar from comment #36)
> Given that LibO + kf5 has also other issues with Wayland (e.g. wrong
> cursors, bug 141828), as a quick hack for those affected, consider
> temporarily ali
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #36 from Callegar ---
Given that LibO + kf5 has also other issues with Wayland (e.g. wrong cursors,
bug 141828), as a quick hack for those affected, consider temporarily aliasing
libreoffice to `WAYLAND_DISPLAY= libreoffice` s
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #35 from Michael Weghorn ---
(In reply to Luca Carlon from comment #33)
> I uploaded a patch for Qt6/Wayland:
> https://gerrit.libreoffice.org/c/core/+/157683. It is far from perfect, but
> it seems to be an improvement for me
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #34 from Michael Weghorn ---
Created attachment 190104
--> https://bugs.documentfoundation.org/attachment.cgi?id=190104&action=edit
Screenshot with https://gerrit.libreoffice.org/c/core/+/157683 v4 in place
--
You are rece
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #33 from Luca Carlon ---
I uploaded a patch for Qt6/Wayland:
https://gerrit.libreoffice.org/c/core/+/157683. It is far from perfect, but it
seems to be an improvement for me. Someone who can test it?
--
You are receiving thi
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Stéphane Guillou (stragu) changed:
What|Removed |Added
Blocks||104160
Referenced B
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Stéphane Guillou (stragu) changed:
What|Removed |Added
CC||i...@sfbtech.nl
---
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Stéphane Guillou (stragu) changed:
What|Removed |Added
CC||dinumar...@gmail.com
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #30 from Callegar ---
Unfortunately it may not be possible to use the GTK4 vcl as a workaround,
because of bug 157452.
As a workaround for this issue, you can try using libreoffice with X11 as
WAYLAND_DISPLAY= libreoffice
b
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #29 from Callegar ---
(In reply to Gergely HORVÁTH from comment #27)
> Interesting, that is quite the opposite of what I experience. In my use case
> (3k monitor notebook screen, FHD external monitor), the external screen is
>
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #28 from Tim ---
When connected, I have my external monitor set to primary.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #27 from Gergely HORVÁTH ---
Interesting, that is quite the opposite of what I experience. In my use case
(3k monitor notebook screen, FHD external monitor), the external screen is the
primary screen. Maybe the problem arises
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #26 from Tim ---
> Is the issue related to fractional scaling only? I.e. does integer scaling
> (i.e. 200%) work correctly?
My use case is reasonably typical. An inbuilt laptop screen running at
1920x1080 and an external mon
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #25 from Gergely HORVÁTH ---
I agree, that the problem is the different scaling factor. I also checked it
with 200% on 3k screen and 100% on FHD screen and the problem persists.
--
You are receiving this mail because:
You ar
https://bugs.documentfoundation.org/show_bug.cgi?id=141578
Michael Weghorn changed:
What|Removed |Added
Summary|Libreoffice unusable with |Libreoffice unusable with
54 matches
Mail list logo
