| Summary: | Connecting external monitor freezes Plasma | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | waldauf <wwwaldauf> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | nate, plasma-bugs |
| Priority: | NOR | ||
| Version: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
waldauf
2020-01-29 15:59:57 UTC
Upgrade qt5-base didn't help: qt5-base (5.14.0-3 -> 5.14.1-1) Is here anybody who can solve this problem? My next error which I captured during restart kdeplasma: Both point size and pixel size set. Using pixel size. trying to show an empty dialog QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_400(0x562e7b9ede60, parent=0x562e7b6bfbf0, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_400(0x562e804fd790), which must be a sibling QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_400(0x562e7bdbc090, parent=0x562e7ba28f20, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_400(0x562e805078a0), which must be a sibling QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_400(0x562e7c3e3230, parent=0x562e7bb65aa0, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_400(0x562e805112e0), which must be a sibling The X11 connection broke (error 1). Did the X11 server die? KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/run/user/1000/kdeinit5__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/bin/plasmashell directly QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 26 and type 'Read', disabling... KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasmashell path = /usr/bin pid = 196325 KCrash: Arguments: /usr/bin/plasmashell KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/lib/drkonqi directly Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Invalid MIT-MAGIC-COOKIE-1 keyqt.qpa.xcb: could not connect to display :0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Unable to start Dr. Konqi Re-raising signal for core dump handling. The problem still persists in new the KDE version: Operating System: Arch Linux KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.5.2-arch2-2 OS Type: 64-bit Hello, is there some progress? I can confirm this problem on two laptopts - Lenovo and Dell. Cannot reproduce the issue. I can connect an external screen and there's no freeze. I'm very confused by the original report. Report says plasmashell is frozen And that kwin is using max CPU The backtrace is of kwin crashing after being closed. That doesn't seem relevant (In reply to Nate Graham from comment #5) > Cannot reproduce the issue. I can connect an external screen and there's no > freeze. What I discovered this freezing occurs when you connect two external monitors. If is there something that I can do for you (some logs, methods, ...) say me. I'd like to help to resolve this issue. (In reply to David Edmundson from comment #6) > I'm very confused by the original report. > > Report says plasmashell is frozen > And that kwin is using max CPU > > The backtrace is of kwin crashing after being closed. That doesn't seem > relevant Yes, you're right. It's confusing. But I don't know what is the cause. After connecting external monitor(s) Plasma is frozen. And after some time (plus-minus) is Kwin consuming almost 100% of CPU. Sometimes is Plasma working but Kwin is consuming CPU. I don't know how to find out what is first. If you can help me I appreciate that. if plasmashell is frozen, lets get a backtrace of plasmashell in the frozen state. I need your help. I'm trying to backtrace plasmashell. There are all processes with plasmashell: UID PID PPID C STIME TTY TIME CMD root 1348 868 0 17:09 ? 00:00:00 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth2ffded24-6e47-4f4c-a2cd-b76662a96337 --id 1 --start /usr/bin/startplasma-x11 --user waldauf waldauf 1371 1348 0 17:09 ? 00:00:00 /usr/bin/startplasma-x11 waldauf 1437 1371 0 17:09 ? 00:00:00 /usr/bin/plasma_session waldauf 1490 1 5 17:09 ? 00:00:08 /usr/bin/plasmashell When I run gdb I see this: $ gdb --pid `pidof plasmashell` 2>&1 | tee kwin.gdb GNU gdb (GDB) 9.1 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Attaching to process 1490 ptrace: Operation not permitted. (gdb) continue The program is not being run. (gdb) The program is not being run. (gdb) What I'm doing wrong? > ptrace: Operation not permitted.
Please ask for help in a forum of your distribution how to generate a backtrace for this case. gdb should be able to attach to a running process, unless the process has already exited.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! In this time - due coronavirus - I'm working from my home and the problems described here I had at work. As soon as will be possible I'll retest the whole issue. If the problems will persistent I send debug information. Thanks for the update. Please set the status to REOPEN if you add new information. |