[neon] [Bug 485494] fcitx5 qt6 library cause desktop failed to start, their maintainer suggests rebuilding the package against new qt
https://bugs.kde.org/show_bug.cgi?id=485494 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Leonard Lausen --- It seems this issue is introduced in fcitx-config-qt 5.1.4-0xneon+22.04+jammy+release+build3 whereas the older 5.1.3-1+22.04+jammy+release+build1 works fine. Is there an archive of the prior packages available? For example, something similar to https://snapshot.debian.org/ for Debian? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462984] [Wayland] Disabling Laptop monitor breaks icon and window button scaling on external monitor
https://bugs.kde.org/show_bug.cgi?id=462984 --- Comment #2 from Leonard Lausen --- Printenv shows PLASMA_USE_QT_SCALING=1. Maybe that's the default for Wayland? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462984] [Wayland] Disabling Laptop monitor breaks icon and window button scaling on external monitor
https://bugs.kde.org/show_bug.cgi?id=462984 --- Comment #1 from Leonard Lausen --- Created attachment 154551 --> https://bugs.kde.org/attachment.cgi?id=154551=edit Screenshot of buggy scaling -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462984] New: [Wayland] Disabling Laptop monitor breaks icon and window button scaling on external monitor
https://bugs.kde.org/show_bug.cgi?id=462984 Bug ID: 462984 Summary: [Wayland] Disabling Laptop monitor breaks icon and window button scaling on external monitor Classification: Plasma Product: kwin Version: 5.26.4 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- Created attachment 154550 --> https://bugs.kde.org/attachment.cgi?id=154550=edit Screenshot with both displays SUMMARY With a FullHD Laptop display and 2K external display, disabling the laptop display (closing the laptop lid) breaks icon and window button scaling on the remaining display. It doesn't matter if the laptop display or external display is configured as primary. STEPS TO REPRODUCE 1. Obtain laptop with FullHD screen and 2K external monitor. 2. Start a Wayland session with both displays. 3. Close laptop lid OBSERVED RESULT Window icon (upper left corner of the window) as well as the window minimize, maximize and close buttons scale breaks and their size doubles. EXPECTED RESULT Window icon and button scale is not affected by disabling the laptop display SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100 Qt Version: 5.15.6 ADDITIONAL INFORMATION See screenshots attached -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 --- Comment #5 from Leonard Lausen --- Created attachment 154487 --> https://bugs.kde.org/attachment.cgi?id=154487=edit drm_info.txt -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 Leonard Lausen changed: What|Removed |Added CC||vlad.zahorod...@kde.org --- Comment #4 from Leonard Lausen --- The verbose DRM dmesg log shows that all configurations tried by kwin fail the kernel drm_atomic_plane_check, specifically the plane_switching_crtc sanity check [1], meaning that kwin triggers unsupported direct switching of CRTCs. Any ideas why that may happen? msm_dpu ae01000.display-controller: [drm:drm_atomic_check_only] [PLANE:41:plane-0] switching CRTC directly msm_dpu ae01000.display-controller: [drm:drm_atomic_check_only] [PLANE:41:plane-0] atomic core check failed I also noticed that above kwin_wayland_drm output says `"rotation": 1` and `"rotation"=invalid value: 1`. @vladz uploaded a log containing `"rotation": 1` at https://invent.kde.org/-/snippets/1976 Any ideas if that is the root-cause? [1]: https://github.com/torvalds/linux/blob/faf68e3523c21d07c5f7fdabd0daf6301ff8db3f/drivers/gpu/drm/drm_atomic.c#L565-L581 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 --- Comment #3 from Leonard Lausen --- Created attachment 154013 --> https://bugs.kde.org/attachment.cgi?id=154013=edit dmesg with verbose DRM logging -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 --- Comment #2 from Leonard Lausen --- Attaching kernel log with verbose DRM logging, which may help determining why KWin is issuing an invalid command and which. KWin is started at [17471.518135] and killed at [17510.700261]. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] New: "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 Bug ID: 462214 Summary: "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU) Classification: Plasma Product: kwin Version: 5.26.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- Created attachment 154000 --> https://bugs.kde.org/attachment.cgi?id=154000=edit startplasma-wayland debug log KWin Wayland session is currently broken on ARM devices such as Acer Spin 513 Chromebook with Qualcomm Snapdragon 7c [1] if an external display is used. There are no issues with using the KWin X11 session in this setting with external display, nor any issues with the KWin Wayland session as long as no external display is connected. STEPS TO REPRODUCE 1. Obtain a laptop with Qualcomm Snapdragon chipset 2. From a tty run `export QT_LOGGING_RULES="kwin_*.debug=true"; startplasma-wayland > ~/startplasma-wayland.log 2>&1 ` 3. Wait a minute and `killall startplasma-wayland` from the serial console (as kwin took over the tty and can't be interrupted) OBSERVED RESULT The tty continues to be displayed and kwin fails to start a graphical session and hangs indefinitely. EXPECTED RESULT kwin successfully starts a plasma session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.0.8 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Full startplasma-wayland.log attached. Also attached is startplasma-wayland-newuser.log which contains the debug log upon reproducing with a fresh user (sudo adduser test). Both logs are substantially similar, but have small differences in the debug messages regarding Drm objects. Relevant excerpt: No backend specified, automatically choosing drm kwin_wayland_drm: Skipping KMS incapable drm device node at "/dev/dri/card0" kwin_wayland_drm: drmModeAddFB2WithModifiers is supported on GPU "/dev/dri/card1" kwin_wayland_drm: Using Atomic Mode Setting on gpu "/dev/dri/card1" kwin_wayland_drm: Number of planes on GPU "/dev/dri/card1" : 4 kwin_wayland_drm: Plane 41 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=125829120, "SRC_H"=70778880, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=1920, "CRTC_H"=1080, "FB_ID"=68, "CRTC_ID"=65, "rotation"=invalid value: 1, "IN_FORMATS"=42 kwin_wayland_drm: Plane 47 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=125829120, "SRC_H"=70778880, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=1920, "CRTC_H"=1080, "FB_ID"=68, "CRTC_ID"=66, "rotation"=invalid value: 1, "IN_FORMATS"=48 kwin_wayland_drm: Plane 53 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=54 kwin_wayland_drm: Plane 59 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=60 kwin_wayland_drm: Crtc 65 has properties "MODE_ID"=69, "ACTIVE"=1, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" not found kwin_wayland_drm: Crtc 66 has properties "MODE_ID"=71, "ACTIVE"=1, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" not found [...] kwin_core: KGlobalAcceld inited kwin_core: Attempting to load the OpenGL scene kwin_scene_opengl: Egl Initialize succeeded kwin_scene_opengl: EGL version: 1 . 5 kwin_scene_opengl: Created EGL context with attributes: Version requested: true Version:3.1 Robust: true Reset on video memory purge:false Forward compatible: false Core profile: false Compatibility profile: false High priority: true kwin_scene_opengl: Created EGL context with attributes: Version requested: true Version:3.1 Robust: true Reset on video memory purge:false Forward compatible: false Core profile: false Compatibility profile: false High priority: true OpenGL vendor string: freedreno OpenGL renderer string: FD618 OpenGL version string: 3.3 (Core Profile) Mesa 22.2.4 OpenGL shading language version string: 3.30 Driver: Unknown GPU class: Unknown OpenGL version: 3.3 GLSL version: 3.30 Mesa version: 22.2.4 Linux kernel version: 6.0.8 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_scene_opengl: Filter multi-plane format 961959257
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 --- Comment #1 from Leonard Lausen --- Created attachment 154001 --> https://bugs.kde.org/attachment.cgi?id=154001=edit startplasma-wayland debug log based on a new test user -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input
https://bugs.kde.org/show_bug.cgi?id=435338 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455720] Night Light broken on ARM devices (Missing Color Transform Matrix support)
https://bugs.kde.org/show_bug.cgi?id=455720 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455720] New: Night Light broken on ARM devices (Missing Color Transform Matrix support)
https://bugs.kde.org/show_bug.cgi?id=455720
Bug ID: 455720
Summary: Night Light broken on ARM devices (Missing Color
Transform Matrix support)
Product: kwin
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: platform-drm
Assignee: kwin-bugs-n...@kde.org
Reporter: leon...@lausen.nl
Target Milestone: ---
Night Light is currently broken on ARM devices such as Acer Spin 513 Chromebook
with Qualcomm Snapdragon 7c [1], as it relies on legacy GAMMA_LUT which is not
supported by the Qualcomm SoCs.
Instead of relying on GAMMA_LUT, these SoCs implement Color Transform Matrix
(CTM), which for example Chrome OS uses to implement their version of night
light. Both GAMMA_LUT and TM are configured through the KMS CRTC Abstraction
[2].
>From IRC #aarch64-laptops:
> robclark | leezu: on CrOS we use display CTM (CRTC property) on internal
> display.. one could also use the GPU for that.. not sure off the top of my
> head what different de's support
> robclark | leezu: yes, that is correct.. GAMMA_LUT is not supported, CTM
> (color transform matrix) is the way to achieve color transform
> robclark | not supported in hw.. CTM is a more general purpose feature
> robclark | GAMMA_LUT is kinda the legacy way, CTM is the new hotness ;-)
It would be great to support Night Light on ARM Laptops by implementing Night
Light via Color Transform Matrix instead of GAMMA_LUT.
drm_info output showing lack of GAMMA_LUT support:
Node: /dev/dri/card1
├───Driver: msm (MSM Snapdragon DRM) version 1.9.0 (20130625)
│ ├───DRM_CLIENT_CAP_STEREO_3D supported
│ ├───DRM_CLIENT_CAP_UNIVERSAL_PLANES supported
│ ├───DRM_CLIENT_CAP_ATOMIC supported
│ ├───DRM_CLIENT_CAP_ASPECT_RATIO supported
│ ├───DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported
│ ├───DRM_CAP_DUMB_BUFFER = 1
│ ├───DRM_CAP_VBLANK_HIGH_CRTC = 1
│ ├───DRM_CAP_DUMB_PREFERRED_DEPTH = 0
│ ├───DRM_CAP_DUMB_PREFER_SHADOW = 0
│ ├───DRM_CAP_PRIME = 3
│ ├───DRM_CAP_TIMESTAMP_MONOTONIC = 1
│ ├───DRM_CAP_ASYNC_PAGE_FLIP = 0
│ ├───DRM_CAP_CURSOR_WIDTH = 64
│ ├───DRM_CAP_CURSOR_HEIGHT = 64
│ ├───DRM_CAP_ADDFB2_MODIFIERS = 1
│ ├───DRM_CAP_PAGE_FLIP_TARGET = 0
│ ├───DRM_CAP_CRTC_IN_VBLANK_EVENT = 1
│ ├───DRM_CAP_SYNCOBJ = 1
│ └───DRM_CAP_SYNCOBJ_TIMELINE = 0
├───Device: platform qcom,sc7180-mdss
│ └───Available nodes: primary, render
├───Framebuffer size
│ ├───Width: [0, 5120]
│ └───Height: [0, 4096]
├───Connectors
│ ├───Connector 0
│ │ ├───Object ID: 32
│ │ ├───Type: eDP
│ │ ├───Status: connected
│ │ ├───Physical size: 294x165 mm
│ │ ├───Subpixel: unknown
│ │ ├───Encoders: {0}
│ │ ├───Modes
│ │ │ └───1920x1080@60.00 preferred driver phsync nvsync
│ │ └───Properties
│ │ ├───"EDID" (immutable): blob = 61
│ │ ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│ │ ├───"link-status": enum {Good, Bad} = Good
│ │ ├───"non-desktop" (immutable): range [0, 1] = 0
│ │ ├───"TILE" (immutable): blob = 0
│ │ └───"CRTC_ID" (atomic): object CRTC = 59
│ └───Connector 1
│ ├───Object ID: 34
│ ├───Type: DisplayPort
│ ├───Status: disconnected
│ ├───Encoders: {1}
│ └───Properties
│ ├───"EDID" (immutable): blob = 0
│ ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│ ├───"link-status": enum {Good, Bad} = Good
│ ├───"non-desktop" (immutable): range [0, 1] = 0
│ ├───"TILE" (immutable): blob = 0
│ └───"CRTC_ID" (atomic): object CRTC = 0
├───Encoders
│ ├───Encoder 0
│ │ ├───Object ID: 31
│ │ ├───Type: DSI
│ │ ├───CRTCS: {0, 1}
│ │ └───Clones: {0}
│ └───Encoder 1
│ ├───Object ID: 33
│ ├───Type: TMDS
│ ├───CRTCS: {0, 1}
│ └───Clones: {1}
├───CRTCs
│ ├───CRTC 0
│ │ ├───Object ID: 59
│ │ ├───Legacy info
│ │ │ ├───Mode: 1920x1080@60.00 preferred driver phsync nvsync
│ │ │ └───Gamma size: 0
│ │ └───Properties
│ │ ├───"ACTIVE" (atomic): range [0, 1] = 1
│ │ ├───"MODE_ID" (atomic): blob = 66
│ │ │ └───1920x1080@60.00 preferred driver phsync nvsync
│ │ ├───"OUT_FENCE_PTR" (atomic): range [0, UINT64_MAX] = 0
│ │ ├───"VRR_ENABLED": range [0, 1] = 0
│ │ └───"CTM": blob = 0
│ └───CRTC 1
│ ├───Object ID: 60
│ ├───Legacy info
│ │ └───Gamma size: 0
│ └───Properties
│ ├───"ACTIVE" (atomic): range [0, 1] = 0
│ ├───"MODE_ID" (atomic): blob = 0
│ ├───"OUT_FENCE_PTR" (atomic): range [0, UINT64_MAX] = 0
│ ├───"VRR_ENABLED": range [0, 1] = 0
│ └───"CTM": blob = 0
└───Planes
├───Plane 0
│ ├───Object ID: 35
│ ├───CRTCs: {0, 1, 2, 3, 4, 5, 6, 7}
│ ├───Legacy info
│ │ ├───FB ID: 63
[umbrello] [Bug 115269] Implement the UML 2.0 standard
https://bugs.kde.org/show_bug.cgi?id=115269 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428854] Nightcolor fails to activate after KWin or the whole session is restarted; must manually toggle it off and on again
https://bugs.kde.org/show_bug.cgi?id=428854 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432436] Keyboard layout with variant in 2nd slot prevents switching back to layout in 1st slot
https://bugs.kde.org/show_bug.cgi?id=432436 Leonard Lausen changed: What|Removed |Added Resolution|WORKSFORME |UPSTREAM --- Comment #6 from Leonard Lausen --- I responded upstream that the proposed patch doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crashes and display issues with mixed non-hiDPI / hiDPI multi-screen setup on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 Leonard Lausen changed: What|Removed |Added Summary|Crash in|Crashes and display issues |QMessageLogger::fatal when |with mixed non-hiDPI / |removing screen containing |hiDPI multi-screen setup on |system tray on wayland |wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 --- Comment #8 from Leonard Lausen --- As this bug is about Wine + XWayland, it's not fixed by the Wine Wayland version. Also I don't think it's clear if the XWayland issue reported here is a upstream bug or kwin bug. Compiling Wine Wayland branch can be used as a workaround. I wouldn't bother with the Xwayland issue as the workaround should in due time become part of stable Wine release. But others may feel different and may want to fix the Xwayland issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 --- Comment #6 from Leonard Lausen --- FYI, Alexandros fixed the KDE related bugs in the wine wayland branch and since March 4 2021 it works well (and much better than the XWayland version). The only caveat is that at this point Wine applications will always use en-us keyboard layout, but that will be fixed later. To install: mkdir -p ~/src/ cd ~/src git clone -b wayland https://gitlab.collabora.com/alf/wine/ ./configure --with-wayland make -j$(nproc) To use: WINEARCH="win32" DISPLAY= WAYLAND_DISPLAY=wayland-0 WINEPREFIX=~/.wine_wayland ~/src/wine/wine program.exe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 --- Comment #5 from Leonard Lausen --- Created attachment 136476 --> https://bugs.kde.org/attachment.cgi?id=136476=edit system-tray and layout issue when system tray on 4K screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 --- Comment #4 from Leonard Lausen --- Created attachment 136475 --> https://bugs.kde.org/attachment.cgi?id=136475=edit desktop background issue when system tray on FHD screen resolved after right click Note the filesize of this .png screenshot was double the size of screenshot taken before "right click" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 --- Comment #3 from Leonard Lausen --- Created attachment 136474 --> https://bugs.kde.org/attachment.cgi?id=136474=edit desktop background issue when system tray on FHD screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 Leonard Lausen changed: What|Removed |Added Version|5.20.4 |5.21.2 CC||leon...@lausen.nl --- Comment #2 from Leonard Lausen --- Thank you Nate for taking a look. I think the behavior has improved as of Plasma 5.21. The session/plasmashell does not crash anymore when removing the screen containing the system try. However, the multi-screen behavior is not completely stable yet either. I observed two issues (please let me know if you'd rather have a new bug-report). Further, in the first message I forgot to include that the main screen (laptop screen) of the setup is a 4K screen and scaled, whereas the external screen is a FHD screen and not scaled. Issue 1: plasmashell can trigger qt5-wayland crash when moving the system tray between screens: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7fb5a0838d51 in raise () at /lib64/libc.so.6 #5 0x7fb5a0822536 in abort () at /lib64/libc.so.6 #6 0x7fb5a0c29c97 in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) [clone .cold] () at /usr/lib64/libQt5Core.so.5 #7 0x7fb59f002a50 in QtWaylandClient::QWaylandDisplay::blockingReadEvents() () at /usr/lib64/libQt5WaylandClient.so.5 #8 0x7fb59f002c3d in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) () at /usr/lib64/libQt5WaylandClient.so.5 #9 0x7fb59f00805e in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) () at /usr/lib64/libQt5WaylandClient.so.5 #10 0x7fb59c03e012 in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) () at /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #11 0x7fb5a274377c in QSGRenderThread::syncAndRender(QImage*) () at /usr/lib64/libQt5Quick.so.5 #12 0x7fb5a2743f47 in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #13 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #14 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #15 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fb5791b0640 (LWP 67852) "QSGRenderThread"): #1 0x7fb5a0c66e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5a2741ad7 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fb5a2743f89 in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #6 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fb5737fe640 (LWP 65416) "Thread (pooled)"): #1 0x7fb5a0c66dc5 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5a0c64762 in QThreadPoolThread::run() () at /usr/lib64/libQt5Core.so.5 #3 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #5 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fb4f3fff640 (LWP 3076) "QSGRenderThread"): #1 0x7fb5a0c66e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5a2741ad7 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fb5a2743f89 in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #6 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fb4fac9b640 (LWP 3047) "QSGRenderThread"): #1 0x7fb5a0c66e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5a2741ad7 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fb5a2743f89 in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #6 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fb511ffb640 (LWP 2700) "GlobalQueue[08]"): #1 0x7fb5a0c66e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5702a11e0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fb5702a4d96 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libK
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #11 from Leonard Lausen --- It turns out this is due to a mismatch in fontconfig (too recent) and font file (too old) in Gentoo. See https://bugs.gentoo.org/716856 I opened an upstream bug in Poppler to suggest the idea that poppler may warn the user if the chosen fallback font can't render all characters in the document: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1054 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 Leonard Lausen changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #10 from Leonard Lausen --- I used qt5/demos/poppler_qt5viewer from poppler to confirm that this is a poppler bug. If I compile qt5/demos/poppler_qt5viewer on Ubuntu 20.04, the checkboxes show up fine. On my Gentoo system they do not. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #9 from Leonard Lausen --- I built Okular 20.04.3 against poppler 0.86 (which matches the versions used in Ubuntu 20.04), but the issue persists on my system. Do you have any suggestions how to further debug? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #8 from Leonard Lausen --- I rebuilt Okular 20.12.2 against poppler 0.86, but the issue persists on my system. Any ideas what component could cause the issue? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #7 from Leonard Lausen --- I was able to reproduce Albert's "Works fine for me" on Ubuntu 20.04 system with poppler 0.86. I'll try poppler 0.86 on the system that currently exhibits the issue and report back. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #6 from Leonard Lausen --- I tried to reproduce Albert's "Works fine for me" on Ubuntu 20.04 system with poppler 0.86. I'll try poppler 0.86 on the system that currently exhibits the issue and report back. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #5 from Leonard Lausen --- Created attachment 136404 --> https://bugs.kde.org/attachment.cgi?id=136404=edit Standard mode -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #4 from Leonard Lausen --- Created attachment 136403 --> https://bugs.kde.org/attachment.cgi?id=136403=edit Show forms mode -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #3 from Leonard Lausen --- Thank you Albert. That's very interesting. Can you share more details on your system configuration (Okular version, poppler version)? I attached two screenshots to show that the boxes do not show up correctly in my environment. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #1 from Leonard Lausen --- I'm using Okular compiled with latest poppler 21.03.0. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 --- Comment #9 from Leonard Lausen --- I opened a related bug at https://bugs.kde.org/show_bug.cgi?id=433979 which however, unlike the current one, is not reproducible with Evince. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] New: American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 Bug ID: 433979 Summary: American tax forms checkbox state cannot been seen when form is hidden Product: okular Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY IRS Tax forms such as https://www.irs.gov/pub/irs-pdf/f1040.pdf contain various checkboxes. In "Show Form" mode, these checkboxes are editable, but they do no longer show up in the printout or no-"Show Form" mode. This is unlike Gnome's Evince, which is also poppler based but does show the ticked checkboxes in printout. As this works in Evince, suspect to be a Okular specific rendering problem? STEPS TO REPRODUCE 1. wget https://www.irs.gov/pub/irs-pdf/f1040.pdf 2. okular f1040.pdf 3. Click "Show Forms" 4. Check a box 5. Print the form or click "Show Forms" again OBSERVED RESULT Ticked checkbox is no longer displayed. EXPECTED RESULT Ticked checkbox is visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 ADDITIONAL INFORMATION This appears unrelated to the XFA content. The same problem applies to f1040-noxfa.pdf file obtained via "pdftk f1040.pdf output f1040-noxfa.pdf drop_xfa" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 Leonard Lausen changed: What|Removed |Added Version|1.11.1 |20.12.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 --- Comment #8 from Leonard Lausen --- I have reproduced this issue with Okular 20.12.2 and Poppler 21.03.0. I opened the "PDF file showing the problem" in Okular, clicked "Show forms" ticked a box, hide the forms and saved the file. The box no longer shows up after hiding the forms. I further confirmed that Evince, which is also based on poppler fails to show the checked box. In fact, clicking any other box in Evince will also fail to show. Finally, I confirmed that opening the modified PDF in either Master PDF Editor [1] or Firefox 86 does show the ticked box. Thus I agree with Albert that this is most likely a poppler bug. @Andreas, would you like to report the bug at https://gitlab.freedesktop.org/poppler/poppler/-/issues/ ? [1] https://code-industry.net/masterpdfeditor/ a proprietary PDF software with Linux support -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 --- Comment #5 from Leonard Lausen --- I think it's valid to mention the Wayland build in this issue. In fact you can try compiling it from source. In my experience, it works well for some applications but there were KDE specific bugs for others. However, I also noted KDE specific bugs with Xwayland Wine, so it's possible that the drag bug you report here is also KDE specific. Have you tried if the Xwayland drag works on Gnome Wayland session or Weston? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl --- Comment #2 from Leonard Lausen --- Are you using the https://gitlab.collabora.com/alf/wine/ wayland wine build? Or are you using stable wine with xwayland? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Keyboard layout's variant for the first layout is not applied
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #12 from Leonard Lausen --- > Oh, the other workaround I forgot to mention: > just add some variants to both layouts. I compiled 5.20.90 again and Neo variant does work fine now even when on position 1. I assume this is because I manually selected "Default" variant for US English while I was still on 5.20 (ie. both layouts now have a variant configured) I'll not touch the setting for as not to risk any problems :) Please let me know once you have a patch that fixes the regression and I'm happy to do further testing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Keyboard layout's variant for the first layout is not applied
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #11 from Leonard Lausen --- Reported as https://bugs.kde.org/show_bug.cgi?id=432436 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432436] New: Keyboard layout with variant in 2nd slot prevents switching back to layout in 1st slot
https://bugs.kde.org/show_bug.cgi?id=432436 Bug ID: 432436 Summary: Keyboard layout with variant in 2nd slot prevents switching back to layout in 1st slot Product: kwin Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl CC: butir...@gmail.com Target Milestone: --- Flags: Wayland+, X11- SUMMARY Both on X11 and Wayland session, configuring German Neo2 Layout as 2nd layout and US English layout as 1st layout will prevent switching back from Neo2 to US layout via keyboard shortcut (Right-Ctrl+Right-shift). There is no such problem if the order is inverse. See https://bugs.kde.org/show_bug.cgi?id=432367#c1 This issue affects both Plasma 5.20.5 and 5.20.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Keyboard layout's variant for the first layout is not applied
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #10 from Leonard Lausen --- > Thanks for testing. Actually I can't explain right now why the order of > layouts matters for the shortcut functionality. > It would be good if you could check on X11 also. I confirmed that also Plasma 5.20 X11 session, if I use Neo as 1st layout and US as 2nd layout, I can switch between them via "Right-Ctrl + Right-Shift" without getting stuck. But once placing Neo as layout 2 and US as layout 1, switching will get stuck once selecting Neo. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375518] global shortcuts show some oddities with foreign keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=375518 --- Comment #12 from Leonard Lausen --- Have you tried switching the order of layouts? In https://bugs.kde.org/show_bug.cgi?id=432367 I observe related issues that only occur if US layout is on position 1 in the settings screen and my custom layout is on position 2. However, when moving the custom layout to position 1 and US layout to position 2 fixes there are no problems. Note that the Layout Settings have Move Up/Down buttons to change layout order. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #7 from Leonard Lausen --- In Plasma 5.20, if I use Neo as 1st layout and US as 2nd layout, I can switch between them via "Right-Ctrl + Right-Shift" without getting stuck. But once placing Neo as layout 2 and US as layout 1, switching will get stuck once selecting Neo. Further I notice that the problem with "Alt key can no longer activate layer 4 (Ebene 4)" is also present on Plasma 5.20 if Neo is selected as 2nd layout. However, Alt key works correctly as long as Neo is selected as 1st layout. Thus I think the only regression here is "variants of the first layout" support. The others are separate bugs related to difference in handling of 1st and n-th layout. Are these known issues? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375518] global shortcuts show some oddities with foreign keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=375518 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #6 from Leonard Lausen --- > Leonard, this is probably because the shortcuts of these layouts do not match. > I wonder if you had similar problems with the same layouts but in different > order? The problem does not occur when using Default variant for German or placing the German Neo variant on position 1 and US on 2. > So if it worked for you earlier, maybe it was on X11? No, I was using Wayland with Plasma 5.20 and I haven't noticed this problem there. In fact the Right-Shift and Right-Ctrl key used as shortcut by me do not differ between the US and Neo. Thus I don't think it's related to 375518. If you like, I can reinstall kwin 5.20 and double check that the shortcut works fine there. > We could check it right now: > add 3 layouts in different order, and watch how it behaves on the shortcuts: > E.g.: US, US, Neo -> US, Neo, US With 4 layouts: English US, English UK, German Neo, German Default I can switch from US to UK to Neo, but then get stuck. I also notice that switching from US to UK, the overlay notifying me about the new layout shows up immediately. For UK to Neo, the overlay does not show up until I switch the application in focus (eg to my browser where I am writing the bug report now) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #3 from Leonard Lausen --- Specifically, I can activate the neo2 layout via the shortcut fine (Pressing "Right-Ctrl+Right-Shift" switches from US layout to neo2), but pressing the shortcut again does not switch back to US layout. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367
--- Comment #2 from Leonard Lausen ---
Thank you Andrey for your work on the Plasma Wayland code and for pointing out
the workaround. The workaround works almost. The only major issue I face now is
that the right Alt key no longer works for activating layer 4 of the layout (cf
https://neo-layout.org/ "Ebene 4" in the picture in the upper right corner).
Pressing the Right Alt key does not perform any action.
For example, Pressing "Right-Alt + D" should result in "Arrow down", but with
your workaround results in "a" (which is the expected result of pressing "D"
but not for "Right-Alt + D").
A second minor issue I find is that switching keyboard layouts via the shortcut
("Right-Ctrl+Right-Shift" in my case) does not work reliably anymore after
moving neo layout to second position.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 432367] New: Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367 Bug ID: 432367 Summary: Neo2 keyboard layout no longer works with Plasma 5.21 beta Product: kwin Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY After updatin from Plasma 5.20 to 5.21 beta, German Neo2 Layout stops working and the standard German keyboard layout is used instead. STEPS TO REPRODUCE 1. Go to keyboard layout settings 2. Add German (Neo 2) variant 3. Enable the variant and press the key corresponding to a in qwerty. input a is registered instead of expected input u (cf https://neo-layout.org/) OBSERVED RESULT Inputs registered are based on standard German keyboard variant EXPECTED RESULT Inputs registered are based on Neo 2 German keyboard variant SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo with Plasma 5.21 Beta KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm using wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] New: Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 Bug ID: 430835 Summary: Crash in QMessageLogger::fatal when removing screen containing system tray on wayland Product: plasmashell Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: leon...@lausen.nl CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In Wayland Sessions, if the system tray was moved to an external screen, the plasma session and many KDE Applications will crash upon removal of the external screen. The crash occurs during a call to QMessageLogger. STEPS TO REPRODUCE 1. Start a KDE Wayland Session 2. Add a second screen 3. Right click on the system tray and "Edit Panel" 4. Drag panel to the new screen and position it there 5. Disconnect second screen 6. Observe crash 7. Reconnect second srceen 8. Observe that plasmashell will start again OBSERVED RESULT plasmashell crashes. System tray disappears, tens of Dr Konqi windows show up for various KDE Background daemons. EXPECTED RESULT Panel moves to remaining screen. No crash SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.10.2-gentoo OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 620 ADDITIONAL INFORMATION Exemplar backtrace (all the backtraces look similar): Application: KOrganizer Reminder Daemon (korgac), signal: Aborted [KCrash Handler] #4 0x7fb88a5cddd1 in raise () from /lib64/libc.so.6 #5 0x7fb88a5b7536 in abort () from /lib64/libc.so.6 #6 0x7fb88aa69c97 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #7 0x7fb8880d0a50 in QtWaylandClient::QWaylandDisplay::checkError() const () from /usr/lib64/libQt5WaylandClient.so.5 #8 0x7fb8880d1a53 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /usr/lib64/libQt5WaylandClient.so.5 #9 0x7fb88ac59b1c in void doActivate(QObject*, int, void**) () from /usr/lib64/libQt5Core.so.5 #10 0x7fb88ac5cd06 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /usr/lib64/libQt5Core.so.5 #11 0x7fb88ac5d45b in QSocketNotifier::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #12 0x7fb88b6046af in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7fb88ac2b018 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x7fb88ac76e8e in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5Core.so.5 #15 0x7fb63867 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #16 0x7fb63af0 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #17 0x7fb63b7f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #18 0x7fb88ac7645b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #19 0x7fb88ac29a43 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #20 0x7fb88ac314b0 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #21 0x55daeb3e6a18 in main () [Inferior 1 (process 2324) detached] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426198] kwin wayland build has X11 dependency
https://bugs.kde.org/show_bug.cgi?id=426198 --- Comment #4 from Leonard Lausen --- I'm building a full KDE Plasma desktop environment from source on Gentoo. Thanks to the great work of KDE community and others, Plasma wayland is fully usable on my setup since a couple of months and I am curious what it takes to remove all X11 packages. In general, Gentoo makes it easy to enable/disable certain build-time features such as X11 via USEFLAGs. Thus removal off X11 packages is possible in principle. If you are aware of any dependencies that block this, collecting the list here will make it easier to work towards the goal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426198] kwin wayland build has X11 dependency
https://bugs.kde.org/show_bug.cgi?id=426198 --- Comment #2 from Leonard Lausen --- Thank you for elaborating David. Where are the dependencies that also require X anyways tracked? If they aren't tracked, would it be sensible to track them in this bug report? Given the existing runtime support for disabling xwayland, this seems to be mainly an issue with the build system and the dependencies. On September 5, 2020 8:14:01 AM PDT, David Edmundson wrote: > >https://bugs.kde.org/show_bug.cgi?id=426198 > >David Edmundson changed: > > What|Removed |Added > > Resolution|--- |LATER > CC||k...@davidedmundson.co.uk > Status|REPORTED|RESOLVED > >--- Comment #1 from David Edmundson --- >Compiling against X and using it on wayland only are very different topics. > >You can already use kwin only for wayland. Simply don't pass the --xwayland >parameter. > >The headers and linked libraries are relatively tiny and our dependencies also >require X anyway. We ultimately plan to slowly phase some of that out but not >in the very near future. > >-- >You are receiving this mail because: >You reported the bug. >You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426198] kwin wayland build has X11 dependency
https://bugs.kde.org/show_bug.cgi?id=426198 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 426199] frameworks-kglobalaccel build requires X11 on Linux
https://bugs.kde.org/show_bug.cgi?id=426199 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 426199] New: frameworks-kglobalaccel build requires X11 on Linux
https://bugs.kde.org/show_bug.cgi?id=426199 Bug ID: 426199 Summary: frameworks-kglobalaccel build requires X11 on Linux Product: frameworks-kglobalaccel Version: 5.73.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- Created attachment 131426 --> https://bugs.kde.org/attachment.cgi?id=131426=edit patch kglobalaccel supports building without X11 only on MacOS. OBSERVED RESULT Building kglobalaccel for Wayland requires building with X11 too. EXPECTED RESULT kglobalaccel can be built without X11 support on Linux. Attached is a simple patch to add an USE_X11 option to the CmakeLists.txt. There might be a more idiomatic way with ECM, but this sufficed to try build kglobalaccel without X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426198] New: kwin wayland build has X11 dependency
https://bugs.kde.org/show_bug.cgi?id=426198 Bug ID: 426198 Summary: kwin wayland build has X11 dependency Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY kwin CMakeLists.txt seems to always require X11. However, users may wish to build kwin only for wayland without X11 support. OBSERVED RESULT Building KWin for Wayland requires building KWin for X11 too. EXPECTED RESULT KWin can be build for Wayland without building for X11. An option USE_X11 can be used to toggle if X11 target is built. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424834] New: Segfault in libwayland-server.so after upgrading to 5.19.4
https://bugs.kde.org/show_bug.cgi?id=424834 Bug ID: 424834 Summary: Segfault in libwayland-server.so after upgrading to 5.19.4 Product: kwin Version: 5.19.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY Following an update of my system to 5.19.4 plasma package I can't open a wayland session anymore. Instead I receive the following segfault after entering my password on the login screen: kwin_wayland[170551]: segfault at 0 ip 7f8cf8fc1027 sp 7ffd4c683788 error 4 in libwayland-server.so.0.1.0[7f8cf8fbc000+8000] SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION The following updates were performed prior to the problem occurring: Thu Jul 30 06:29:51 2020 >>> kde-plasma/breeze-grub-5.19.4 Thu Jul 30 06:30:41 2020 >>> net-misc/rsync-3.2.2-r1 Thu Jul 30 06:31:55 2020 >>> sys-kernel/gentoo-sources-5.7.11 Thu Jul 30 06:32:15 2020 >>> dev-python/pip-20.2 Thu Jul 30 06:39:37 2020 >>> sys-devel/gdb-9.2 Thu Jul 30 06:44:07 2020 >>> dev-python/pandas-1.1.0 Thu Jul 30 06:50:57 2020 >>> sys-apps/systemd-245.5 Thu Jul 30 06:51:09 2020 >>> kde-plasma/kwallet-pam-5.19.4 Thu Jul 30 06:51:26 2020 >>> kde-plasma/plasma-workspace-wallpapers-5.19.4 Thu Jul 30 07:59:40 2020 >>> www-client/chromium-84.0.4147.105 Thu Jul 30 07:59:53 2020 >>> kde-plasma/breeze-plymouth-5.19.4 Thu Jul 30 08:00:12 2020 >>> kde-plasma/kdecoration-5.19.4 Thu Jul 30 08:01:12 2020 >>> kde-plasma/libkscreen-5.19.4 Thu Jul 30 08:02:17 2020 >>> kde-plasma/kwayland-server-5.19.4 Thu Jul 30 08:02:36 2020 >>> kde-plasma/kgamma-5.19.4 Thu Jul 30 08:02:55 2020 >>> kde-plasma/kwayland-integration-5.19.4 Thu Jul 30 08:03:14 2020 >>> kde-plasma/xembed-sni-proxy-5.19.4 Thu Jul 30 08:03:32 2020 >>> kde-plasma/polkit-kde-agent-5.19.4 Thu Jul 30 08:03:45 2020 >>> kde-plasma/ksshaskpass-5.19.4 Thu Jul 30 08:04:58 2020 >>> kde-plasma/drkonqi-5.19.4 Thu Jul 30 08:05:12 2020 >>> kde-plasma/kwrited-5.19.4 Thu Jul 30 08:06:11 2020 >>> kde-plasma/kactivitymanagerd-5.19.4 Thu Jul 30 08:06:40 2020 >>> kde-plasma/kmenuedit-5.19.4 Thu Jul 30 08:07:05 2020 >>> kde-plasma/user-manager-5.19.4 Thu Jul 30 08:08:08 2020 >>> kde-plasma/libksysguard-5.19.4 Thu Jul 30 08:09:14 2020 >>> kde-plasma/discover-5.19.4 Thu Jul 30 08:10:14 2020 >>> kde-plasma/ksysguard-5.19.4 Thu Jul 30 08:10:50 2020 >>> kde-plasma/xdg-desktop-portal-kde-5.19.4 Thu Jul 30 08:11:35 2020 >>> kde-plasma/plasma-vault-5.19.4 Thu Jul 30 08:12:13 2020 >>> kde-plasma/plasma-pa-5.19.4 Thu Jul 30 08:12:52 2020 >>> kde-plasma/plasma-sdk-5.19.4 Thu Jul 30 08:13:15 2020 >>> kde-plasma/milou-5.19.4 Thu Jul 30 08:13:45 2020 >>> kde-plasma/plasma-browser-integration-5.19.4 Thu Jul 30 08:14:51 2020 >>> kde-plasma/breeze-5.19.4 Thu Jul 30 08:15:18 2020 >>> kde-plasma/plasma-integration-5.19.4 Thu Jul 30 08:15:33 2020 >>> kde-plasma/breeze-gtk-5.19.4 Thu Jul 30 08:16:13 2020 >>> kde-plasma/kscreenlocker-5.19.4 Thu Jul 30 08:25:01 2020 >>> kde-plasma/kwin-5.19.4 Thu Jul 30 08:25:26 2020 >>> kde-plasma/libkworkspace-5.19.4 Thu Jul 30 08:26:21 2020 >>> kde-plasma/kde-cli-tools-5.19.4 Thu Jul 30 08:34:47 2020 >>> kde-plasma/plasma-workspace-5.19.4 Thu Jul 30 08:36:29 2020 >>> kde-plasma/oxygen-5.19.4 Thu Jul 30 08:36:50 2020 >>> kde-plasma/kde-gtk-config-5.19.4 Thu Jul 30 08:39:43 2020 >>> kde-plasma/plasma-nm-5.19.4 Thu Jul 30 08:40:05 2020 >>> kde-plasma/sddm-kcm-5.19.4 Thu Jul 30 08:41:21 2020 >>> kde-plasma/khotkeys-5.19.4 Thu Jul 30 08:42:30 2020 >>> kde-plasma/kinfocenter-5.19.4 Thu Jul 30 08:43:10 2020 >>> kde-plasma/kscreen-5.19.4 Thu Jul 30 08:44:45 2020 >>> kde-plasma/powerdevil-5.19.4 Thu Jul 30 08:45:19 2020 >>> kde-plasma/systemsettings-5.19.4 Thu Jul 30 08:46:27 2020 >>> kde-plasma/bluedevil-5.19.4 Thu Jul 30 08:46:47 2020 >>> kde-plasma/plymouth-kcm-5.19.4 Thu Jul 30 08:54:25 2020 >>> kde-plasma/plasma-desktop-5.19.4 Thu Jul 30 08:56:31 2020 >>> kde-plasma/kdeplasma-addons-5.19.4 Thu Jul 30 08:56:41 2020 >>> kde-plasma/plasma-meta-5.19.4 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407287] New: Ubuntu | LinuxMint | Elementary PPA build failed
https://bugs.kde.org/show_bug.cgi?id=407287 Bug ID: 407287 Summary: Ubuntu | LinuxMint | Elementary PPA build failed Product: kdenlive Version: 19.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY https://kdenlive.org/en/download/ recommends Ubuntu | LinuxMint | Elementary users to install kdenlive via the ppa. However, the ppa contains only outdated versions as the build of 19.04 failed. STEPS TO REPRODUCE 1. sudo add-apt-repository ppa:kdenlive/kdenlive-stable 2. sudo apt-get update 3. sudo apt install kdenlive OBSERVED RESULT kdenlive 18.12 is installed EXPECTED RESULT kdenlive 19.04 is installed SOFTWARE/OS VERSIONS Linux/KDE Plasma: elementary OS 5 Juno ADDITIONAL INFORMATION Build logs of the failed builds are available at https://launchpad.net/~kdenlive/+archive/ubuntu/kdenlive-stable/+packages -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 403255] Screenlock prevented by kdialog on read-only filesystem
https://bugs.kde.org/show_bug.cgi?id=403255 --- Comment #5 from Leonard Lausen --- Thanks Kai. Sorry if I misunderstood your previous comment as requiring the env variable. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 403255] Screenlock prevented by kdialog on read-only filesystem
https://bugs.kde.org/show_bug.cgi?id=403255 --- Comment #3 from Leonard Lausen --- Thanks Kai. I would argue that KDE_HOME_READONLY should not be required to avoid this freeze. Requiring KDE_HOME_READONLY means that a user must consciously want to run on a read-only system, which I guess is not very useful / common. But read-only remount due to kernel bug or cosmic ray is somewhat common, so KDE should still support users investigate and fix the root-cause if that happens. If KDE locks up the X Session, this makes debugging harder and may encourage users to force reboot their system, which in turn would make documenting and recovering from the kernel issue / bit-flip data corruption issue harder. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 403255] New: Screenlock prevented by kdialog on read-only filesystem
https://bugs.kde.org/show_bug.cgi?id=403255 Bug ID: 403255 Summary: Screenlock prevented by kdialog on read-only filesystem Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: l-softw...@lausen.nl CC: bhus...@gmail.com Target Milestone: --- SUMMARY If .config/kscreenlocker_greetrc is not writable (eg. due to emergency remount of the partition as read-only) and the user attempts to lock the screen, a dialogue containing: 'Configuration file "/home/leonard/.config/kscreenlocker_greetrc" not writable. Please contact your system administrator.' will popup and the system will freeze. It is not possible to close the dialog, neither does the lock screen show up. Logging in on tty and issuing `killall kdialog` closes the dialog. Switching back to X session, the lock screen shows up. Unlocking the system works fine. STEPS TO REPRODUCE 1. mount -o remount,ro /home 2. Lock screen OBSERVED RESULT System hangs with dialog message 'Configuration file "/home/leonard/.config/kscreenlocker_greetrc" not writable. Please contact your system administrator.' open. EXPECTED RESULT Screen is locked. Dialog with warning may/should be opened, but should not block screen locking process and cause system hang. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 4.20.2 KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397834] Native Firefox/Wayland port works poorly on Wayland Plasma
https://bugs.kde.org/show_bug.cgi?id=397834 Leonard Lausen changed: What|Removed |Added CC||l-softw...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399914] [Qt5.12]Various menus open only once
https://bugs.kde.org/show_bug.cgi?id=399914 --- Comment #8 from Leonard Lausen --- It seems the fix made it for the QT 5.12 release -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399914] [Qt5.12]Various menus open only once
https://bugs.kde.org/show_bug.cgi?id=399914 Leonard Lausen changed: What|Removed |Added CC||l-softw...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 401132] New: Crash on manually adding wifi connection
https://bugs.kde.org/show_bug.cgi?id=401132 Bug ID: 401132 Summary: Crash on manually adding wifi connection Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: l-softw...@lausen.nl Target Milestone: --- Application: kcmshell5 (5.14.3) (Compiled from sources) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.2-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I finished filling all details of the network connection (WPA 2 Enterprise) SSID, username, etc. Then I selected an already existing connection to compare the filled in details. At that moment the application crashed. The manually, newly added connection was nevertheless successfully saved and was connected to automatically at around the same time of te crashing settings dialogue. - Unusual behavior I noticed: Before adding the connection manually in the Network Settings dialogue, I tried adding it "automatically" via pressing "Connect" in the Network / wifi dialogue showing nearby networks. Nothing happened. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7e1e4b0240 (LWP 4630))] Thread 5 (Thread 0x7f7df8a34700 (LWP 4634)): #0 0x7f7e1de2dfe0 in read () from /lib64/libc.so.6 #1 0x7f7e150482c0 in g_wakeup_acknowledge () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7e15003bdf in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7e150040b0 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7f7e1500422c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f7e1b0ec51b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f7e1b09c533 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f7e1af14586 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f7e1974c835 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #9 0x7f7e1af1d608 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #10 0x7f7e17d18973 in start_thread () from /lib64/libpthread.so.0 #11 0x7f7e1de3e57f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f7df9235700 (LWP 4633)): #0 0x7f7e17d1f59c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f7df95ee1a3 in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7f7df95edef7 in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7f7e17d18973 in start_thread () from /lib64/libpthread.so.0 #4 0x7f7e1de3e57f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f7e00fef700 (LWP 4632)): #0 0x7f7e15049694 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f7e1500364b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7e15004036 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7e1500422c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f7e1b0ec51b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f7e1b09c533 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f7e1af14586 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f7e1c914269 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #8 0x7f7e1af1d608 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f7e17d18973 in start_thread () from /lib64/libpthread.so.0 #10 0x7f7e1de3e57f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f7e0999c700 (LWP 4631)): #0 0x7f7e1de32943 in poll () from /lib64/libc.so.6 #1 0x7f7e16fcb7f7 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7f7e16fcd40a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f7e0baee6d9 in QXcbEventReader::run() () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f7e1af1d608 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7f7e17d18973 in start_thread () from /lib64/libpthread.so.0 #6 0x7f7e1de3e57f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f7e1e4b0240 (LWP 4630)): [KCrash Handler] #6 0x7f7e1b0c4d1e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #7 0x7f7e1969e3e2 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Qml.so.5 #8 0x7f7e196ff32d in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const () from /usr/lib64/libQt5Qml.so.5 #9 0x7f7e19665531 in
[dolphin] [Bug 304371] Dolphin unable to set folder view properties easily in large/complex file heirarchy.
https://bugs.kde.org/show_bug.cgi?id=304371 Leonard Lausen changed: What|Removed |Added CC||l-softw...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional
https://bugs.kde.org/show_bug.cgi?id=389191 --- Comment #11 from Leonard Lausen <l-softw...@lausen.nl> --- Another one is Emacs. Unlike Firefox and Chrome it likely won't support Wayland natively in the near future either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388140] Frequent crashes (few per day) when using application launcher
https://bugs.kde.org/show_bug.cgi?id=388140 Leonard Lausen <l-softw...@lausen.nl> changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Leonard Lausen <l-softw...@lausen.nl> --- How confident are you Christoph that the problem is not part of plasmashell? I received the following reply on the sqlite mailinglist: > These kinds of things are almost always the result of heap > corruption in the application. In other words, there is nothing wrong > with SQLite. SQLite just happened to be the unlucky victim to first > stumble over the corrupted heap. In fact, we find that whenever there > is heap corruption of any sort, SQLite is more likely that most other > libraries to be the first to stumble into it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional
https://bugs.kde.org/show_bug.cgi?id=389191 --- Comment #1 from Leonard Lausen <l-softw...@lausen.nl> --- Possibly upscaling could be replaced by downscaling for the lower DPI screens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389191] New: xwayland auto-upscaling causes pixelation and should be optional
https://bugs.kde.org/show_bug.cgi?id=389191 Bug ID: 389191 Summary: xwayland auto-upscaling causes pixelation and should be optional Product: kwin Version: 5.11.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: l-softw...@lausen.nl Target Milestone: --- With a plasma wayland session and a multi-monitor (high and normal DPI) setup / scaling enabled, legacy xwayland applications are automatically scaled up, causing them to look bad on the HIDPI screen. This is especially grave if an application used predominantly during the day relies on xwayland. These legacy applications often have their own settings to adapt to HIDPI screens. I argue in that case it is better to tune the xwayland applications by hand instead of relying on autoscaling, as only in this way a sharp output can be achieved. While autoscaling is a great feature for many workflows that only seldomly use xwayland applications (thanks for developing it!), it should be optional and it should be possible to disable it. Is there some run- or compile-time option to disable the xwayland autoscaling? -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 388796] Measure actual pixel size on HiDPI displays
https://bugs.kde.org/show_bug.cgi?id=388796 Leonard Lausen <l-softw...@lausen.nl> changed: What|Removed |Added CC||l-softw...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated
https://bugs.kde.org/show_bug.cgi?id=374014 Leonard Lausen <l-softw...@lausen.nl> changed: What|Removed |Added CC||l-softw...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 373178] Blurry scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=373178 Leonard Lausen <l-softw...@lausen.nl> changed: What|Removed |Added CC||l-softw...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389189] New: wl_seat 5 problems
https://bugs.kde.org/show_bug.cgi?id=389189
Bug ID: 389189
Summary: wl_seat 5 problems
Product: kwin
Version: 5.11.95
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: l-softw...@lausen.nl
Target Milestone: ---
Some applications fail to start on a plasma wayland session due to missing
wl_seat 5 support:
wl_registry@2: error 0: invalid version for global wl_seat (6): have 4, wanted
5
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error {
repr: Os { code: 71, message: "Protocol error" } }',
src/libcore/result.rs:906:4
( https://github.com/jwilm/alacritty )
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 388140] New: Frequent crashes (few per day) when using application launcher
https://bugs.kde.org/show_bug.cgi?id=388140 Bug ID: 388140 Summary: Frequent crashes (few per day) when using application launcher Product: plasmashell Version: 5.11.4 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: l-softw...@lausen.nl CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.4) (Compiled from sources) Qt Version: 5.10.0 Frameworks Version: 5.41.0 Operating System: Linux 4.14.7-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Open the application launcher via shortcut / mouse and start typing to retrieve search result (application / desktop action). Sometimes the plasma desktop crashes during the typing or keyboard navigation in the results list. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81e59b3e00 (LWP 2825))] Thread 17 (Thread 0x7f80e159c700 (LWP 10067)): #0 0x7f81df010c9d in poll () from /lib64/libc.so.6 #1 0x7f81d9c285e6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f81d9c286fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f81df9811eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f81df92ccfa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f81df77de7a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f81e2801cf5 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #7 0x7f81df7827f4 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7f81de8c7687 in start_thread () from /lib64/libpthread.so.0 #9 0x7f81df01c03f in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f810089a700 (LWP 3252)): #0 0x7f81de8ce586 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f81df782fab in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f8124b35005 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f8124b39198 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f8124b340fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f8124b391f2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f8124b340fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f8124b3704b in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f81df7827f4 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f81de8c7687 in start_thread () from /lib64/libpthread.so.0 #10 0x7f81df01c03f in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f810109b700 (LWP 3251)): #0 0x7f81de8ce586 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f81df782fab in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f8124b35005 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f8124b39198 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f8124b340fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f8124b391f2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f8124b340fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f8124b3704b in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f81df7827f4 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f81de8c7687 in start_thread () from /lib64/libpthread.so.0 #10 0x7f81df01c03f in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f810189c700 (LWP 3250)): #0 0x7f81de8ce586 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f81df782fab in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f8124b35005 in
[plasmashell] [Bug 384806] Digital clock shows wrong time after time zone change
https://bugs.kde.org/show_bug.cgi?id=384806 --- Comment #2 from Leonard Lausen <l-softw...@lausen.nl> --- Thanks Peter. I'm on Gentoo. My /etc/timezone file contains a single line with the active time zone. Do you mean the /etc/timezone file is obsolete? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359531] [wayland] add support for xdg_shell should stop gtk3 applications from crashing
https://bugs.kde.org/show_bug.cgi?id=359531 Leonard Lausen <l-softw...@lausen.nl> changed: What|Removed |Added CC||l-softw...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384806] New: Digital clock shows wrong time after time zone change
https://bugs.kde.org/show_bug.cgi?id=384806 Bug ID: 384806 Summary: Digital clock shows wrong time after time zone change Product: plasmashell Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: l-softw...@lausen.nl Target Milestone: 1.0 Adjusting the system time zone from "Date & Time - Systems Settings Module" "Time Zone" leads to the Digital Clock Widget showing the wrong time in case of the clock being setup to show multiple timezones. The clock works correctly once plasmashell is restarted (i.e. logout, login). It seems that the clock widget does not recalculate the offsets of the displayed timezones to the system timezone, and naively applies the old offset to the changed system time, leading to a wrongly displayed time. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 384410] New: nm-applet fails to connect to APs whose SSID can't be decoded with system locale
https://bugs.kde.org/show_bug.cgi?id=384410 Bug ID: 384410 Summary: nm-applet fails to connect to APs whose SSID can't be decoded with system locale Product: plasma-nm Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: l-softw...@lausen.nl Target Milestone: --- If an AP name cannot be decoded with the system locale (or fallback locale), nm-applet will display gibberish instead of the AP name. Clicking connect will fail to connect to the network. Instead, if the AP name cannot be decoded, the BSSID should be displayed in nm-applet, which would make it possible to still connect to the network. For example, in greater China region some AP names may use the gb18030 encoding, which cannot be decoded with en_US.UTF-8 locale. The user should not be required to switch his system locale to zh_CN.gb18030 locale just to connect to networks for which the AP name cannot be decoded. Secondly, nm-applet should use LC_CTYPE to determine the encoding (and list of fallback encodings [1]) used for decoding AP names. https://bugzilla.gnome.org/show_bug.cgi?id=784415 contains more background information. [1]: https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-core/nm-utils.c?id=a47153f5b8a114ce1f0d226b33d0ad6d6ec7f150#n76 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383583] Display scale is not applied consistently to mouse pointer
https://bugs.kde.org/show_bug.cgi?id=383583 --- Comment #1 from Leonard Lausen <leon...@lausen.nl> --- Created attachment 107304 --> https://bugs.kde.org/attachment.cgi?id=107304=edit Correctly scaled mouse pointer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383583] New: Display scale is not applied consistently to mouse pointer
https://bugs.kde.org/show_bug.cgi?id=383583 Bug ID: 383583 Summary: Display scale is not applied consistently to mouse pointer Product: plasmashell Version: 5.10.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: leon...@lausen.nl CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 107303 --> https://bugs.kde.org/attachment.cgi?id=107303=edit Wrongly scaled mouse pointer Most of the time the mouse pointer is correctly scaled. If the pointer is positioned atop of some regions such as parts of settings dialogues or the window title bar, no scaling is applied. Please see the 2 pictures attached. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 378598] Scaling display affects all monitors
https://bugs.kde.org/show_bug.cgi?id=378598 Leonard Lausen <leon...@lausen.nl> changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374158] Dual screen with xrandr setting
https://bugs.kde.org/show_bug.cgi?id=374158 Leonard Lausen <leon...@lausen.nl> changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381525] Crash in QQmlBinding::getPropertyData
https://bugs.kde.org/show_bug.cgi?id=381525 Leonard Lausen <leon...@lausen.nl> changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383098] Plasma crash on audio volume change
https://bugs.kde.org/show_bug.cgi?id=383098 Leonard Lausen <leon...@lausen.nl> changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383098] Plasma crash on audio volume change
https://bugs.kde.org/show_bug.cgi?id=383098 --- Comment #1 from Leonard Lausen <leon...@lausen.nl> --- Created attachment 107082 --> https://bugs.kde.org/attachment.cgi?id=107082=edit New crash information added by DrKonqi plasmashell (5.10.4) using Qt 5.9.1 - What I was doing when the application crashed: Change of volume with connected Bluetooth speaker. Crash occasionally also happens when switching between headset and internal speakers (and then changing the volume). -- Backtrace (Reduced): #6 0x7f45a0181b50 in QQmlBinding::getPropertyData(QQmlPropertyData**, QQmlPropertyData*) const () from /usr/lib64/libQt5Qml.so.5 #7 0x7f45a0184fb2 in GenericBinding<10>::write(QV4::Value const&, bool, QFlags) () from /usr/lib64/libQt5Qml.so.5 #8 0x7f45a0185bc4 in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) () from /usr/lib64/libQt5Qml.so.5 #9 0x7f45a0182cf3 in QQmlBinding::update(QFlags) () from /usr/lib64/libQt5Qml.so.5 #10 0x7f45a0182f3e in QQmlBinding::refresh() () from /usr/lib64/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 Leonard Lausen <leon...@lausen.nl> changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 Leonard Lausen <leon...@lausen.nl> changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #15 from Leonard Lausen <leon...@lausen.nl> --- I was using QT 5.9.0. Realizing that I should update to 5.9.1 I saw that there was a bug in the qtwayland-5.9.0 ebuild which was fixed recently by kensington for the qtwayland-5.9.1 ebuild: https://github.com/gentoo/qt/commit/648d83e691da9a49cd4f76ade3c8466a377ac0b8 I.e. qtgui was not built with libinput support. So that should resolve the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 --- Comment #13 from Leonard Lausen <leon...@lausen.nl> --- Indeed I have pressed these keys, but the output did not appear in the kwrite window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 --- Comment #11 from Leonard Lausen <leon...@lausen.nl> --- I attached the outputs of running startplasmacompositor and kwinwayland --xwayland --exit-with-session=kwrite with WAYLAND_DEBUG. Please let me know if you had something different in mind. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 --- Comment #10 from Leonard Lausen <leon...@lausen.nl> --- Created attachment 106692 --> https://bugs.kde.org/attachment.cgi?id=106692=edit Output of kwin_wayland --xwayland --exit-with-session=kwrite with WAYLAND_DEBUG -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 --- Comment #9 from Leonard Lausen <leon...@lausen.nl> --- Created attachment 106691 --> https://bugs.kde.org/attachment.cgi?id=106691=edit Output of startplasmacompositor with WAYLAND_DEBUG when NOT pressing keys -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 --- Comment #8 from Leonard Lausen <leon...@lausen.nl> --- Created attachment 106690 --> https://bugs.kde.org/attachment.cgi?id=106690=edit Output of startplasmacompositor with WAYLAND_DEBUG when pressing keys -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 --- Comment #6 from Leonard Lausen <leon...@lausen.nl> --- The xcb useflag is enabled globally on my system (i.e. it is present in the output of emerge --info). So as far as I see qtgui is built with xkbcommon support. USE="X a52 aac acl acpi alsa amd64 berkdb bluetooth branding bzip2 cairo cdda cdr cjk cli cracklib crypt cups cxx dbus declarative dri dts dvd dvdr egl emacs emboss encode exif fam firefox flac fontconfig fortran gdbm gif glamor gles gpm gtk iconv icu inotify ipv6 ja jemalloc jpeg kde kipi ko kwallet lcms ldap libnotify lm_sensors lzma mad mng modules mp3 mp4 mpeg multilib ncurses nls nptl ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds pulseaudio qml qt3support qt4 qt5 readline sdl seccomp semantic-desktop session sound spell sqlite ssl startup-notification svg systemd tcpd tiff touch touchscreen truetype udev udisks unicode upower usb vaapi vorbis vulkan wayland widgets wxwidgets x264 xattr xcb xcomposite xinerama xml xscreensaver xv xvid zeroconf zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 fma3 mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="synaptics evdev libinput" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6" POSTGRES_TARGETS="postgres9_5" PYTHON_SINGLE_TARGET="python3_4" PYTHON_TARGETS="python2_7 python3_4" RUBY_TARGETS="ruby23" USERLAND="GNU" VIDEO_CARDS="intel i965" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 --- Comment #3 from Leonard Lausen <leon...@lausen.nl> --- Sorry for not being clear about this. Any application is affected. (So perhaps the bug should be reported against kwin_wayland instead?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381755] Keyboard input not working on wayland (only shortcuts work)
https://bugs.kde.org/show_bug.cgi?id=381755 Leonard Lausen <leon...@lausen.nl> changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
