| Summary: | wayland: kinfocenter still crashing when clicking on Graphical Information | ||
|---|---|---|---|
| Product: | [Applications] kinfocenter | Reporter: | Henning <wuelpi> |
| Component: | Info | Assignee: | Martin Flöser <mgraesslin> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | amirseni, andrius, boyko_kanev, bugseforuns, fabian, hmpl, mail, strelok5771, wuelpi |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| URL: | https://phabricator.kde.org/D10391 | ||
| Latest Commit: | https://commits.kde.org/kinfocenter/a7e887975d0181d9039e3d727b0f8172b0bfc2e3 | Version Fixed In: | 5.12.1 |
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Henning
2017-11-30 19:54:26 UTC
Created attachment 109342 [details]
New crash information added by DrKonqi
kinfocenter (5.11.4) using Qt 5.9.3
- What I was doing when the application crashed:
Clicking on the OpenGL tab, neither the update to Qt5.9.3 nor to Info Centre 5.11.4 helped.
- Custom settings of the application:
Happens on dual monitor setups and on single monitor setups, crashlogs are of the former case.
If you need any additional information or help reproducing I am happy to help, the silence is worring me though. Is this a Tumbleweed problem?
-- Backtrace (Reduced):
#6 0x00007f281df7bd39 in wl_map_insert_at (map=<optimized out>, flags=<optimized out>, i=<optimized out>, data=<optimized out>) at src/wayland-util.c:249
#7 0x00007f281df77e4e in proxy_destroy (proxy=0x55f8b0536ed0) at src/wayland-client.c:411
#8 wl_proxy_destroy (proxy=0x55f8b0536ed0) at src/wayland-client.c:442
#9 0x00007f281c223e85 in wl_registry_destroy (wl_registry=<optimized out>) at /usr/include/wayland/wayland-client-protocol.h:1065
#10 KWayland::Client::WaylandPointer<wl_registry, wl_registry_destroy>::release (this=0x55f8b0578600, this=0x55f8b0578600) at /usr/src/debug/kwayland-5.40.0/src/client/wayland_pointer_p.h:53
Created attachment 109425 [details]
New crash information added by DrKonqi
kinfocenter (5.11.4) using Qt 5.10.0
- What I was doing when the application crashed:
- Custom settings of the application:
Running on archlinux synced and updated on intel hardware.
-- Backtrace (Reduced):
#6 0x00007f34cc98d7e7 in wl_proxy_destroy () from /usr/lib/libwayland-client.so.0
#7 0x00007f34cb0fa606 in KWayland::Client::Registry::release() () from /usr/lib/libKF5WaylandClient.so.5
#8 0x00007f34cb0fa62f in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5
#9 0x00007f34cb0fa71a in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5
#10 0x00007f34da0a254d in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5
Created attachment 109934 [details]
New crash information added by DrKonqi
kinfocenter (5.12.80) using Qt 5.10.0
- What I was doing when the application crashed:
I can confirm this reliably.
The crash happens here only when switching to any Info Center module _after_ the "Graphical Information" > "Wayland" module.
-- Backtrace (Reduced):
#6 0x00007f742a3d1bc9 in wl_map_insert_at (map=<optimized out>, flags=flags@entry=0, i=<optimized out>, data=<optimized out>) at /var/tmp/portage/dev-libs/wayland-1.13.0/work/wayland-1.13.0/src/wayland-util.c:249
#7 0x00007f742a3cdebe in proxy_destroy (proxy=0x55e64b5c4db0) at /var/tmp/portage/dev-libs/wayland-1.13.0/work/wayland-1.13.0/src/wayland-client.c:411
#8 wl_proxy_destroy (proxy=0x55e64b5c4db0) at /var/tmp/portage/dev-libs/wayland-1.13.0/work/wayland-1.13.0/src/wayland-client.c:442
#9 0x00007f7428f1c645 in wl_registry_destroy (wl_registry=<optimized out>) at /usr/include/wayland-client-protocol.h:1065
#10 KWayland::Client::WaylandPointer<wl_registry, wl_registry_destroy>::release (this=0x55e64b533e70, this=0x55e64b533e70) at /var/tmp/portage/kde-frameworks/kwayland-9999/work/kwayland-9999/src/client/wayland_pointer_p.h:53
I can confirm this issue on openSUSE Tumbleweed with Qt 5.10.0 and kwayland from git master (07935f7). Assigning to the creator of the wayland info module in kinfocenter. *** Bug 389199 has been marked as a duplicate of this bug. *** Created attachment 110205 [details]
New crash information added by DrKonqi
kinfocenter (5.11.95) using Qt 5.10.0
- What I was doing when the application crashed:
Just tried open graphic information in wayland-mode
-- Backtrace (Reduced):
#6 0x00007f4f17ad99c9 in wl_map_insert_at () from /lib64/libwayland-client.so.0
#7 0x00007f4f17ad5ade in wl_proxy_destroy () from /lib64/libwayland-client.so.0
#8 0x00007f4f15e9db45 in KWayland::Client::Registry::release() () from /lib64/libKF5WaylandClient.so.5
#9 0x00007f4f15e9db6c in KWayland::Client::Registry::~Registry() () from /lib64/libKF5WaylandClient.so.5
#10 0x00007f4f15e9dbf9 in KWayland::Client::Registry::~Registry() () from /lib64/libKF5WaylandClient.so.5
Created attachment 110379 [details]
New crash information added by DrKonqi
kinfocenter (5.12.0) using Qt 5.9.3
- What I was doing when the application crashed:
I clicked on Graphical Information>Wayland (no problem so far) Whatever I click after that (OpenGL, X-Server, Memory, About System etc.) The Info Center Crashes
-- Backtrace (Reduced):
#6 0x00007f2a6ad0c5b9 in wl_map_insert_at (map=<optimized out>, flags=flags@entry=0, i=<optimized out>, data=<optimized out>) at ../src/wayland-util.c:249
#7 0x00007f2a6ad087be in proxy_destroy (proxy=0x238b230) at ../src/wayland-client.c:411
#8 wl_proxy_destroy (proxy=0x238b230) at ../src/wayland-client.c:442
#9 0x00007f2a691ec555 in wl_registry_destroy (wl_registry=<optimized out>) at /usr/include/wayland-client-protocol.h:1065
#10 KWayland::Client::WaylandPointer<wl_registry, wl_registry_destroy>::release (this=0x1d25b70, this=0x1d25b70) at /workspace/build/src/client/wayland_pointer_p.h:53
patch at: https://phabricator.kde.org/D10391 The regression was caused by a change in libWayland. We had similar crashes unfortunately in other areas as well. Git commit a7e887975d0181d9039e3d727b0f8172b0bfc2e3 by Martin Flöser. Committed on 08/02/2018 at 17:59. Pushed by graesslin into branch 'Plasma/5.12'. Ensure Registry gets destroyed before the Wayland connection Summary: Registry was parented to WaylandModule, but the ConnectionThread got destroyed in the dtor, thus before the Registry resulting in a crash when the Registry got destroyed. This change addresses this problem by tracking the Registry and destroying it before destroying the Connection. FIXED-IN: 5.12.1 Test Plan: Clicked Wayland section, then quit application, verified exit code Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D10391 M +3 -1 Modules/base/info_wayland.cpp M +2 -0 Modules/base/info_wayland.h https://commits.kde.org/kinfocenter/a7e887975d0181d9039e3d727b0f8172b0bfc2e3 |