| Summary: | Plasma crashes anytime. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | chenlinux945 |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | plasma-bugs-null |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.18.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
chenlinux945
2020-03-30 15:17:44 UTC
Maybe this bug is thes same as mine : https://bugs.kde.org/show_bug.cgi?id=418767#c0 Trace is completely different QtXCB is hitting a fatal assertion for some reason. #37 0x00007fc2625be537 in __run_exit_handlers () at /usr/lib/libc.so.6 #40 0x00007fc25df80bc4 in () at /usr/lib/libQt5XcbQpa.so.5 Then we happen to crash when we're doing an unexpected teardown, but the real important thing is the unexpected teardown. Is your X setup unusual in any way? I'm using a DisplayLink screen : https://www.asus.com/us/Monitors/MB16AC/ I don't know if it's a particular setup, but it needs many configurations. The ASUS screen is a second monitor, not the main one. debug symbols for /usr/lib/libQt5XcbQpa.so.5 will help Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! The bug doesn't appears any more (or rarely) so I'm marking it as REPORTED. There aren't many places in Qt's xcb platform plugin that call exit(), so it is possible to investigate without debug symbols, see https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/xcb/qxcbconnection.cpp#n982 I suggest to report this issue directly to Qt developers via https://bugreports.qt.io/ |