Bug 164380 - Move slides in preview pane by drag-and-drop not possible in qt6-based vcl on Wayland
Summary: Move slides in preview pane by drag-and-drop not possible in qt6-based vcl on...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
24.8.4.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 164534 (view as bug list)
Depends on:
Blocks: Wayland Qt6
  Show dependency treegraph
 
Reported: 2024-12-19 13:09 UTC by robby.engelmann
Modified: 2025-01-09 12:31 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description robby.engelmann 2024-12-19 13:09:18 UTC
Exactly as stated in the summary.

Moving slides when using the gtk3 VCL works as expected.


Version: 24.8.3.2 (X86_64) / LibreOffice Community
Build ID: 480(Build:2)
CPU threads: 20; OS: Linux 6.11; UI render: default; VCL: qt6 (gtk3)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Buovjaga 2024-12-19 13:45:19 UTC
Yeah, kf5 seems fine and thus we can't bibisect this as the repositories have not been built with kf6/qt6. Could be an implementation error.
Comment 2 Michael Weghorn 2024-12-19 19:26:43 UTC
Works for me with QT_QPA_PLATFORM=xcb, i.e. on X11/XWayland  (even though the drag cursor shows a "stop" sign), but not on native Wayland.

Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 36276f606cd99561dd8449f41ba846866e75affa
CPU threads: 32; OS: Linux 6.11; UI render: default; VCL: qt6 (cairo+xcb)
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 36276f606cd99561dd8449f41ba846866e75affa
CPU threads: 32; OS: Linux 6.11; UI render: default; VCL: qt6 (cairo+wayland)
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded
Comment 3 Michael Weghorn 2025-01-09 12:31:45 UTC
*** Bug 164534 has been marked as a duplicate of this bug. ***