Could you confirm that those loaded the new library version? Because I
confirmed locally that the segfault and valgrind error were fixed with
the new release, at least in the testcase described upstream (but could
be that the issue referred to is different from the one
reported/triggered by the testcase)
** Changed in: accountsservice (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: indicator-messages (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2015962
Title:
indicator-messages-service crashed with SIGSEGV in
g_type_check_instance() from g_signal_handlers_disconnect_matched()
from act_user_manager_finalize() from g_object_unref() from
im_accounts_service_dispose()
Status in accountsservice:
Fix Released
Status in accountsservice package in Ubuntu:
Incomplete
Status in indicator-messages package in Ubuntu:
Incomplete
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
indicator-messages. This problem was most recently seen with package version
13.10.1+18.10.20180918-0ubuntu3, the problem page at
https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
