After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 608709 - Can't create a new account on 2.29.6
Can't create a new account on 2.29.6
Status: RESOLVED DUPLICATE of bug 608510
Product: libgnome-keyring
Classification: Core
Component: General
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-02-01 18:57 UTC by Luis Medinas
Modified: 2019-02-22 11:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
debug log (5.56 KB, text/plain)
2010-02-09 01:57 UTC, Luis Medinas
Details

Description Luis Medinas 2010-02-01 18:57:08 UTC
Hi

Using empathy 2.29.6 the dialog doesn't allow me to create new accounts, the save button is grey (sensitive) and i can't save the new account.
Comment 1 Guillaume Desmottes 2010-02-08 16:04:00 UTC
Which kind of account are you trying to create? Did you file all the fields?
Comment 2 Luis Medinas 2010-02-08 23:55:59 UTC
Correction the save button doesn't have any action this happens with all accounts. Probably is some missing callback on the save button that doesn't allow me to create any account.
Comment 3 Luis Medinas 2010-02-09 01:57:10 UTC
Created attachment 153300 [details]
debug log

It seems something wrong is happening with telepathy-mission-control.
I have version 5.3.2 installed.
Comment 4 Guillaume Desmottes 2010-02-09 14:26:07 UTC
empathy/Account-DEBUG: 02/09/2010 01:55:08.366127: accounts_dialog_manager_ready_cb: Failed to prepare account manager: Process /usr/lib/mission-control-5 received signal 6

Seems to be a problem in telepathy-mission-control-5. Can you run it manually (you have to kill it before) using MC_DEBUG=5 before starting Empathy and attach MC5 logs please?
Comment 5 Luis Medinas 2010-02-09 16:49:11 UTC
Mission control:

MC_DEBUG=5 /usr/lib/mission-control-5 
(process:15126): mcd-DEBUG: telepathy-mission-control version 5.3.2
(process:15126): mcd-DEBUG: mcd_service_init: called
(process:15126): mcd-DEBUG: mcd_account_manager_init: Loading accounts from /home/metalgod/.mission-control/accounts/accounts.cfg
(process:15126): mcd-DEBUG: mcd_client_registry_constructed: Starting to look for clients
(process:15126): mcd-DEBUG: _mcd_account_constructed: 0x66d820 (butterfly/msn/metalfisico_40hotmail_2ecom0)
(process:15126): mcd-DEBUG: mcd_manager_setup: Manager butterfly created
(process:15126): mcd-DEBUG: _mcd_mission_set_parent: child = 0x65ad00, parent = 0x660000
(process:15126): mcd-DEBUG: _mcd_account_constructed: 0x66d900 (salut/local_2dxmpp/account0)
(process:15126): mcd-DEBUG: mcd_manager_setup: Manager salut created
(process:15126): mcd-DEBUG: _mcd_mission_set_parent: child = 0x66f040, parent = 0x660000
(process:15126): mcd-DEBUG: _mcd_account_constructed: 0x66d9e0 (gabble/jabber/lmedinas_40gmail_2ecom0)
(process:15126): mcd-DEBUG: mcd_manager_setup: Manager gabble created
(process:15126): mcd-DEBUG: _mcd_mission_set_parent: child = 0x66f0b0, parent = 0x660000
(process:15126): mcd-DEBUG: release_load_accounts_lock: called, count is now 3
(process:15126): mcd-DEBUG: _mcd_mission_set_parent: child = 0x665830, parent = 0x667320
(process:15126): mcd-DEBUG: _mcd_account_maybe_autoconnect: salut/local_2dxmpp/account0 not Valid
(process:15126): mcd-DEBUG: _mcd_account_maybe_autoconnect: gabble/jabber/lmedinas_40gmail_2ecom0 not Enabled
(process:15126): mcd-DEBUG: _mcd_account_maybe_autoconnect: butterfly/msn/metalfisico_40hotmail_2ecom0 not Valid
(process:15126): mcd-DEBUG: mcd_service_constructed: called
(process:15126): mcd-DEBUG: mcd_service_obtain_bus_name: Requesting MC dbus service
(process:15126): mcd-DEBUG: Object Hierarchy of object 0x660000
(process:15126): mcd-DEBUG: [
(process:15126): mcd-DEBUG:     McdService (0x660000): 6
(process:15126): mcd-DEBUG:         McdManager (0x66f0b0): 2
(process:15126): mcd-DEBUG:         McdManager (0x66f040): 2
(process:15126): mcd-DEBUG:         McdManager (0x65ad00): 2
(process:15126): mcd-DEBUG: ]
(process:15126): mcd-DEBUG: mcd_client_registry_list_names_cb: ListNames returned
(process:15126): mcd-DEBUG: list_connection_names_cb: 0 connections
(process:15126): mcd-DEBUG: mcd_client_registry_list_activatable_names_cb: ListActivatableNames returned
(process:15126): mcd-DEBUG: _mcd_client_registry_found_name: Registering client org.freedesktop.Telepathy.Client.Empathy
(process:15126): mcd-DEBUG: mcd_client_proxy_constructed: org.freedesktop.Telepathy.Client.Empathy
(process:15126): mcd-DEBUG: _mcd_client_registry_inc_startup_lock: 1 -> 2
(process:15126): mcd-DEBUG: _mcd_client_registry_dec_startup_lock: 2 -> 1
(process:15126): mcd-DEBUG: _mcd_client_proxy_parse_client_file: File found for org.freedesktop.Telepathy.Client.Empathy: /usr/share/telepathy/clients/Empathy.client
(process:15126): mcd-DEBUG: _mcd_client_proxy_add_interfaces: org.freedesktop.Telepathy.Client.Empathy: org.freedesktop.Telepathy.Client.Handler
(process:15126): mcd-DEBUG: _mcd_client_proxy_add_interfaces: org.freedesktop.Telepathy.Client.Empathy: org.freedesktop.Telepathy.Client.Interface.Requests
(process:15126): mcd-DEBUG: mcd_client_proxy_introspect: org.freedesktop.Telepathy.Client.Empathy is a Handler but not active
(process:15126): mcd-DEBUG: mcd_client_registry_ready_cb: org.freedesktop.Telepathy.Client.Empathy
(process:15126): mcd-DEBUG: _mcd_client_registry_dec_startup_lock: 1 -> 0
(process:15126): mcd-DEBUG: mcd_dispatcher_client_registry_ready_cb: All initial clients have been inspected
(process:15126): mcd-DEBUG: _mcd_client_proxy_dup_handler_capabilities: org.freedesktop.Telepathy.Client.Empathy:
(process:15126): mcd-DEBUG: _mcd_client_proxy_dup_handler_capabilities: - 1 channel filters
(process:15126): mcd-DEBUG: _mcd_client_proxy_dup_handler_capabilities: - 0 capability tokens:
(process:15126): mcd-DEBUG: _mcd_client_proxy_dup_handler_capabilities: -end-
(process:15126): mcd-DEBUG: on_manager_ready: manager butterfly is ready
(process:15126): mcd-DEBUG: mcd_account_check_parameters: called for butterfly/msn/metalfisico_40hotmail_2ecom0
(process:15126): mcd-DEBUG: on_manager_ready: manager salut is ready
(process:15126): mcd-DEBUG: mcd_account_check_parameters: called for salut/local_2dxmpp/account0
(process:15126): mcd-DEBUG: release_load_accounts_lock: called, count is now 2
(process:15126): mcd-DEBUG: _mcd_account_maybe_autoconnect: salut/local_2dxmpp/account0 does not ConnectAutomatically
(process:15126): mcd-DEBUG: on_manager_ready: manager gabble is ready
(process:15126): mcd-DEBUG: mcd_account_check_parameters: called for gabble/jabber/lmedinas_40gmail_2ecom0
**
ERROR:gnome-keyring.c:105:prepare_get_secret: assertion failed: (path)
Aborted
Comment 6 Guillaume Desmottes 2010-02-09 17:21:29 UTC
The assertion error is in libgnome-keyring; do you have any similar problem with other apps using gnome-keyring?
Comment 7 Guillaume Desmottes 2010-02-09 17:22:16 UTC
Could you also run telepathy-mission-control-5 in gdb and attach a trace please?
Comment 8 Luis Medinas 2010-02-09 17:26:59 UTC
Here's the backtrace:

ERROR:gnome-keyring.c:105:prepare_get_secret: assertion failed: (path)

Program received signal SIGABRT, Aborted.
0x00007ffff67dd4e5 in raise () from /lib64/libc.so.6
(gdb) bt
  • #0 raise
    from /lib64/libc.so.6
  • #1 abort
    from /lib64/libc.so.6
  • #2 g_assertion_message
    from /usr/lib64/libglib-2.0.so.0
  • #3 g_assertion_message_expr
    from /usr/lib64/libglib-2.0.so.0
  • #4 ??
    from /usr/lib64/libgnome-keyring.so.0
  • #5 gnome_keyring_item_info_free
    from /usr/lib64/libgnome-keyring.so.0
  • #6 gnome_keyring_item_info_free
    from /usr/lib64/libgnome-keyring.so.0
  • #7 ??
    from /lib64/libdbus-1.so.3
  • #8 dbus_connection_dispatch
    from /lib64/libdbus-1.so.3
  • #9 ??
    from /usr/lib64/libgnome-keyring.so.0
  • #10 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #11 ??
    from /usr/lib64/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #13 main
    at mc-server.c line 81
  • #0 raise
    from /lib64/libc.so.6
  • #1 abort
    from /lib64/libc.so.6
  • #2 g_assertion_message
    from /usr/lib64/libglib-2.0.so.0
  • #3 g_assertion_message_expr
    from /usr/lib64/libglib-2.0.so.0
  • #4 ??
    from /usr/lib64/libgnome-keyring.so.0
  • #5 gnome_keyring_item_info_free
    from /usr/lib64/libgnome-keyring.so.0
  • #6 gnome_keyring_item_info_free
    from /usr/lib64/libgnome-keyring.so.0
  • #7 ??
    from /lib64/libdbus-1.so.3
  • #8 dbus_connection_dispatch
    from /lib64/libdbus-1.so.3
  • #9 ??
    from /usr/lib64/libgnome-keyring.so.0
  • #10 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #11 ??
    from /usr/lib64/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #13 main
    at mc-server.c line 81

It seems something bad on gnome-keyring (2.29.5)
Comment 9 Guillaume Desmottes 2010-02-09 17:58:07 UTC
Re-assigning to gnome-keyring for now to see what they think.
Comment 10 Jürg Billeter 2010-02-11 20:18:02 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 608510 ***