Summary: | krunner crashes when starting another app | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | Anatoly Berbeka <ekzo.tech> |
Component: | general | Assignee: | Kai Uwe Broulik <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | justin.zobel |
Priority: | NOR | Keywords: | drkonqi, triaged |
Version: | 5.14.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Anatoly Berbeka
2018-10-20 05:57:57 UTC
Can you try to reproduce with debugging symbols for qtcore? Also perhaps run krunner from console and see what it outputs there. #11 0x00007fbf544c4dc5 in qt_assert(char const*, char const*, int) () at /usr/lib64/libQt5Core.so.5 #12 0x00007fbf544c7198 in () at /usr/lib64/libQt5Core.so.5 ← This line I'm interested but you lack debug symbols #13 0x00007fbf52c8f554 in start_thread () at /lib64/libpthread.so.0 #14 0x00007fbf53fe2ccf in clone () at /lib64/libc.so.6 Ok, so I tried to run krunner from console, then pushed Alt+F2 and started typing, then krunner instantly crashed with this output: --- krunner crash output from console --- terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' org.kde.plasma.runner.appstream: Had errors when loading AppStream metadata pool "" KCrash: Attempting to start /usr/bin/krunner from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'krunner' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 14 and type 'Read', disabling... QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Exception', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... radeon: Failed to allocate a buffer: radeon: size : 4096 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: flags : 4 radeon: The kernel rejected CS, see dmesg for more information (-9). radeon: Failed to allocate a buffer: radeon: size : 4096 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: flags : 4 radeon: Failed to allocate a buffer: radeon: size : 4096 bytes radeon: alignment : 4096 bytes radeon: domains : 2 radeon: flags : 0 radeon: Failed to allocate a buffer: radeon: size : 4096 bytes radeon: alignment : 4096 bytes radeon: domains : 2 radeon: flags : 0 radeon: The kernel rejected CS, see dmesg for more information (-9). radeon: Failed to allocate a buffer: radeon: size : 4096 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: flags : 4 radeon: Failed to allocate a buffer: radeon: size : 4096 bytes radeon: alignment : 4096 bytes radeon: domains : 4 radeon: flags : 4 [1] + 27744 suspended (signal) krunner -- END --- Those errors about 'Failed to allocate a buffer' repeats many times, so I cut most of them. But they are absolutely the same like 2 last. -- dmesg last line (because previous lines are too old) -- [102873.345766] radeon_dp_aux_transfer_native: 242 callbacks suppressed --- END --- (In reply to Kai Uwe Broulik from comment #1) > Can you try to reproduce with debugging symbols for qtcore? Also perhaps run > krunner from console and see what it outputs there. > > #11 0x00007fbf544c4dc5 in qt_assert(char const*, char const*, int) () at > /usr/lib64/libQt5Core.so.5 > #12 0x00007fbf544c7198 in () at /usr/lib64/libQt5Core.so.5 ← This line I'm > interested but you lack debug symbols > #13 0x00007fbf52c8f554 in start_thread () at /lib64/libpthread.so.0 > #14 0x00007fbf53fe2ccf in clone () at /lib64/libc.so.6 I'm not very familiar with Qt, is rebuilding qtcore with debug support is the only option? I couldn't find how to do this without rebuilding. 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 set the bug status 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! 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! Still got crashed krunner when running apps. Thank you for the report, Anatoly. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |