Summary: | krunner crashes while nepomuk was indexing | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | matthias sweertvaegher <matthias.sweertvaegher> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
matthias sweertvaegher
2010-01-13 01:26:01 UTC
I wonder if this could be related to bug 210695. Regards I may also add, because of giving nepomuk more resources, it also started more processes. I don't know if it matters, but I also have 4 cores. the reproducibility of this bug seems quite okay. I just tried: reenable nepomuk file indexer. press alt-F2 and type amarok. it does not crash, after a few seconds some nepomuk data is listed too. Then I press backspace until all chars are gone and type "ama" again. currently, it does not crash, but hangs without crashes (maybe because this time I did not reboot, but rather just reenabled nepomuk file indexer). in this case you can't use krunner anymore and you also cannot easily kill it since ctrl+esc does not work :) when i kill it in console the command line of krunner says: "krunner --nocrashhandler". maybe that's the reason why it does not want to crash? :) after killing it, I cannot open krunner anymore using alt-F2, neither from console: it shows some output about registering runners, but gui does not show up and nepomuk goes down again. Merging with bug 224085 as backtraces matches. Regards *** This bug has been marked as a duplicate of bug 224085 *** |