Summary: | System Settings crashed randomly in the background. | ||
---|---|---|---|
Product: | [Plasma] lightdm | Reporter: | Ashlar <atrystan> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | tbuckner2 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ashlar
2012-10-24 13:02:03 UTC
*** Bug 311963 has been marked as a duplicate of this bug. *** To reproduce: - open LightDM KCM - close it - manipulate users The bug itself is in QLightDM, but we may as well track it here. The user's list is a singleton in the wrapped GObject library, so it can't get deleted when we close the KCM. Our model wrapping this, however, does get deleted. When the callback occurs to say the user's have changed, it's trying to run code on an object that no longer exists.. and therefore crashes. g-signals don't disconnect when an object is deleted like in Qt. We do try and disconnect manually: UsersModelPrivate::~UsersModelPrivate() { g_signal_handlers_disconnect_by_func(lightdm_user_list_get_instance(), NULL, this); } however, clearly this isn't working. Now tracked at: https://bugs.launchpad.net/lightdm/+bug/1092409 Fix will be in the next version of LightDM (not the KDE code). |