Application: kaccess () (Compiled from sources) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: When starting an empty KDE Wayland session, the kaccess program crashes. The crash can be reproduced every time. -- Backtrace: Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7c0af67ec0 (LWP 1727))] Thread 2 (Thread 0x7f7bf7d79700 (LWP 1728)): #0 0x00007f7c0a8cf68d in poll () from /lib64/libc.so.6 #1 0x00007f7c00194876 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f7c0019498c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f7c06f961bb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #4 0x00007f7c06f3f4da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007f7c06d6cb83 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x00007f7c03a85c49 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x00007f7c06d71986 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x00007f7c01c62454 in start_thread () from /lib64/libpthread.so.0 #9 0x00007f7c0a8d839f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f7c0af67ec0 (LWP 1727)): [KCrash Handler] #6 0x00007f7bf69ddf49 in wl_map_insert_at () from /usr/lib64/libwayland-client.so.0 #7 0x00007f7bf69da16e in wl_proxy_destroy () from /usr/lib64/libwayland-client.so.0 #8 0x00007f7bf5f44c75 in KWayland::Client::Registry::release() () from /usr/lib64/libKF5WaylandClient.so.5 #9 0x00007f7bf5f44c9c in KWayland::Client::Registry::~Registry() () from /usr/lib64/libKF5WaylandClient.so.5 #10 0x00007f7bf5f44d39 in KWayland::Client::Registry::~Registry() () from /usr/lib64/libKF5WaylandClient.so.5 #11 0x00007f7c06f6bd31 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #12 0x00007f7c06f750cf in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #13 0x00007f7bf4a227e3 in ?? () from /usr/lib64/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so #14 0x00007f7c0a825ea0 in __run_exit_handlers () from /lib64/libc.so.6 #15 0x00007f7c0a825efa in exit () from /lib64/libc.so.6 #16 0x00007f7c0a80f298 in __libc_start_main () from /lib64/libc.so.6 #17 0x00000000004006aa in _start () Reported using DrKonqi
Could you please provide a backtrace with debug symbols.
Created attachment 102872 [details] Error report with debug symbols
In the attachment you can find the report with debug symbols. I have exactly the same problem (also with tumbleweed). Hope this helps
The same happens to me: - Distribution: OpenSUSE Tumbleweed, up-to-date - Thinkpad T500 - Device: Mesa DRI Mobile Intel® GM45 Express Chipset (0x2a42) Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faed31cd4c0 (LWP 12702))] Thread 2 (Thread 0x7faebfdc8700 (LWP 12704)): #0 0x00007ffe27fb1b12 in clock_gettime () #1 0x00007faed2b4b216 in clock_gettime () from /lib64/libc.so.6 #2 0x00007faecf07e6e1 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x00007faecf1fa419 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #4 0x00007faecf1fa9c5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5 #5 0x00007faecf1fbd6e in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x00007faec83f9d79 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #7 0x00007faec83fa79b in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x00007faec83fa98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x00007faecf1fc79b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #10 0x00007faecf1a61ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #11 0x00007faecefd48b3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #12 0x00007faecbcf03e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #13 0x00007faecefd9558 in ?? () from /usr/lib64/libQt5Core.so.5 #14 0x00007faec9eca454 in start_thread () from /lib64/libpthread.so.0 #15 0x00007faed2b3e37f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7faed31cd4c0 (LWP 12702)): [KCrash Handler] #6 0x00007faebea2bf49 in wl_map_insert_at () from /usr/lib64/libwayland-client.so.0 #7 0x00007faebea2816e in wl_proxy_destroy () from /usr/lib64/libwayland-client.so.0 #8 0x00007faebdf91415 in wl_registry_destroy (wl_registry=<optimized out>) at /usr/include/wayland/wayland-client-protocol.h:1065 #9 KWayland::Client::WaylandPointer<wl_registry, wl_registry_destroy>::release (this=0x9a46c0, this=0x9a46c0) at /usr/src/debug/kwayland-5.29.0/src/client/wayland_pointer_p.h:53 #10 KWayland::Client::Registry::release (this=this@entry=0xa06b60) at /usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:358 #11 0x00007faebdf9143c in KWayland::Client::Registry::~Registry (this=0xa06b60, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:353 #12 0x00007faebdf914d9 in KWayland::Client::Registry::~Registry (this=0xa06b60, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:354 #13 0x00007faecf1d26d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #14 0x00007faecf1dba4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #15 0x00007faebca6b753 in WaylandIntegration::~WaylandIntegration (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.8.4/src/windowsystem/waylandintegration.cpp:51 #16 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.8.4/src/windowsystem/waylandintegration.cpp:37 #17 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.8.4/src/windowsystem/waylandintegration.cpp:43 #18 0x00007faed2a8bea0 in __run_exit_handlers () from /lib64/libc.so.6 #19 0x00007faed2a8befa in exit () from /lib64/libc.so.6 #20 0x00007faed2a75298 in __libc_start_main () from /lib64/libc.so.6 #21 0x000000000040068a in _start () at ../sysdeps/x86_64/start.S:120 Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faed31cd4c0 (LWP 12702))] Thread 2 (Thread 0x7faebfdc8700 (LWP 12704)): #0 0x00007ffe27fb1b12 in clock_gettime () #1 0x00007faed2b4b216 in clock_gettime () from /lib64/libc.so.6 #2 0x00007faecf07e6e1 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x00007faecf1fa419 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #4 0x00007faecf1fa9c5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5 #5 0x00007faecf1fbd6e in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x00007faec83f9d79 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #7 0x00007faec83fa79b in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x00007faec83fa98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x00007faecf1fc79b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #10 0x00007faecf1a61ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #11 0x00007faecefd48b3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #12 0x00007faecbcf03e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #13 0x00007faecefd9558 in ?? () from /usr/lib64/libQt5Core.so.5 #14 0x00007faec9eca454 in start_thread () from /lib64/libpthread.so.0 #15 0x00007faed2b3e37f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7faed31cd4c0 (LWP 12702)): [KCrash Handler] #6 0x00007faebea2bf49 in wl_map_insert_at () from /usr/lib64/libwayland-client.so.0 #7 0x00007faebea2816e in wl_proxy_destroy () from /usr/lib64/libwayland-client.so.0 #8 0x00007faebdf91415 in wl_registry_destroy (wl_registry=<optimized out>) at /usr/include/wayland/wayland-client-protocol.h:1065 #9 KWayland::Client::WaylandPointer<wl_registry, wl_registry_destroy>::release (this=0x9a46c0, this=0x9a46c0) at /usr/src/debug/kwayland-5.29.0/src/client/wayland_pointer_p.h:53 #10 KWayland::Client::Registry::release (this=this@entry=0xa06b60) at /usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:358 #11 0x00007faebdf9143c in KWayland::Client::Registry::~Registry (this=0xa06b60, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:353 #12 0x00007faebdf914d9 in KWayland::Client::Registry::~Registry (this=0xa06b60, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-5.29.0/src/client/registry.cpp:354 #13 0x00007faecf1d26d1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #14 0x00007faecf1dba4f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #15 0x00007faebca6b753 in WaylandIntegration::~WaylandIntegration (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.8.4/src/windowsystem/waylandintegration.cpp:51 #16 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.8.4/src/windowsystem/waylandintegration.cpp:37 #17 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.8.4/src/windowsystem/waylandintegration.cpp:43 #18 0x00007faed2a8bea0 in __run_exit_handlers () from /lib64/libc.so.6 #19 0x00007faed2a8befa in exit () from /lib64/libc.so.6 #20 0x00007faed2a75298 in __libc_start_main () from /lib64/libc.so.6 #21 0x000000000040068a in _start () at ../sysdeps/x86_64/start.S:120
Thanks for the update.
I also experienced this crash when trying plasma/wayland for the first time. I had a backtrace with debug symbols but DrKonqi judged the backtrace quality too low (1 star out of 3) to let me report it.
*** Bug 374198 has been marked as a duplicate of this bug. ***
I think this should become confirmed, happens to me on openSUSE Tumbleweed too, with 5.8.5 and with latest git packages (from openSUSE unstable KDE repos)
confirmed has no meaning on bugs.kde.org.
*** Bug 374836 has been marked as a duplicate of this bug. ***
*** Bug 374835 has been marked as a duplicate of this bug. ***
*** Bug 375030 has been marked as a duplicate of this bug. ***
same here on arch linux Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f99811d1840 (LWP 1980))] Thread 2 (Thread 0x7f996e3ad700 (LWP 1982)): #0 0x00007f9980c1248d in poll () from /usr/lib/libc.so.6 #1 0x00007f99761c4786 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007f99761c489c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007f997d2583eb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #4 0x00007f997d201c1a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #5 0x00007f997d0239f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x00007f9979cd00c5 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x00007f997d028658 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x00007f9977c88454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x00007f9980c1b7df in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f99811d1840 (LWP 1980)): [KCrash Handler] #6 0x00007f996d163138 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 0x00007f996d15efbe in proxy_destroy (proxy=0x25c5cf0) at src/wayland-client.c:411 #8 wl_proxy_destroy (proxy=0x25c5cf0) at src/wayland-client.c:442 #9 0x00007f996c2891e5 in KWayland::Client::Registry::release() () from /usr/lib/libKF5WaylandClient.so.5 #10 0x00007f996c28920e in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5 #11 0x00007f996c2892e9 in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5 #12 0x00007f997d22d791 in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #13 0x00007f997d2370ef in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #14 0x00007f99660fe393 in ?? () from /usr/lib/qt/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so #15 0x00007f9980b68990 in __run_exit_handlers () from /usr/lib/libc.so.6 #16 0x00007f9980b689ea in exit () from /usr/lib/libc.so.6 #17 0x00007f9980b53298 in __libc_start_main () from /usr/lib/libc.so.6 #18 0x000000000040066a in _start ()
Created attachment 103609 [details] New crash information added by DrKonqi kaccess () using Qt 5.7.1 Don't know if my machine set up has some issue also... wayland + hi-res display + opensuse tumbleweed + sddm. Gnome on wayland working with no issues -- Backtrace (Reduced): #6 0x00007f8a6144ef49 in wl_map_insert_at () from /usr/lib64/libwayland-client.so.0 #7 0x00007f8a6144b16e in wl_proxy_destroy () from /usr/lib64/libwayland-client.so.0 #8 0x00007f8a60577415 in KWayland::Client::Registry::release() () from /usr/lib64/libKF5WaylandClient.so.5 #9 0x00007f8a6057743c in KWayland::Client::Registry::~Registry() () from /usr/lib64/libKF5WaylandClient.so.5 #10 0x00007f8a605774d9 in KWayland::Client::Registry::~Registry() () from /usr/lib64/libKF5WaylandClient.so.5
Created attachment 104280 [details] New crash information added by DrKonqi kaccess () using Qt 5.8.0 - What I was doing when the application crashed: Start KDE Plasma Wayland - Unusual behavior I noticed: The application crashes immediatly after plasma starts - Custom settings of the application: No -- Backtrace (Reduced): #6 0x00007f7b29bc0d49 in wl_map_insert_at () from /usr/lib/libwayland-client.so.0 #7 0x00007f7b29bbcf1e in wl_proxy_destroy () from /usr/lib/libwayland-client.so.0 #8 0x00007f7b28ce7175 in KWayland::Client::Registry::release() () from /usr/lib/libKF5WaylandClient.so.5 #9 0x00007f7b28ce719e in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5 #10 0x00007f7b28ce7279 in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5
I am also experiencing these crashes. This bug was introduced with Wayland 1.13. Downgrading to 1.12 fixes the problem temporarily.
New backtrace with debug symbols Distribution: opensuse tumbleweed (march 4th 2017) KDE frameworks: 5.31.0 Qt: 5.7.1 wayland Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd89751540 (LWP 7352))] Thread 2 (Thread 0x7fcd76321700 (LWP 7353)): #0 0x00007fcd890d56dd in read () from /lib64/libc.so.6 #1 0x00007fcd7e9aeba0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fcd7e96a35e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fcd7e96a834 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x00007fcd7e96a9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x00007fcd857a018b in QEventDispatcherGlib::processEvents (this=0x7fcd700008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x00007fcd85749aea in QEventLoop::exec (this=this@entry=0x7fcd76320c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x00007fcd85577813 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:507 #8 0x00007fcd8228b385 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x00007fcd8557c4c8 in QThreadPrivate::start (arg=0x7fcd824fcd20) at thread/qthread_unix.cpp:368 #10 0x00007fcd80466454 in start_thread () from /lib64/libpthread.so.0 #11 0x00007fcd890e237f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fcd89751540 (LWP 7352)): [KCrash Handler] #6 0x00007fcd74f60029 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 0x00007fcd74f5c1fe in proxy_destroy (proxy=0xcb84b0) at src/wayland-client.c:411 #8 wl_proxy_destroy (proxy=0xcb84b0) at src/wayland-client.c:442 #9 0x00007fcd742a0415 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=0xcb4090, this=0xcb4090) at /usr/src/debug/kwayland-5.31.0/src/client/wayland_pointer_p.h:53 #11 KWayland::Client::Registry::release (this=this@entry=0xcb1420) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:358 #12 0x00007fcd742a043c in KWayland::Client::Registry::~Registry (this=0xcb1420, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:353 #13 0x00007fcd742a04d9 in KWayland::Client::Registry::~Registry (this=0xcb1420, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:354 #14 0x00007fcd85775f31 in QObjectPrivate::deleteChildren (this=this@entry=0xcbe210) at kernel/qobject.cpp:1970 #15 0x00007fcd8577f2bf in QObject::~QObject (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qobject.cpp:1041 #16 0x00007fcd6e1557e3 in WaylandIntegration::~WaylandIntegration (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:51 #17 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:37 #18 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:43 #19 0x00007fcd8902fea0 in __run_exit_handlers () from /lib64/libc.so.6 #20 0x00007fcd8902fefa in exit () from /lib64/libc.so.6 #21 0x00007fcd89019298 in __libc_start_main () from /lib64/libc.so.6 #22 0x000000000040068a in _start () at ../sysdeps/x86_64/start.S:120
*** Bug 377218 has been marked as a duplicate of this bug. ***
*** Bug 377962 has been marked as a duplicate of this bug. ***
This seems to be caused by global objects in KWayland integration, which get deleted by __run_exit_handlers, probably after the wayland connection has been shutdown.
This smells like the root cause is somewhere else. The code is supposed to cleanup, the Wayland objects are properly parented. It means that either the application or the framework is not cleaned up correctly.
Do those crashes happen on the developer machines? Can I do anything to help narrow down the cause? So far it seems like kaccess, kate and dolphin are affected by this bug, but not calligra*, kwrite, konsole and krusader.
(In reply to Kurt Seebauer from comment #22) > Do those crashes happen on the developer machines? We have had similar crashes before in other components. It started with a Wayland library update which my distribution has not yet shipped. That makes it more difficult ;-)
*** Bug 378362 has been marked as a duplicate of this bug. ***
*** Bug 379367 has been marked as a duplicate of this bug. ***
Fixed in Plasma 5.10 with 34fc30c4f7ca6d461ebfa0b7691e05edf2b0e40e
Edit. I'm a bit confused by this bug. /usr/bin/kaccess still crashes, it has ungaurded X calls. That doesn't match the backtrace here, which is a common theme that comes up in many places, which is what I've fixed.
(In reply to David Edmundson from comment #27) > Edit. I'm a bit confused by this bug. > > /usr/bin/kaccess still crashes, it has ungaurded X calls. > > That doesn't match the backtrace here, which is a common theme that comes up > in many places, which is what I've fixed. It's possible that the unguarded X calls were just hidden by the other problems.
*** Bug 379366 has been marked as a duplicate of this bug. ***
*** Bug 379728 has been marked as a duplicate of this bug. ***
This crash happens on Arch running plasma 5.10 beta under Wayland.
Created attachment 105650 [details] New crash information added by DrKonqi kaccess () using Qt 5.7.1 - What I was doing when the application crashed: KAccess with KDE Apps 17.04.1, Plasma 5.9.5, KF 5.34.0 crashed upon startup in Wayland session. -- Backtrace (Reduced): #6 0x00007f9e84bbcb21 in wl_map_insert_at () from /usr/lib64/libwayland-client.so.0 #7 0x00007f9e84bb8e6e in wl_proxy_destroy () from /usr/lib64/libwayland-client.so.0 #8 0x00007f9e840fa6a5 in KWayland::Client::Registry::release() () from /usr/lib64/libKF5WaylandClient.so.5 #9 0x00007f9e840fa6cc in KWayland::Client::Registry::~Registry() () from /usr/lib64/libKF5WaylandClient.so.5 #10 0x00007f9e840fa759 in KWayland::Client::Registry::~Registry() () from /usr/lib64/libKF5WaylandClient.so.5
Created attachment 105698 [details] another backtrace, waylandintegration.cpp Clearly same issue as this, but a little more backtrace info
*** Bug 380373 has been marked as a duplicate of this bug. ***
Seems to still happen in plasma 5.10, regardless of comment 26 The backtrace is the same, though I dont seem able to paste it into chrome from a wayland session. Using plasma5-desktop-5.10.0 from opensuse tumbleweed
I can confirm, this crash is still happening on Arch running plasma 5.10 stable.
Git commit c75338d4a57cdc382830fafd946d2ed887a08bab by David Edmundson. Committed on 05/06/2017 at 12:09. Pushed by davidedmundson into branch 'Plasma/5.10'. Force KAccess to run under XCB Summary: KAccess is responsible for: visual system bell stick keys/slow keys starting orca None of this will work in wayland as-is; and when they are done, will probably be in kwin anyway. But, we do still want this set up for xwayland applications. This sets the platform, so that we have xwayland apps still working the same. Making wayland apps work properly is a task for another day. Primarily this stops the thing crashing on startup. Reviewers: #plasma, mart Reviewed By: #plasma, mart Subscribers: mart, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D6035 M +4 -0 kaccess/main.cpp https://commits.kde.org/plasma-desktop/c75338d4a57cdc382830fafd946d2ed887a08bab
*** Bug 380828 has been marked as a duplicate of this bug. ***
*** Bug 381226 has been marked as a duplicate of this bug. ***
It looks like bug 385535 says this (or a related crash) is still happening with KF5 5.38 and Plasma 5.11.
There is a bit of a regression related to this one. On wayland you can click on "Graphical information>opengl" all good, but if you click on "wayland" and then "opengl" again, infocenter will close with not triggering drkonqui.
Can we assume that the bug is indeed in wayland libraries? Also happening with recent master versions, see bug 385633.
*** Bug 385535 has been marked as a duplicate of this bug. ***
*** Bug 385633 has been marked as a duplicate of this bug. ***
Created attachment 108965 [details] New crash information added by DrKonqi kinfocenter (5.11.3) using Qt 5.9.2 The bug is still present on OpenSuse Tumbleweed (Plasma 5.11.3 Frameworks 54 Applications 5.11.3 Qt 5.9.2). I attached a backtrace with full debug symbols. -- Backtrace (Reduced): #6 0x00007f44fc419d39 in wl_map_insert_at (map=<optimized out>, flags=<optimized out>, i=<optimized out>, data=<optimized out>) at src/wayland-util.c:249 #7 0x00007f44fc415e4e in proxy_destroy (proxy=0x5570003ac7f0) at src/wayland-client.c:411 #8 wl_proxy_destroy (proxy=0x5570003ac7f0) at src/wayland-client.c:442 #9 0x00007f44fa6b5e85 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=0x5570003a6980, this=0x5570003a6980) at /usr/src/debug/kwayland-5.40.0/src/client/wayland_pointer_p.h:53