Summary: | kontact crash after network status changed | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | LuRan <hephooey_dev> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ahartmetz, andresbajotierra, chanika |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
LuRan
2010-01-27 23:52:20 UTC
This looks like a variant of bug 223313... Regards LuRan: I am pretty sure that this bug was fixed in revision 1078887, nevertheless it would be interesting to know the kdelibs revision you were using at the time. The checkin comment of r1078887 is: - Make it explicit which job of a connected slave is running, fixing a spurious assert failure. - Fix a bug masked by the previous bug: Don't try to "unschedule" twice queued jobs of a slave that is being killed. The second item fixes this bug, it breaks the "infinite" recursion by marking the job as unscheduled in removeSlave() so cancelJob() will bail out early and *not* call removeSlave() again. I have just updated to rev 1081672, I tried to switch between wired and wireless network a few times and have not get any crash yet. I guess the crash is fixed. *** Bug 224558 has been marked as a duplicate of this bug. *** |