|
Bugzilla – Full Text Bug Listing |
| Summary: | xwayland crashing for more than 2 months now | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Miguel Rozsas <miguel> |
| Component: | KDE Workspace (Plasma) | Assignee: | E-Mail List <opensuse-kde-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | sndirsch |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | A complete log from journal | ||
|
Description
Miguel Rozsas
2023-10-15 13:33:18 UTC
Created attachment 870370 [details]
A complete log from journal
A complete log from journal when the bug happens.
The bug remains on openSUSE Tumbleweed 20231019. Hmm. kwin is running on Xwayland? This sounds weird. I would habe expected there is a KDE desktop available for Wayland. (In reply to Stefan Dirsch from comment #3) > Hmm. kwin is running on Xwayland? This sounds weird. I would habe expected > there is a KDE desktop available for Wayland. Let's check this first. running google-chrome on a terminal to collect the error messages it issues the following messages when an error occur abd the program crash (both xwayland and google-chrome): The X11 connection broke: I/O error (code 1) X connection to :1 broken (explicit kill or server shutdown). [3364:3364:1023/144052.095249:ERROR:connection.cc(46)] X connection error received. [3364:3480:1023/144052.095249:ERROR:connection.cc(46)] X connection error received. Just want to add that I've installed gnome-wayland-desktop and in 2 days I didn't experienced any crashes or any other problem, using the same google-chrome and Bravo browser I use under KDE/Wayland. So , I think I can say it is a problem in KDE/Wayland only. Not under KDE/X11 neither Gnome/wayland. Currently running Tumbleweed 20231020 . (In reply to Miguel Rozsas from comment #6) > So , I think I can say it is a problem in KDE/Wayland only. Not under > KDE/X11 neither Gnome/wayland. Sure on KDE/X11 there is no need for Xwayland. ;-) Updated to openSUSE Tumbleweed 20231025, xwayland-23.2.2-1.1.x86_64 and google-chrome-stable-118.0.5993.117-1.x86_64 and no issues any more since then (3 days ago). I don't know which package had the fix, I suspect it was xwayland but I could not be sure. |