ABI changed without a corresponding soname change

Bug #117732 reported by Tollef Fog Heen
104
Affects Status Importance Assigned to Milestone
ekiga (Ubuntu)
Fix Released
High
Unassigned
Gutsy
Fix Released
High
Unassigned

Bug Description

On gutsy i386:

ekiga: symbol lookup error: ekiga: undefined symbol: _ZN11SIPEndPoint8RegisterERK7PStringS2_S2_S2_S2_i

downgrading opal to the version in 7.04 fixes it.

Related branches

Changed in opal:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Olivier Cortès (olive) wrote :

Hi, there is still a problem with this, making ekiga unusable on up-to-date gutsy (as of 20070920 19:23 UTC+2):

$ ekiga &
ekiga: symbol lookup error: /usr/lib/libopal.so.2.2: undefined symbol: _ZN11PSafeObjectC2Ev

didn't investigate further but will be glad to have instructions to follow.

Revision history for this message
Olivier Cortès (olive) wrote :

ok, i need my webcam to work somehow, so i tried to fix this bug and it's easy :

sudo apt-get source libopal-2.2.0
sudo apt-get build-dep libopal-2.2.0
cd libopal-2.2.0
dch -i "rebuild to fix LP #117732."
debuild
sudo dpkg -i ../libopal-2.2.0*deb ../simpleopal*deb

and ekiga works !!

Revision history for this message
Stéphane Graber (stgraber) wrote :

Simply rebuilding libopal caused segfauls here (when doing a SIP call)

I have rebuilt both libopal and ekiga, test packages are available in my PPA:
deb http://ppa.launchpad.net/stgraber/ubuntu gutsy main restricted universe multiverse

It's simply a rebuild of libopal, then a rebuild of ekiga using the new libopal and with a small configure change so it uses the new libpt (so configure now works)

I'll attach both debdiff soon

Revision history for this message
Stéphane Graber (stgraber) wrote :
Revision history for this message
Stéphane Graber (stgraber) wrote :
Revision history for this message
Olivier Cortès (olive) wrote :

Yup, sorry for my false positive. Ekiga effectively "runs", but I haven't done any phone/SIP call yet. I'm currently using ekiga to test a Webcam (uvc driver), because ekiga seems to be the one and only app in ubuntu to know how to handle v4l2/uvc devices (qtwengophone crashes, camorama uses old API and can't connect, don't have K* installed).

Revision history for this message
Stéphane Graber (stgraber) wrote :

No problem.
For uvc testing you may want to use the luvcview software (you have to compile it by hand though) which I use to test my QuickCam sphere.
It's available at : http://mxhaard.free.fr/spca50x/Investigation/uvc/luvcview-20070512.tar.gz

Revision history for this message
Stéphane Graber (stgraber) wrote :

Sorry I didn't upload the right file :)
This one contains the build-depends change

Revision history for this message
Olivier Cortès (olive) wrote :

Luvcview works too, I found it yesterday night googling. I didn't mention it because there is no ubuntu package, so "apt-cache search uvc" returns nothing besides "uvc-source", which could be misleading because uvc driver is already in the kernel...

-> Anyway thanks for the link and your help !!

Note that ekiga compiles and runs just fine with your first debdiff, because strict libpt-dev version is not needed as there is only one version in gutsy (As a debian maintainer on my freetime, I prefer not to "force" a particular version when a program compiles/runs with previous ones too, but that could a matter of personal taste, correct me if I miss something).

Changed in opal:
assignee: nobody → stgraber
status: Triaged → In Progress
Revision history for this message
Fernando Ribeiro (ipsec) wrote :
Changed in opal:
assignee: stgraber → fernando
status: In Progress → Fix Committed
Revision history for this message
Christopher Denter (dennda) wrote :

Hi there.
I get the same error:
----
dennda@cave:~$ ekiga -c sip:foo@bar
ekiga: symbol lookup error: /usr/lib/libopal.so.2.2: undefined symbol: _ZN11PSafeObjectC2Ev
----

(This also happens with really existing sip-adresses.)
I hope this gets fixed in gutsy. :)

regards

Revision history for this message
Brian Fallik (bfallik) wrote :

same error here ( undefined symbol: _ZN11PSafeObjectC2Ev)

Revision history for this message
Fernando Ribeiro (ipsec) wrote :

ekiga (2.0.11-1ubuntu1) gutsy; urgency=low

  * Close (LP: #117732)
  * Resynchronized with Debian, only Ubuntu changes are:
    - debian/control.in, debian/patches/01_lpi.dpatch,
      debian/patches/02_autoconf.dpatch:
      - Launchpad Integration
    - debian/control.in, debian/patches/42_change_pixmaps.dpatch:
      - patched icons.
    - debian/patches/trayicon_transparency.dpatch,
      debian/patches/os-detection.dpatch,
      debian/patches/50_fix_POTFILES.in.dpatch:
      - Distro fixes.
    - debian/control.in:
      - Added Maintainer to MOTU
      - Updated Build-Depends
      - Updated Depends
      - Dropped Suggests
    - debian/ekiga.menu:
      - Updated
    - debian/rules:
      - Added dbus support
      - intltool magic.

ekiga (2.0.11-1) unstable; urgency=low

  * New upstream release.
  * Bump build-depends to PWLib 1.10.10 and OPAL 2.2.11. (Closes: #443501)
  * Use pkg-gnome's version of get-orig-source (gnome-get-source.mk)
  * Remove armel.dpatch - included upstream.
  * Use debian/compat rather than setting DH_COMPAT
  * Use Applications in menu rather than Apps

 -- Fernando Ribeiro <email address hidden> Mon, 24 Sep 2007 11:58:54 -0300

Changed in ekiga:
status: Fix Committed → Fix Released
Revision history for this message
Richie Ward (richies) wrote :

I do not believe this is fixed.

richie@richie-desktop:~$ ekiga
ekiga: symbol lookup error: /usr/lib/libopal.so.2.2: undefined symbol: _ZN11PSafeObjectC2Ev
richie@richie-desktop:~$

This is with latest gutsy updates.

Revision history for this message
ccc1 (cllccl-deactivatedaccount) wrote :

yeah the new version isn't uploaded to gusty yet.
i think we have to be a bit more patient ;)

Revision history for this message
Olivier Guéry (nemolivier) wrote :

Same problem here (with an AMD64 and a dua-core dell laptop)
On the AMD64 I get the sources of the last stable (2.0.11) and compile them : it seems to work (but I wanted to call the laptop… and my girlfriend don’t want me to mess her laptop with compiled things :o) — she’s wright !)

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

This is clearly not fixed in current gutsy. Resetting status to 'fix committed'. Please correct me if I'm wrong, but I'm still getting this bug.

Revision history for this message
Stéphane Graber (stgraber) wrote :

Ekiga has been uploaded but it's currently missing a build-dep to be built : https://launchpad.net/ubuntu/gutsy/+builds?build_text=ekiga&build_state=all
Once the new opal is uploaded, the build should start and the new ekiga will appear in Gutsy.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

it's uploaded, should be in the archives now.

There was a massive lot of stuff to build over the weekend (& friday)- you just need to have patience, and know that uploaded doesn't automatically mean "has been built yet" - there is a queue, and sometimes it's longer than others.

Revision history for this message
GabrielGrant (gabrielgrant) wrote :

Sarah: That's true, but it I thought a bug isn't supposed to be marked as "Fix Released" until the fix is, in fact, available. Is that not the intended distinction between the "Fix Committed" and "Fix Released" statuses?

Thanks,
-Gabriel

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote : Re: [Bug 117732] Re: ABI changed without a corresponding soname change

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This all depends on the definition of fix released - mine tends to be
"in the ubuntu archive", which includes anything between when it is
ACCEPTED (and hits gutsy-changes), and is actually published, and in the
archive.

We (who are not archive admins) can't actually push the bugs any further
than this - we have to wait for soyuz, etc, to sort itself out. So for
all intents and purposes, i'd say that this should be marked Fix
Released, yes.

Also, the bug closing by changelog comes in somewhere - i think when the
package itself is accepted - where it is automatically marked as fix
released.

Hobbsee

GabrielGrant wrote:
> Sarah: That's true, but it I thought a bug isn't supposed to be marked
> as "Fix Released" until the fix is, in fact, available. Is that not the
> intended distinction between the "Fix Committed" and "Fix Released"
> statuses?
>
> Thanks,
> -Gabriel
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHAH9P7/o1b30rzoURAqKkAKCENz99ViYdwHlmSjEMr31wGYSg5gCeKEX2
5WGCpMVzz14vYNxcUaBtpP4=
=Fb90
-----END PGP SIGNATURE-----

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 117732] Re: ABI changed without a corresponding soname change

Sarah Hobbs [2007-10-01 5:02 -0000]:
> Also, the bug closing by changelog comes in somewhere - i think when the
> package itself is accepted - where it is automatically marked as fix
> released.

When the source package is published, to be precise. I. e. during a
freeze the bug will not be marked as fixreleased until the RM actually
accepts the uploaded package.

Revision history for this message
Christopher Denter (dennda) wrote :

Sorry if I mess things up here:
The update is already available through update-manager (the description even has a link to this bug report) but cannot be installed since I cannot tick the checkbox.
I guess this has to do with what Stéphane said:
>Ekiga has been uploaded but it's currently missing a build-dep to be built : >https://launchpad.net/ubuntu/gutsy/+builds?build_text=ekiga&build_state=all
>Once the new opal is uploaded, the build should start and the new ekiga will appear in Gutsy.

If this is true and I just have to wait please ignore this posting and go on with your more important work. :)

regards

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.