Summary: | KRunner crashed when exectuting a command [QVariant, QtDbus, Kephal::DBusConfigurations::activeConfiguration, Kephal::ScreenUtils::primaryScreenId, ..., KRunnerDialog::positionOnScreen] | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | Tom Albers <toma> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | aitoralzolamolina, andresbajotierra, dev, h0rr0rr_drag0n, kdelibs-bugs, matthias.sweertvaegher, pablo, sam, till2.schaefer |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tom Albers
2010-01-12 21:25:31 UTC
This looks related to Kephal From bug 222596: -- Information about the crash: I am able to reproduce 222486 and thought I'd report another stacktrace in case it contains any other info that may help solve this case. I rebooted and saw nepomuk was running and indexing again. Krunner normally does not crash, but when I type amarok, some data is found in the nepomuk database because I visited the amarok site, which seems to cause a crash..? I will let you know if I can reproduce the crash in a consistent way. In any case, when nepomuk is not indexing, krunner does not crash -- I can confirm that I am using a dual monitor setup.. (in which my primary monitor is right of the secondary (usually it's the other way round)) Since the latest rc, I may have noted unexpected behavior in on which monitor a window pops up. Maybe that's related. Normally, when you press alt-F2, the krunner should open on the monitor the mouse is on, and also the application which you launch. I seem to remember that the application does not always show up on the monitor I expect. *** Bug 222596 has been marked as a duplicate of this bug. *** *** Bug 232749 has been marked as a duplicate of this bug. *** *** Bug 233560 has been marked as a duplicate of this bug. *** *** Bug 242059 has been marked as a duplicate of this bug. *** *** Bug 234753 has been marked as a duplicate of this bug. *** [Comment from a bug triager] As noted in bug 251890 this could also have been related to the dbus threading issues, fixed in libdbus 1.4.0 and later *** Bug 231812 has been marked as a duplicate of this bug. *** |