Your message dated Sat, 04 Apr 2020 20:33:50 +0000
with message-id <[email protected]>
and subject line Bug#954771: fixed in telepathy-mission-control-5 1:5.16.5-2
has caused the Debian Bug report #954771,
regarding telepathy-mission-control-5 broken by strict checks in recent glib
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
954771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954771
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: empathy
Version: 3.25.90+really3.12.14-2
Severity: important
Dear Maintainers,
when I start empathy, if first asks me to import my accounts from pidgin.
However this doesn't work at all, but nevermind.
The real issue: When I try to manually add any account for any protocoll
(tried Jabber and SIP) clicking on the "Add" button just shows no
visible response at all. Since I can't add any accounts, this renders
the package unusable for me.
A web search turns up some sporadic forum posts discussion this issue
over the past decade. Most of them end in "Oh, no [eg after rebooting]
it suddenly works." Well, rebooting didn't solve the problem for me.
Since I'm not running a full gnome desktop, my first guess was, that
some vital dependency might be missing, which actual gnome users never
notice. But after installing all gnome components, that might be remotely
related to storing account data, up to gnome-control-center, the issue
still persists.
I got the following debug output during the critical action of clicking
the "Add" button:
EMPATHY_DEBUG=all G_MESSAGES_DEBUG=all empathy
(empathy:3596): tp-glib/accounts-DEBUG: 23:48:09.567:
tp_account_request_create_account_cb: failed to create account:
(empathy:3596): tp-account-widgets-DEBUG: 23:48:09.568:
account_widget_applied_cb: Could not apply changes to account:
(empathy:3596): tp-glib/proxy-DEBUG: 23:48:09.568:
tp_proxy_pending_call_lost_weak_ref: 0xaaaada9eab00 lost weak ref to
0xaaaada52e6e0
(empathy:3596): tp-glib/proxy-DEBUG: 23:48:09.568:
tp_proxy_pending_call_cancel: 0xaaaada9eab00
Please note, that telepathy unhelpfully provides empty error messages
for the problem.
During the same operation this is the debug output from mission-control:
G_MESSAGES_DEBUG=all MC_DEBUG=all /usr/lib/telepathy/mission-control-5
(process:3557): mcd-DEBUG: 23:48:09.562: _mcd_account_manager_create_account:
called
(process:3557): mc-plugins-DEBUG: 23:48:09.563:
mcp_account_storage_set_attribute: accounts-sso:
(process:3557): mc-plugins-DEBUG: 23:48:09.563: mcp_account_storage_set:
accounts-sso:
(process:3557): mcd-DEBUG: 23:48:09.563: update_storage: MCP:accounts-sso ->
ignore gabble/jabber/foo_40jabber_2ede1.manager
(process:3557): mc-plugins-DEBUG: 23:48:09.563:
mcp_account_storage_set_attribute: goa:
(process:3557): mc-plugins-DEBUG: 23:48:09.563: mcp_account_storage_set: goa:
(process:3557): mcd-DEBUG: 23:48:09.563: update_storage: MCP:goa -> ignore
gabble/jabber/foo_40jabber_2ede1.manager
(process:3557): mc-plugins-DEBUG: 23:48:09.563:
mcp_account_storage_set_attribute: default-gkeyfile:
(process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set:
default-gkeyfile:
(process:3557): mcd-DEBUG: 23:48:09.564: update_storage: MCP:default-gkeyfile
-> store gabble/jabber/foo_40jabber_2ede1.manager
(process:3557): mc-plugins-DEBUG: 23:48:09.564:
mcp_account_storage_set_attribute: accounts-sso:
(process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set:
accounts-sso:
(process:3557): mcd-DEBUG: 23:48:09.564: update_storage: MCP:accounts-sso ->
ignore gabble/jabber/foo_40jabber_2ede1.protocol
(process:3557): mc-plugins-DEBUG: 23:48:09.564:
mcp_account_storage_set_attribute: goa:
(process:3557): mc-plugins-DEBUG: 23:48:09.564: mcp_account_storage_set: goa:
(process:3557): mcd-DEBUG: 23:48:09.564: update_storage: MCP:goa -> ignore
gabble/jabber/foo_40jabber_2ede1.protocol
(process:3557): mc-plugins-DEBUG: 23:48:09.564:
mcp_account_storage_set_attribute: default-gkeyfile:
(process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set:
default-gkeyfile:
(process:3557): mcd-DEBUG: 23:48:09.565: update_storage: MCP:default-gkeyfile
-> store gabble/jabber/foo_40jabber_2ede1.protocol
(process:3557): mc-plugins-DEBUG: 23:48:09.565:
mcp_account_storage_set_attribute: accounts-sso:
(process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set:
accounts-sso:
(process:3557): mcd-DEBUG: 23:48:09.565: update_storage: MCP:accounts-sso ->
ignore gabble/jabber/foo_40jabber_2ede1.DisplayName
(process:3557): mc-plugins-DEBUG: 23:48:09.565:
mcp_account_storage_set_attribute: goa:
(process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set: goa:
(process:3557): mcd-DEBUG: 23:48:09.565: update_storage: MCP:goa -> ignore
gabble/jabber/foo_40jabber_2ede1.DisplayName
(process:3557): mc-plugins-DEBUG: 23:48:09.565:
mcp_account_storage_set_attribute: default-gkeyfile:
(process:3557): mc-plugins-DEBUG: 23:48:09.565: mcp_account_storage_set:
default-gkeyfile:
(process:3557): mcd-DEBUG: 23:48:09.566: update_storage: MCP:default-gkeyfile
-> store gabble/jabber/foo_40jabber_2ede1.DisplayName
(process:3557): GLib-GObject-CRITICAL **: 23:48:09.566:
g_object_new_is_valid_property: object class 'McdAccount' has no property named
'connectivity-monitor'
(process:3557): mcd-DEBUG: 23:48:09.566: _mcd_account_dispose: 0xaaaafa63f490
((null))
(process:3557): mcd-DEBUG: 23:48:09.566: _mcd_account_finalize: 0xaaaafa63f490
((null))
(process:3557): GLib-GObject-CRITICAL **: 23:48:09.566: object McdAccount
0xaaaafa63f490 finalized while still in-construction
(process:3557): GLib-GObject-CRITICAL **: 23:48:09.566: Custom constructor for
class McdAccount returned NULL (which is invalid). Please use GInitable instead.
Since I don't have a working installation to compare against, I don't
know which messages are related to the issue at hand. At this point it
seems likely, that the issue is not in empathy, but somewhere in
telepathy. I'm not experienced with gnome, freedesktop.org, dbus,
telepathy etc to figure out, how to properly debug this or even who is
actually responsible.
I'm willing to put more effort into figuring this out, but I'd need
somebody to point me in the right direction.
Unless the missing dependency theory turns out to be correct, this
probably is an upstream bug. But I can't report it there, not knowing
which component is at fault.
TIA,
Harald
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 5.3.0-2-arm64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
LANGUAGE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages empathy depends on:
ii dbus-user-session [default-dbus-session-bus] 1.12.16-2
ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1
ii empathy-common 3.25.90+really3.12.14-2
ii geoclue-2.0 2.5.6-1
ii gsettings-desktop-schemas 3.36.0-1
ii gstreamer1.0-pulseaudio 1.16.2-2
ii libc6 2.30-2
ii libcairo2 1.16.0-4
ii libcanberra-gtk3-0 0.30-7
ii libcanberra0 0.30-7
ii libchamplain-0.12-0 0.12.20-1
ii libchamplain-gtk-0.12-0 0.12.20-1
ii libcheese-gtk25 3.34.0-1+b1
ii libclutter-1.0-0 1.26.4+dfsg-1
ii libclutter-gst-3.0-0 3.0.27-1
ii libclutter-gtk-1.0-0 1.8.4-4
ii libcogl-path20 1.22.4-4
ii libcogl20 1.22.4-4
ii libdbus-glib-1-2 0.110-3
ii libenchant-2-2 2.2.8-1
ii libfarstream-0.2-5 0.2.8-5
ii libfolks-telepathy25 0.13.2-1
ii libfolks25 0.13.2-1
ii libgcr-base-3-1 3.34.0-1
ii libgcr-ui-3-1 3.34.0-1
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-3
ii libgee-0.8-2 0.20.3-1
ii libgeocode-glib0 3.26.2-1
ii libglib2.0-0 2.64.1-1
ii libgoa-1.0-0b 3.36.0-1
ii libgstreamer-plugins-base1.0-0 1.16.2-2
ii libgstreamer1.0-0 1.16.2-2
ii libgtk-3-0 3.24.14-1
ii libgudev-1.0-0 233-1
ii libmission-control-plugins0 1:5.16.5-1
ii libnotify4 0.7.9-1
ii libpango-1.0-0 1.42.4-8
ii libpulse-mainloop-glib0 13.0-5
ii libpulse0 13.0-5
ii libsecret-1-0 0.20.2-1
ii libsoup2.4-1 2.70.0-1
ii libtelepathy-farstream3 0.6.2-1+b2
ii libtelepathy-glib0 0.24.1-2+b1
ii libtelepathy-logger3 0.8.2-4
ii libwebkit2gtk-4.0-37 2.28.0-2
ii libx11-6 2:1.6.9-2
ii libxml2 2.9.10+dfsg-4
ii telepathy-logger 0.8.2-4
ii telepathy-mission-control-5 1:5.16.5-1
Versions of packages empathy recommends:
ii gnome-contacts 3.34-2
ii gvfs-backends 1.44.0-1
ii sound-theme-freedesktop 0.8-2
ii telepathy-gabble 0.18.4-1
ii telepathy-haze 0.8.0-2.1
ii telepathy-salut 0.8.1-5.1
Versions of packages empathy suggests:
pn telepathy-idle <none>
pn vino <none>
Versions of packages empathy is related to:
ii telepathy-gabble [telepathy-connection-manager] 0.18.4-1
ii telepathy-haze [telepathy-connection-manager] 0.8.0-2.1
ii telepathy-rakia [telepathy-connection-manager] 0.8.0-3+b1
ii telepathy-salut [telepathy-connection-manager] 0.8.1-5.1
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: telepathy-mission-control-5
Source-Version: 1:5.16.5-2
Done: Sjoerd Simons <[email protected]>
We believe that the bug you reported is fixed in the latest version of
telepathy-mission-control-5, which is due to be installed in the Debian FTP
archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sjoerd Simons <[email protected]> (supplier of updated
telepathy-mission-control-5 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 04 Apr 2020 22:03:25 +0200
Source: telepathy-mission-control-5
Architecture: source
Version: 1:5.16.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Telepathy maintainers
<[email protected]>
Changed-By: Sjoerd Simons <[email protected]>
Closes: 954771
Changes:
telepathy-mission-control-5 (1:5.16.5-2) unstable; urgency=medium
.
[ Laurent Bigonville ]
* Add support for usr-merge in the apparmor profile, from Ubuntu.
* debian/control: Mark the -doc package as Multi-arch: foreign
.
[ Debian Janitor ]
* Use versioned copyright format URI.
* Set debhelper-compat version in Build-Depends.
* Re-export upstream signing key without extra signatures.
.
[ Sjoerd Simons ]
* d/p/account-Fix-property-name.patch: Fix property naming in account class,
fixes running with newer glib. (Closes: #954771)
Checksums-Sha1:
78f0a00e97b39b3b7f832f8ca77a41174831ba98 3091
telepathy-mission-control-5_5.16.5-2.dsc
1e0ac3797fc94eab442fd91ba10f5653f45de036 16080
telepathy-mission-control-5_5.16.5-2.debian.tar.xz
4a49e4a1ee64411bae0e46d0579c51e8d6e16a2f 10167
telepathy-mission-control-5_5.16.5-2_amd64.buildinfo
Checksums-Sha256:
29428b46cacafa7f292c366c5e270fff47b2d10e7afe0fda83d5f0057ec52953 3091
telepathy-mission-control-5_5.16.5-2.dsc
e9b9ae45cbd3739342cb7b36a479d95cd66ab36f0ee38ff22b6c0fa7a2c3f054 16080
telepathy-mission-control-5_5.16.5-2.debian.tar.xz
5dad86a7c858a2280ea08d10e06ed9cd9e4941bf18cfc717d9928ad365895dad 10167
telepathy-mission-control-5_5.16.5-2_amd64.buildinfo
Files:
00a68a4c03e1a1888da7baba18df21c8 3091 net optional
telepathy-mission-control-5_5.16.5-2.dsc
8df56dab33f9e80bbe3f3c57ed0d6c39 16080 net optional
telepathy-mission-control-5_5.16.5-2.debian.tar.xz
8d6667611a61152ceaad86853a21ef1f 10167 net optional
telepathy-mission-control-5_5.16.5-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEKHCjG+qdvPJ0cjEIwnTbZMIwD3sFAl6I6O0ACgkQwnTbZMIw
D3vSVxAAsLghhjgg+3fXJ60jjjkqigCuac/cYMC9+XGspZsy4UPgFhOjDaYKJDGh
9UfApq2chhc0+eNt/H1WPEnm3Zx8FwLCm7r0MeOqw9loqgDH2eG4D/fthbTsqns7
a0bg+8QxuwVUqup2/LWJ3RFtUy/XZSJ5kuiUc9yMpS7RPzHCU29CrTALlAQFCAGP
VqMcd3HXrdMGbESI9thASlEQ+j1ZjCY+R6GvlHXpQqrKLFR9CN6GbneXXvAh0w5F
/gGpUzPbKImg7wVcIErVlXU06nKk4Re6kSAZ1NhlpagMBwnVifb8XXPMkAWq0sWl
gl+btjnngbkIKo20CFmIKeIAhs6IkKeadkOTy3bzNLvJ0SqmEUBytkrPyH5qkosN
EIM1AVufIefmNAgfuP+q4oIqc94juQc8bmVFM4rm6ZHqgmk4BQDYRB524FfVBUMJ
SWZvtIepXBYHtNUHI2ORAFCS6ocgDTdFJZmebFb7uQH5/dZxJgey0bGf4hB+nCbD
pDg4nEaq+q+vTl/jYsCvmCsZ0/oYNQ98VwYbV0dGvKVZjlBaQ+NlV7HrpZiz6MdJ
+iEBF1zDEYrxlTeBwUfjpFWPUnBzOu90ES+/7s+Uf3yYif4ZPluCw2cnmyCPV1bh
2Qjt88d/1mJseXrRwabL/zK+zrpZQmkAzaHhRrL2X5KxsZy4baU=
=zEIB
-----END PGP SIGNATURE-----
--- End Message ---
