Bug 17382 - assertion fails if you try to set the alias for a buddy not on your list
Summary: assertion fails if you try to set the alias for a buddy not on your list
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: haze (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Will Thompson
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-01 01:33 UTC by Will Thompson
Modified: 2009-04-04 03:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Will Thompson 2008-09-01 01:33:20 UTC 
#0  0xb7f48424 in __kernel_vsyscall ()
#1  0xb7be5ef5 in raise () from /lib/i686/cmov/libc.so.6
#2  0xb7be7871 in abort () from /lib/i686/cmov/libc.so.6
#3  0xb7dfde52 in g_assertion_message () from /usr/lib/libglib-2.0.so.0
#4  0xb7dfe37d in g_assertion_message_expr () from /usr/lib/libglib-2.0.so.0
#5  0x0804f8bc in set_aliases_foreach (key=0x2, value=0x9a72948, user_data=0xbf9613f0) at connection-aliasing.c:172
#6  0xb7dc8ec6 in g_hash_table_foreach () from /usr/lib/libglib-2.0.so.0
#7  0x0804f9d6 in haze_connection_set_aliases (self=0x9a7a050, aliases=0x9bcef68, context=0x9ab0240) at connection-aliasing.c:214
#8  0xb7d837c7 in tp_svc_connection_interface_aliasing_set_aliases (self=0x9a7a050, in_aliases=0x9bcef68, context=0x9ab0240) at _gen/tp-svc-connection.c:895
#9  0xb7d7d953 in _tp_marshal_VOID__BOXED_POINTER (closure=0xbf96170c, return_value=0x0, n_param_values=3, param_values=0x9ab4300, invocation_hint=0x0, marshal_data=0xb7d83780) at _gen/signals-marshal.c:236
#10 0xb7ba96b9 in ?? () from /usr/lib/libdbus-glib-1.so.2
#11 0xbf96170c in ?? ()
#12 0x00000000 in ?? ()

The assumption was that the handle being valid => the person being on your blist.  Clearly false.
Comment 1 Will Thompson 2009-03-25 17:18:54 UTC 
Fixed in Git, will be in 0.3.0.
Comment 2 Will Thompson 2009-04-04 03:39:55 UTC 
Fixed in 0.3.0.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.