Bug 465104 - Intermittent crash of Panel when hovering mouse over program icon - wl_display@1: error 1: invalid arguments for xdg_surface@586.get_toplevel
Summary: Intermittent crash of Panel when hovering mouse over program icon - wl_displa...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.26.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2023-02-01 07:13 UTC by Daniel Ayers
Modified: 2023-09-18 20:29 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Ayers 2023-02-01 07:13:27 UTC
SUMMARY

KDE Plasma 5.26.5 using Wayland on Fedora 37 (KDE Plasma Spin) with kernel 6.1.7-200.fc37.x86_64. AMD Ryzen 9 5950X, AMD Radeon RX 6750 XT, 128Gb RAM. 3 x DP monitors, 1 x HDMI monitor.

Intermittent crash (plasmashell crash causing plasma-plasmashell.service to bounce) when hovering mouse over panel at bottom of screen (with intention of clicking on program icon on panel to open window of running program, but panel crashes before click).

Unfortunately no debug build installed and backtrace not available via coredumpctl.

However, relevant log messages appear to be:

Feb 01 19:29:41 fedora37 kwin_wayland_wrapper[7938]: not a valid new object id (665), message get_toplevel(n)
Feb 01 19:29:41 fedora37 kwin_wayland_wrapper[7938]: error in client communication (pid 493616)
Feb 01 19:29:41 fedora37 plasmashell[493616]: wl_display@1: error 1: invalid arguments for xdg_surface@586.get_toplevel
Feb 01 19:29:41 fedora37 plasmashell[493616]: The Wayland connection experienced a fatal error: Invalid argument

See below for additional context before/after these messages.


STEPS TO REPRODUCE
1. Run plasmasell.
2. Open several different programs (I had 12 running at the time, multiple instances of some)
3. Hover mouse pointer over program icon on panel (left side, not the tray icons at right) as if you are about to click one
4. Might crash, might not. :)

OBSERVED RESULT

Feb 01 19:29:41 fedora37 plasmashell[493616]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x557dedcf3780)
Feb 01 19:29:41 fedora37 plasmashell[493616]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x557dedcf3780)
Feb 01 19:29:41 fedora37 plasmashell[493616]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x557dedcf3780)
Feb 01 19:29:41 fedora37 plasmashell[493616]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x557dedcf3780)
Feb 01 19:29:41 fedora37 kwin_wayland_wrapper[7938]: not a valid new object id (665), message get_toplevel(n)
Feb 01 19:29:41 fedora37 kwin_wayland_wrapper[7938]: error in client communication (pid 493616)
Feb 01 19:29:41 fedora37 plasmashell[493616]: wl_display@1: error 1: invalid arguments for xdg_surface@586.get_toplevel
Feb 01 19:29:41 fedora37 plasmashell[493616]: The Wayland connection experienced a fatal error: Invalid argument
Feb 01 19:29:41 fedora37 systemd[7856]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE
Feb 01 19:29:41 fedora37 systemd[7856]: plasma-plasmashell.service: Failed with result 'exit-code'.
Feb 01 19:29:41 fedora37 systemd[7856]: plasma-plasmashell.service: Consumed 11min 43.221s CPU time.
Feb 01 19:29:41 fedora37 systemd[7856]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 2.
Feb 01 19:29:41 fedora37 systemd[7856]: Stopped plasma-plasmashell.service - KDE Plasma Workspace.
Feb 01 19:29:41 fedora37 systemd[7856]: plasma-plasmashell.service: Consumed 11min 43.221s CPU time.
Feb 01 19:29:41 fedora37 systemd[7856]: Starting plasma-plasmashell.service - KDE Plasma Workspace...
Feb 01 19:29:42 fedora37 systemd[7856]: Started plasma-plasmashell.service - KDE Plasma Workspace.
Feb 01 19:29:42 fedora37 plasmashell[4124751]: kf.plasma.quick: Applet preload policy set to 1

EXPECTED RESULT

No crash, able to hover over and click on any program icon to maximise program.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 37 (KDE Plasma Spin)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Graphics Platform: Wayland
Comment 1 Daniel Ayers 2023-02-01 07:17:54 UTC
Appears similar to https://bugs.kde.org/show_bug.cgi?id=357895

This bug could easily be triggered by a failed attempt to display a pop-up window for a program group on the panel.
Comment 2 Justin Zobel 2023-02-02 01:22:45 UTC
If you can please when experiencing the crash acquire a backtrace so the developers can see where the issue is within the code. For more information on obtaining a backtrace see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 3 Daniel Ayers 2023-02-03 23:20:14 UTC
I am aware of how to obtain a backtrace, however there is no sign of a coredump being created.  I have installed debuginfo files for many KDE-related packages (including plasma-desktop, which installs the plasmashell binary).  I have checked the system configuration to ensure that coredumps are saved.  Yet, this event (which has occurred twice today) does not generate a coredump.

Note the sequence of log messages I posted with the original ticket included this line:

Feb 01 19:29:41 fedora37 systemd[7856]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE

The "plasma-plasmashell.service" is a user unit with the following definition:

# /usr/lib/systemd/user/plasma-plasmashell.service
[Unit]
Description=KDE Plasma Workspace
After=plasma-ksmserver.service plasma-kcminit.service
PartOf=graphical-session.target

[Service]
ExecStart=/usr/bin/plasmashell --no-respawn
Restart=on-failure
Type=dbus
BusName=org.kde.plasmashell
Slice=session.slice
TimeoutSec=40sec

[Install]
WantedBy=plasma-core.target

Therefore the plasmashell binary terminated successfully with an exit code of 1. AFAIK when a process is terminated by a signal the return code will be >128.  This would appear to eliminate the possibility that the process dumped core as a result of a signal, rather it suggests to me a "controlled" failure due to an error condition that was caught.  Therefore I would expect that logging would be the only source of debugging information.

If my understanding is wrong, I am happy to be corrected and do what I can to gather the required information.

I have experienced the problem twice today (after the above changes to catch any coredump that was generated, none was).

On both occasions today I was moving the mouse towards the "Konsole terminal" icon in the panel (not the leftmost Konsole icon that is always there, the second one further right that appears when at least one instance of the program is running).  On the first occasion, one instance of Konsole was running.  The crash occurred after my cursor was over the icon and before the window that would show a thumbnail of the running process appeared.

On the second occasion, no instances of Konsole were running.  I moved the mouse pointer over the Konsole icon (immediately net to the Fedora icon at the extreme left of the panel).  Plasmashell crashed (exited) before the tooltip appeared above the icon that would say "Konsole Terminal".
Comment 4 David Edmundson 2023-02-03 23:37:54 UTC
You're not getting a backtrace because it's not crashing, it's exiting on being told it has an error.
Comment 5 Daniel Ayers 2023-02-03 23:46:24 UTC
That is what I just said.
Comment 6 Jin Liu 2023-02-14 01:32:12 UTC
Same problem for me. In my case there's no "not a valid new object id" log, only these logs before crash:

 792   │ 2月 14 09:22:03 laptop-jin-mi kwin_wayland_wrapper[1060]: error in client communication (pid 372594)
 793   │ 2月 14 09:22:03 laptop-jin-mi plasmashell[372594]: wl_display@1: error 0: invalid object 258
 794   │ 2月 14 09:22:03 laptop-jin-mi plasmashell[372594]: The Wayland connection experienced a fatal error: Invalid argument

And no coredump.
Comment 7 Nate Graham 2023-09-18 20:29:11 UTC
This is fixed now in Plasma 6.