dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #43935
[Bug 2015962] Re: 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()
I accepted indicator-messages into lunar-proposed but, sadly, it didn't
build. The issue is on the binary-package level:
https://launchpad.net/ubuntu/+source/indicator-
messages/13.10.1+18.10.20180918-0ubuntu4
Basically what's happening is that indicator-messages and ayatana-
indicator-messages both build the libmessaging-menu* binary packages.
This is not right. Both are available in the archive for lunar. So
indicator-messages cannot be published as it tries to upload the new
binaries but it sees newer versioned ones (from ayatana) already - and
bails.
We probably need to drop the libmessaging-menu* packages from indicator-
messages.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
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:
Fix Committed
Status in indicator-messages package in Ubuntu:
Invalid
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