| Summary: | crashed during creation of the new association of *.aspx to be opend by kate | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | max5555 <max_ph> |
| Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | andresbajotierra, cfeck, osezno141 |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
max5555
2008-12-26 22:50:26 UTC
The backtrace looks related to the one in bug 173325 This does not look like a kdelibs bug. For sure, it is NOT a Solid bug. Looking at the backtrace the following happens: * KOpenWithDialog is accepted and calls hide() * Something in Qt fails to hide the widget, it runs through some widgetAt() and eventually causes an XIOError * that XIOError calls exit() * static globals are deleted there, including the Solid globals * Dolphin also seems to have some global exit() handler installed (not sure why), and calls into KIO during ~DolphinSettings * the Solid query from KIO now accesses an invalid Solid backend manager -> crash I am not sure why Qt would cause an XIOError, but that part of the backtrace should be send to Qt Software for inspection. Some googling revealed
../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy->request)) >= 0)' failed.
so it looks like Xlib bug https://bugs.freedesktop.org/show_bug.cgi?id=14211
https://bugs.launchpad.net/xorg-server/+bug/185311 suggests
export LIBXCB_ALLOW_SLOPPY_LOCK=1
for a workaround.
*** Bug 173325 has been marked as a duplicate of this bug. *** |