Bug 223176 - gtkpod: undefined symbol: itdb_device_set_mountpoint
gtkpod: undefined symbol: itdb_device_set_mountpoint
Product: Fedora
Classification: Fedora
Component: libgpod (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Depends On:
  Show dependency treegraph
Reported: 2007-01-18 00:28 EST by Jason Farrell
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-18 04:46:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jason Farrell 2007-01-18 00:28:22 EST
Description of problem:
With the libgpod currently in updates-testing (and the new compat-libgpod),
gtkpod crashes when attempting to mount the ipod by clicking the "Load Ipod(s)"

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. yum --enablerepo=updates-testing install libgpod
2. run gtkpod from the terminal then click the "load ipod" button
Actual results:
gtkpod crashes with the following error:
gtkpod: symbol lookup error: gtkpod: undefined symbol: itdb_device_set_mountpoint

Expected results:

Additional info:
Reverting to the previous version (libgpod-0.4.0-0.fc6) fixes the problem:
rpm -e --nodeps compat-libgpod libgpod && yum update
Comment 1 Alexander Larsson 2007-01-18 04:46:02 EST
0.4.0 was never in fc6, because it is binary incompatible to the 0.3 version in
fc6 but doesn't change the soname. Where did you get that from, and if the
gtkpod is built against that i can understand why it crashes with the 0.3.2 in
the compat update. Thats not really a fedora issue though.
Comment 2 Jason Farrell 2007-01-18 15:26:15 EST
Yeah, you're right - i didn't look closely enough at it. Both libgpod (0.4.0)
and gtkpod were provided by freshrpms, and the compat update wont place nice
with it.

Note You need to log in before you can comment on or make changes to this bug.