|
Bugzilla – Full Text Bug Listing |
| Summary: | kded5 or kwin_wayland_wrapper crash during start | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Jiri Slaby <jslaby> |
| Component: | KDE Workspace (Plasma) | Assignee: | E-Mail List <opensuse-kde-bugs> |
| Status: | NEW --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | fvogt, jengelh, peter |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jiri Slaby
2023-07-24 07:32:17 UTC
(In reply to Jiri Slaby from comment #0) > started from sddm 0.20 (wayland-configured too) $ cat /etc/sddm.conf.d/wayland [General] DisplayServer=wayland [Users] MinimumUid=500 [Autologin] Session=plasmawayland User=xslaby Relogin=true > 54 wl_list_remove(struct wl_list *elm) > 55 { > 56 elm->prev->next = elm->next; > 57 elm->next->prev = elm->prev; ... > So elm->next is corrupted, apparently. Cc Jan as wayland maintainer. It looks like the crash is during shutdown, but it should not shut down at all. "Could not create wayland socket" is probably the cause, but that's a weird issue, there's not much that could go wrong there. Possibly XDG_RUNTIME_DIR isn't set or the directory not created (properly), but that should be taken care of by pam_systemd. >#3 <signal handler called>
>#4 wl_list_remove
>#5 wl_event_queue_release
>#6 wl_display_disconnect
>#7/8 QtWaylandClient::QWaylandDisplay::~QWaylandDisplay()
>#9 QtWaylandClient::QWaylandIntegration::~QWaylandIntegration()
>#10 QGuiApplicationPrivate::~QGuiApplicationPrivate()
>#11 QApplicationPrivate::~QApplicationPrivate()
>#12 main(int, char**)
mh, initial hypothesis goes for a double-free/use-after-free.
(In reply to Jan Engelhardt from comment #3) > mh, initial hypothesis goes for a double-free/use-after-free. How can I run kded5 under valgrind? Will something like this: cat > /etc/sddm.conf.d/valgrind <<EOF [Wayland] CompositorCommand=valgrind kwin_wayland --no-global-shortcuts --no-lockscreen --locale1 EOF work? (In reply to Jiri Slaby from comment #4) > (In reply to Jan Engelhardt from comment #3) > > mh, initial hypothesis goes for a double-free/use-after-free. > > How can I run kded5 under valgrind? > > Will something like this: > cat > /etc/sddm.conf.d/valgrind <<EOF > [Wayland] > CompositorCommand=valgrind kwin_wayland --no-global-shortcuts > --no-lockscreen --locale1 > EOF > > work? kded5 is probably started through dbus activation, so you'd have to edit either the dbus service file or the referenced systemd user service. (In reply to Jiri Slaby from comment #4) > (In reply to Jan Engelhardt from comment #3) > > mh, initial hypothesis goes for a double-free/use-after-free. > > How can I run kded5 under valgrind? No reports. But also the crashes of kded are gone. Maybe I couldn't reproduce ATM or perhaps this was fixed. (In reply to Fabian Vogt from comment #2) > It looks like the crash is during shutdown, but it should not shut down at > all. > > "Could not create wayland socket" is probably the cause, This remains and happened twice now: Wed 2023-08-02 08:20:42 CEST 6716 500 500 SIGABRT present /usr/bin/kwin_wayland_wrapper 386.9K Wed 2023-08-02 08:22:35 CEST 8258 500 500 SIGABRT present /usr/bin/kwin_wayland_wrapper 386.4K |