Summary: | Crash Reporting while Muon is running makes the Crash Reporting Assistant crash | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Jay H. <jayhacker> |
Component: | Updates (interactive) | Assignee: | Jonathan Thomas <echidnaman> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | platonus18 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.0 | |
Sentry Crash Report: |
Description
Jay H.
2012-08-16 17:05:30 UTC
Ok, what seems to have happened here is that a second frontend application using LibQApt was performing a cache update, which happened to finish as you were starting the update manager. In QApt1 all events were sent globally to every frontend, so in certain situations you could get a reload event when the program was still starting up, causing this crash. Worker actions are now handled through a transaction system in QApt2, and only somebody actively listening to a transaction will get events related to that transaction. *** Bug 317859 has been marked as a duplicate of this bug. *** |