https://bugs.kde.org/show_bug.cgi?id=502695
Vlad Zahorodnii <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|REPORTED |RESOLVED --- Comment #11 from Vlad Zahorodnii <[email protected]> --- (In reply to unhappy-ending from comment #10) > Hello, is there any news on this? It's still an issue and I have a display I > would like to scale at less than 100%. Because of this behavior, I can't. I looked at the events that kwin sends [4255966.088] xdg_toplevel#64.configure(1440, 2560, array[8]) [4255966.138] xdg_surface#63.configure(9422) [4255966.189] -> xdg_toplevel#64.set_min_size(500, 87) [4255966.192] -> xdg_toplevel#64.set_max_size(0, 0) [4255967.166] -> xdg_toplevel#64.set_min_size(500, 87) [4255967.178] -> xdg_toplevel#64.set_max_size(0, 0) [4255967.271] zwp_text_input_v3#59.done(11) [4255967.276] zwp_text_input_v3#59.done(12) [4255967.278] -> zwp_text_input_v3#59.set_content_type(0, 5) [4255967.281] -> zwp_text_input_v3#59.set_cursor_rectangle(158, 54, 1, 18) [4255967.283] -> zwp_text_input_v3#59.commit() [4255967.342] zwp_text_input_v3#59.done(13) [4255974.655] -> wp_linux_drm_syncobj_timeline_v1#75.destroy() [4255974.694] -> wl_buffer#92.destroy() [4255974.742] -> wp_linux_drm_syncobj_timeline_v1#51.destroy() [4255974.750] -> wl_buffer#88.destroy() [4255975.765] -> zwp_linux_dmabuf_v1#32.create_params(new id zwp_linux_buffer_params_v1#96) [4255975.773] -> zwp_linux_buffer_params_v1#96.add(fd 178, 0, 0, 6144, 33554432, 533253) [4255975.777] -> zwp_linux_buffer_params_v1#96.create_immed(new id wl_buffer#50, 1536, 2304, 875708993, 0) [4255975.786] -> wp_linux_drm_syncobj_manager_v1#35.import_timeline(new id wp_linux_drm_syncobj_timeline_v1#89, fd 189) [4255975.794] -> zwp_linux_buffer_params_v1#96.destroy() [4255975.808] -> xdg_surface#63.set_window_geometry(0, 0, 1440, 2560) [4255975.814] -> xdg_surface#63.ack_configure(9422) [4255975.819] -> wl_surface#33.frame(new id wl_callback#66) [4255975.826] -> wp_presentation#29.feedback(wl_surface#33, new id wp_presentation_feedback#67) [4255975.835] -> wp_linux_drm_syncobj_surface_v1#72.set_acquire_point(wp_linux_drm_syncobj_timeline_v1#71, 0, 128) [4255975.838] -> wp_linux_drm_syncobj_surface_v1#72.set_release_point(wp_linux_drm_syncobj_timeline_v1#89, 0, 1) [4255975.840] -> wl_surface#33.attach(wl_buffer#50, 0, 0) [4255975.844] -> wl_compositor#4.create_region(new id wl_region#95) [4255975.847] -> wl_region#95.add(0, 0, 1080, 1920) [4255975.858] -> wl_surface#33.set_input_region(wl_region#95) [4255975.860] -> wl_region#95.destroy() [4255975.862] -> wl_compositor#4.create_region(new id wl_region#81) [4255975.864] -> wl_region#81.add(0, 0, 1080, 1920) [4255975.866] -> wl_surface#33.set_opaque_region(wl_region#81) [4255975.868] -> wl_region#81.destroy() [4255975.873] -> wp_viewport#54.set_source(0.00000000, 0.00000000, 1080.00000000, 1920.00000000) [4255975.877] -> wp_viewport#54.set_destination(-1, -1) [4255975.880] -> wl_surface#33.damage(0, 0, 1080, 1920) [4255975.882] -> wl_surface#33.commit() kwin sends a configure event with 1440x2560 as expected (my monitor's resolution is 1080x1920 and the scale factor is 75%), but chromium resizes the window to 1080x1920 instead of 1440x2560 (it's in logical pixels, it's different from the buffer size, which should be 1080x1920). This looks like a chromium bug, I don't think we can help you with this issue. Can you report this issue to Chromium developers please? -- You are receiving this mail because: You are watching all bug changes.
