Bug 29509

Summary: rtcom-accounts-ui crashes with MSN
Product: Telepathy Reporter: Alban Crequy <alban.crequy>
Component: m5-account-pluginsAssignee: Jonny Lamb <jonny.lamb>
Status: NEW --- QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: 0.8   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Alban Crequy 2010-08-11 08:40:24 UTC
I am trying to add a MSN account in control-panel -> IM accounts.

Program received signal SIGSEGV, Segmentation fault.
fill_advanced_table (plugin=<value optimized out>, service=0x1590c8, account=0x7a9b8, table=0x1a6580) at butterfly-plugin.c:62
62	butterfly-plugin.c: No such file or directory.
	in butterfly-plugin.c
(gdb) bt
#0  fill_advanced_table (plugin=<value optimized out>, service=0x1590c8, account=0x7a9b8, table=0x1a6580) at butterfly-plugin.c:62
#1  0x4185e66c in ?? () from /usr/lib/liblongcat.so.1
#2  0x4185e66c in ?? () from /usr/lib/liblongcat.so.1
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) p service
$1 = (RtcomAccountService *) 0x1590c8
(gdb) p service->protocol
$2 = (const TpConnectionManagerProtocol *) 0x0
(gdb) p   service->protocol->params
Cannot access memory at address 0x4
(gdb) 

It happens when I have a bogus butterfly installed:

$ dpkg --contents telepathy-butterfly_0.5.11-1maemo0_all.deb
drwxr-xr-x root/root         0 2010-08-11 16:11:23 ./
drwxr-xr-x root/root         0 2010-08-11 16:11:23 ./usr/
drwxr-xr-x root/root         0 2010-08-11 16:11:24 ./usr/share/
drwxr-xr-x root/root         0 2010-08-11 16:11:23 ./usr/share/doc/
drwxr-xr-x root/root         0 2010-08-11 16:11:24 ./usr/share/doc/telepathy-butterfly/
-rw-r--r-- root/root      2103 2010-08-11 10:41:08 ./usr/share/doc/telepathy-butterfly/changelog.Debian.gz
-rw-r--r-- root/root     24374 2010-06-08 15:53:32 ./usr/share/doc/telepathy-butterfly/changelog.gz
$

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.