Bug 2172601 - xdg-desktop-portal-kde crash when using sddm-wayland-plasma on F37
Summary: xdg-desktop-portal-kde crash when using sddm-wayland-plasma on F37
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-22 16:31 UTC by Geraldo Simião
Modified: 2023-03-24 02:12 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-03-24 02:12:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Coredump xdg-desktop-portal-kde crash (56.19 KB, text/plain)
2023-02-22 16:31 UTC, Geraldo Simião
no flags Details
journalctl from login moment (75.92 KB, text/plain)
2023-02-22 16:40 UTC, Geraldo Simião
no flags Details
plasma desktop conf file (3.45 KB, text/plain)
2023-02-22 16:46 UTC, Geraldo Simião
no flags Details
x11 destop conf (3.09 KB, text/plain)
2023-02-22 16:47 UTC, Geraldo Simião
no flags Details
screencast from a F37 VM having the same behavior (6.31 MB, video/webm)
2023-02-22 17:49 UTC, Geraldo Simião
no flags Details

Description Geraldo Simião 2023-02-22 16:31:22 UTC
Created attachment 1945755 [details]
Coredump xdg-desktop-portal-kde crash

Description of problem:
When using sddm-wayland-plasma on an upgraded f36=>f37 kde spin installation, the login screen freezes, the line with the options below the password field dissapears (suspend, reboot, shutdown, other...) and after some time (about 30s) I can type the passowrd and login. 
Coredumpctl return a xdg-desktop-portal-kde crash.
I'm on a laptop with a second monitor on HDMI output, the login screen appears only on this second monitor, not on the build-in primary monitor (as is used to be on the sddm-x11 login)


Version-Release number of selected component (if applicable):

Operating System: Fedora Linux 37

KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

Kernel Version: 6.1.12-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000

plasma-lookandfeel-fedora-5.27.0-4.fc37.noarch.rpm
plasma-workspace-doc-5.27.0-4.fc37.noarch.rpm
sddm-breeze-5.27.0-4.fc37.noarch.rpm
sddm-wayland-plasma-5.27.0-4.fc37.noarch.rpm
sddm-0.19.0^git20230201.3ee57e9-2.fc37.x86_64
sddm-kcm-5.27.0-1.fc37.x86_64



How reproducible:
Allways


Steps to Reproduce:
1. Upgrade F36 KDE to F37 KDE
2. sudo dnf swap sddm-x11 sddm-wayland-plasma
3. Reboot

Actual results:
Login screen freezes for a while, some options dissapear, passowrd field start working. After login, one xdg-desktop-portal-kde crash.
Two screen setup, login shows only at the second monitor, not on the primary built-in laptop monitor.

Expected results:
Login acting as usual, no freezes or coredumps, all options working normal at the login screen, login enabled at primary monitor.


Additional info (full log attached too):

logs at journalctl shows:
sddm-greeter[1133]: Malformed entry in "/usr/share/wayland-sessions/plasma.desktop" : ""
sddm-greeter[1133]: Malformed entry in "/usr/share/xsessions/plasmax11.desktop" : ""


and:
sddm-greeter[1133]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
pipewire[1195]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
pipewire[1195]: mod.rt: found session bus but no portal
wireplumber[1198]: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
wireplumber[1198]: found session bus but no portal
pipewire-pulse[1199]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
pipewire-pulse[1199]: mod.rt: found session bus but no portal

Comment 1 Geraldo Simião 2023-02-22 16:40:20 UTC
Created attachment 1945757 [details]
journalctl from login moment

Comment 2 Geraldo Simião 2023-02-22 16:46:02 UTC
Created attachment 1945758 [details]
plasma desktop conf file

Comment 3 Geraldo Simião 2023-02-22 16:47:23 UTC
Created attachment 1945759 [details]
x11 destop conf

Comment 4 Geraldo Simião 2023-02-22 17:49:49 UTC
Created attachment 1945775 [details]
screencast from a F37 VM having the same behavior

Comment 5 Nate Graham 2023-03-08 04:49:40 UTC
Can reproduce this issue. The backtrace of these crashes is not super duper helpful:

#0  0x00007f83c2cafe5c in __pthread_kill_implementation () from /lib64/libc.so.6
#1  0x00007f83c2c5fa76 in raise () from /lib64/libc.so.6
#2  0x00007f83c2c497fc in abort () from /lib64/libc.so.6
#3  0x00007f83c32b14e5 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5
#4  0x00007f83c396330b in QGuiApplicationPrivate::createPlatformIntegration() () from /lib64/libQt5Gui.so.5
#5  0x00007f83c39637b8 in QGuiApplicationPrivate::createEventDispatcher() () from /lib64/libQt5Gui.so.5
#6  0x00007f83c34a3dd1 in QCoreApplicationPrivate::init() () from /lib64/libQt5Core.so.5
#7  0x00007f83c3965b73 in QGuiApplicationPrivate::init() () from /lib64/libQt5Gui.so.5
#8  0x00007f83c4db437d in QApplicationPrivate::init() () from /lib64/libQt5Widgets.so.5
#9  0x00005597088b3a61 in main ()


...But it does have a nugget of potentially useful information: QGuiApplicationPrivate::createPlatformIntegration() being in there looks a bit suspicious. Maybe it's trying to start the KDE portal process before plasma-integration is available or something?

Comment 6 Geraldo Simião 2023-03-21 12:06:01 UTC
This was fixed on F38 with this update => https://bodhi.fedoraproject.org/updates/FEDORA-2023-dad8b1e03f, can whe have it backported to F37 too?

Comment 7 Geraldo Simião 2023-03-21 15:45:50 UTC
tested the new sddm build, but it didn't fixed the crash
https://bodhi.fedoraproject.org/updates/FEDORA-2023-59657907de

Comment 8 Geraldo Simião 2023-03-23 13:21:41 UTC
Now with the new build version sddm-0.19.0^git20230320.e07e805-2.fc37 at the update https://bodhi.fedoraproject.org/updates/FEDORA-2023-59657907de crash is finaly fixed. 
Thanks for all of you that helped with this.

Comment 9 Geraldo Simião 2023-03-24 02:12:02 UTC
I'm closing this now, as this ticket wasn't tied to the update at bodhi.
Bug is fixed.


Note You need to log in before you can comment on or make changes to this bug.