| Summary: | Crash in KWin::SurfaceInterface::firstTransaction with xpra | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | RW <kde> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | kde |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 6.2.5 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 6.3.0 | |
| Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/80663/events/50cc0c41feb5462aa9020ea070a21590/ | ||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
RW
2024-10-18 08:50:00 UTC
Created attachment 174978 [details]
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
Crash just happened 10-15 minutes later again. I have the feeling that this related to the Xpra (https://xpra.org) update. Xpra is very handy when working with multiple computers but only one screen. E.g. I'm starting Firefox on a remote machine via SSH + Xpra and the Firefox window appears as I'd have started Firefox locally. I upgraded from version 4.4.5. to 6.2.0 this morning. Xpra is always a bit special but I've never seen that it crashes that hard. Normally it just doesn't work e.g. if Xpra version doesn't match on local and remote host or if some video codes are not there. But that's it. Looks like downgrading Xpra from 6.2.0 to 4.4.5 "solved" the issue. Haven't had the crash anymore so far. But without a fix I'm not really able to update Xpra anymore. Can you elaborate on how to use xpra to reproduce this Thanks for getting back on this! Well it's actually pretty easy. I've a workstation and a laptop. Both run latest Archlinux, KDE and xpra. So they are installed basically the same way. Xpra allows me to get the windows of various programs displayed on my workstation and it looks like they run locally. The connection is over SSH. E.g. for Firefox I run this command: xpra start ssh:laptop --keyboard-layout=de --pulseaudio=no --speaker=disabled --microphone=disabled --exit-with-client=yes --daemon=no --printing=no --exit-with-children --clipboard=yes --clipboard-direction=both --start-child=/usr/bin/firefox' That's basically all I do to get the remote window displayed. But the crash doesn't happen immediately. Sometimes it takes 30 minutes, sometimes only one or two minutes. But I haven't found a pattern yet when it happens. I also do nothing special with the remote Firefox (not watching videos e.g.). It's really just "normal" webpages. Hope this helps a bit. With xpra 4.4.5 it works like a charm. I'm using it all day long. But after upgrading to 6.2.0 I got this crashes. That's why I needed to downgrade to 4.4.5 again. Today I had another crash. I submitted a new crash report. I just don't know where it ended up in the bug tracking system. But it was transmitted successfully and I put a link to this bug ID in the crash comment. I need to use xpra 6.2.1 now instead of 4.4.5 (which was stable) because of updated dependencies in Archlinux (mainly Python 3.13 which xpra 4.4.5 doesn't like anymore...) . Meanwhile I'm using KDE 6.2.5 and kernel 6.12.8 (but I guess the kernel doesn't matter). I updated the "version" in the bug details accordingly. This time the crash only happened after two days of usage. So it looked like that the crash wouldn't show up anymore but I was wrong. But I guess that was only by accident that it took that long to get the crash. I don't really know what causes the crash. I was just using the remote Firefox (via xpra) as usual until the crash happened. I've three KDE activities and after the crash all remaining windows were moved to the "default" activity. The other two KDE activities didn't contain any windows anymore. I did a full Archlinux update now and restarted my computer. So I've the very latest packages installed. The last six days it worked fine and stable. So I'll close this. I'm not sure if it's resolved or if happens again. But then I'll open a new crash report. Sadly I've to re-open the bug. Crash happened again today. I just don't know where it ended. Is there a possibility to figure out which bug ID such a crash report gets? I just updated my Archlinx to the very latest packages yesterday. While the crash happened I was using xpra (https://xpra.org - screen for X11/Wayland) to work on a remote machine forwarding the display of a remote Firefox to my local machine (basically the same as doing I already described in the initial bug description and the ones that followed). I was using the remote Firefox to log into Google Cloud console. The crash happened while I was pressing a submit button to send the 2FA code during the login process. My local Firefox instances crashed too. Also Slack, Thunderbird and a few other apps died without any messages or so. Only every local Firefox process (three separate Firefox instances at that time) opened a window to create a crash report. All remaining windows were moved to "Default" activity. I have three activities altogether as mentioned in an earlier comment already. The only app that "survived" was "konsole" (again). Besides that all "konsole" windows were moved to "Default" activity and centered on the middle top of that activity, "konsole" was still working. That's basically everything I can say. This is the last message I got from the remote xpra session: "Gdk-Message: 07:29:17.397: Error flushing display: Connection reset by peer" But I guess that's not really related to the crash itself. Maybe one additional information that just came into my mind: I'm using remote apps with xpra from my local machine to two remote machines: local (Archlinux) -> remote (Archlinux) local (Archlinux) -> remote (Ubuntu 24.04) While both Archlinux machines are "full" desktops (both have KDE installed), the Ubuntu one is more or less just a server where I installed Firefox without a full desktop environment (just the dependencies that Firefox pulls in when you install the package). This kind of crash never happened to me when I was using the remote Firefox on the Ubuntu host from my local machine. |