Hi,

Downgrading in Ubuntu/Debian is never safe, I would avoid it. If you can 
compile sflphoned from sources, it might solve the problem for now. You can 
semi automate the process of fetching the dependencies using "sudo apt-get 
build-dep sflphone-daemon" and then follow the steps on our website.

----- Original Message -----
From: "Jan Middelkoop" <[email protected]>
To: "Emmanuel Lepage" <[email protected]>
Cc: [email protected]
Sent: Wednesday, June 6, 2012 10:01:43 AM
Subject: Re: [SFLphone] Segfaults today in sflphoned

Hi Emmanuel,

Thank you for your reply.  Ubuntu has updated a bunch of packages.  
Probably related to that then.

Any idea which of these might cause these problems?  Which shall I 
downgrade again?

Start-Date: 2012-06-06  11:16:13
Commandline: apt-get upgrade
Upgrade:

libsmbclient:amd64 (3.6.3-2ubuntu2.1, 3.6.3-2ubuntu2.2)
libpolkit-backend-1-0:amd64 (0.104-1, 0.104-1ubuntu1)
libkrb5-3:amd64 (1.10+dfsg~beta1-2, 1.10+dfsg~beta1-2ubuntu0.1)
libk5crypto3:amd64 (1.10+dfsg~beta1-2, 1.10+dfsg~beta1-2ubuntu0.1)
libpam-winbind:amd64 (3.6.3-2ubuntu2.1, 3.6.3-2ubuntu2.2)
unity:amd64 (5.12-0ubuntu1, 5.12-0ubuntu1.1)
update-notifier-common:amd64 (0.119ubuntu8.1, 0.119ubuntu8.4)
libcupsppdc1:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
bind9-host:amd64 (9.8.1.dfsg.P1-4, 9.8.1.dfsg.P1-4ubuntu0.1)
libcupsimage2:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
libcupscgi1:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
smbclient:amd64 (3.6.3-2ubuntu2.1, 3.6.3-2ubuntu2.2)
libcupsdriver1:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
libgnome-control-center1:amd64 (3.4.1-0ubuntu2, 3.4.2-0ubuntu0.2)
dnsutils:amd64 (9.8.1.dfsg.P1-4, 9.8.1.dfsg.P1-4ubuntu0.1)
bamfdaemon:amd64 (0.2.114-0ubuntu1, 0.2.118-0ubuntu0.1)
unity-common:amd64 (5.12-0ubuntu1, 5.12-0ubuntu1.1)
libnm-util2:amd64 (0.9.4.0-0ubuntu4, 0.9.4.0-0ubuntu4.1)
libgl1-mesa-dri:amd64 (8.0.2-0ubuntu3, 8.0.2-0ubuntu3.1)
cups-client:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
libgl1-mesa-glx:amd64 (8.0.2-0ubuntu3, 8.0.2-0ubuntu3.1)
libpolkit-gobject-1-0:amd64 (0.104-1, 0.104-1ubuntu1)
libdns81:amd64 (9.8.1.dfsg.P1-4, 9.8.1.dfsg.P1-4ubuntu0.1)
libwbclient0:amd64 (3.6.3-2ubuntu2.1, 3.6.3-2ubuntu2.2)
gnome-control-center-data:amd64 (3.4.1-0ubuntu2, 3.4.2-0ubuntu0.2)
libglapi-mesa:amd64 (8.0.2-0ubuntu3, 8.0.2-0ubuntu3.1)
policykit-1:amd64 (0.104-1, 0.104-1ubuntu1)
grub-pc:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1)
libisccc80:amd64 (9.8.1.dfsg.P1-4, 9.8.1.dfsg.P1-4ubuntu0.1)
cups-ppdc:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
update-manager-core:amd64 (0.156.14.4, 0.156.14.5)
samba-common:amd64 (3.6.3-2ubuntu2.1, 3.6.3-2ubuntu2.2)
cups-common:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
network-manager:amd64 (0.9.4.0-0ubuntu4, 0.9.4.0-0ubuntu4.1)
liblwres80:amd64 (9.8.1.dfsg.P1-4, 9.8.1.dfsg.P1-4ubuntu0.1)
libcups2:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
libnm-glib-vpn1:amd64 (0.9.4.0-0ubuntu4, 0.9.4.0-0ubuntu4.1)
libkrb5support0:amd64 (1.10+dfsg~beta1-2, 1.10+dfsg~beta1-2ubuntu0.1)
libnm-glib4:amd64 (0.9.4.0-0ubuntu4, 0.9.4.0-0ubuntu4.1)
libunity-core-5.0-5:amd64 (5.12-0ubuntu1, 5.12-0ubuntu1.1)
libgcrypt11:amd64 (1.5.0-3, 1.5.0-3ubuntu0.1)
ssl-cert:amd64 (1.0.28, 1.0.28ubuntu0.1)
libxatracker1:amd64 (8.0.2-0ubuntu3, 8.0.2-0ubuntu3.1)
libbind9-80:amd64 (9.8.1.dfsg.P1-4, 9.8.1.dfsg.P1-4ubuntu0.1)
cups:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
samba:amd64 (3.6.3-2ubuntu2.1, 3.6.3-2ubuntu2.2)
unity-services:amd64 (5.12-0ubuntu1, 5.12-0ubuntu1.1)
grub-pc-bin:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1)
gimp:amd64 (2.8.0-1ubuntu0ppa4~precise, 2.8.0-1ubuntu0ppa5~precise)
cups-bsd:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
libgimp2.0:amd64 (2.8.0-1ubuntu0ppa4~precise, 2.8.0-1ubuntu0ppa5~precise)
libisccfg82:amd64 (9.8.1.dfsg.P1-4, 9.8.1.dfsg.P1-4ubuntu0.1)
krb5-locales:amd64 (1.10+dfsg~beta1-2, 1.10+dfsg~beta1-2ubuntu0.1)
libpolkit-agent-1-0:amd64 (0.104-1, 0.104-1ubuntu1)
gnome-control-center:amd64 (3.4.1-0ubuntu2, 3.4.2-0ubuntu0.2)
samba-common-bin:amd64 (3.6.3-2ubuntu2.1, 3.6.3-2ubuntu2.2)
winbind:amd64 (3.6.3-2ubuntu2.1, 3.6.3-2ubuntu2.2)
grub-common:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1)
grub2-common:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1)
libglu1-mesa:amd64 (8.0.2-0ubuntu3, 8.0.2-0ubuntu3.1)
libgssapi-krb5-2:amd64 (1.10+dfsg~beta1-2, 1.10+dfsg~beta1-2ubuntu0.1)
libcupsmime1:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu1)
libisc83:amd64 (9.8.1.dfsg.P1-4, 9.8.1.dfsg.P1-4ubuntu0.1)
gimp-data:amd64 (2.8.0-1ubuntu0ppa4~precise, 2.8.0-1ubuntu0ppa5~precise)
libbamf3-0:amd64 (0.2.114-0ubuntu1, 0.2.118-0ubuntu0.1)
libbamf0:amd64 (0.2.114-0ubuntu1, 0.2.118-0ubuntu0.1)
Error: Sub-process /usr/bin/dpkg returned an error code (1)

End-Date: 2012-06-06  11:17:46

Kindest regards,

Jan Middelkoop
Recreatie en Zorg Groep B.V.

-- 
Website: http://www.recreatie-zorg.nl/
E-mail: [email protected]
Telephone: +31 10 714 22 97


Op 06-06-12 15:54, Emmanuel Lepage schreef:
> Can you please install sflphone debug symbols (or compile it) then run it 
> with a tool called gdb:
>
> gdb /path/to/sflphoned
>> run
> in other shell:
> sflphone-client-gnome
>
> back in the gdb shell, you will see the prompt again with the segfault error 
> message, and write "backtrace".
>
> This will give us the details we need.
>
> But looking at the error you gave us, it seem that your sflphone is not in 
> sync with your C library. Have you done any major system updates?
>
> ----- Original Message -----
> From: "Jan Middelkoop"<[email protected]>
> To: [email protected]
> Sent: Wednesday, June 6, 2012 8:44:46 AM
> Subject: Re: [SFLphone] Segfaults today in sflphoned
>
> Hi,
>
> Some more info:
>
> When I start sflphoned, and then sflphone-client-gnome, I can see
> sflphoned segfaults as soon as I click to start a new call on the Gnome
> client.  Before even entering a phone number, sflphoned segfaults.
>
> If then go on to enter a phone number (while sflphoned isn't running),
> and press 'enter' to place the call, a new instance of sflphoned is
> launched by the Gnome client, which makes the call, but the Gnome client
> doesn't seem to be 'connected' to the sflphoned properly.  There's no
> sound heard on the headset, and when the call is hung up by the Gnome
> client, sflphoned still continues to call.
>
> I have no idea why this problem suddenly appeared, but it's causing some
> big problems for me.  Any help would be very welcome, as I'm a bit out
> of ideas at the moment.
>
> Kindest regards,
>
> Jan Middelkoop
> Recreatie en Zorg Groep B.V.
>
_______________________________________________
SFLphone mailing list
[email protected]
http://lists.savoirfairelinux.net/mailman/listinfo/sflphone

Reply via email to