Ubuntu
libgpod package

libgpod causes segfault on startup

Bug #40359 reported by Jeremy Kerr
8
Affects Status Importance Assigned to Milestone
libgpod (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I'm getting a segfault when starting gtkpod on my machine:

[jk@pokey ~]$ gtkpod
libhal.c 2213 : LibHalContext *ctx is NULL
libhal.c 2568 : LibHalContext *ctx is NULL
Segmentation fault
[jk@pokey ~]$

I believe this may be specific to powerpc.

After a little googling, I've found that this is fixed after the libgpod 0.3.2 release (all hal-related code has since been removed: http://cvs.sourceforge.net/viewcvs.py/*checkout*/gtkpod/libgpod/ChangeLog - see the 2006-02-17 commit).

Looks like the developer has acknowledged this here: http://comments.gmane.org/gmane.comp.ipod.gtkpod.user/204

Details:
Architecture: powerpc
Ubuntu version: Dapper beta, as of 20/04/06
libgpod version: 0.3.2-0ubuntu1
gtkpod version: 0.99.2-1ubuntu1

Additional details:

from valgrinding gtkpod, I see a null pointer dereference:

Invalid read of size 4
   at 0xF407DB0: (within /usr/lib/libgpod.so.0.302.0)
   by 0xF47C8B4: g_object_newv (in /usr/lib/libgobject-2.0.so.0.1000.2)
   by 0xF47CF8C: g_object_new_valist (in /usr/lib/libgobject-2.0.so.0.1000.2)
   by 0xF47D158: g_object_new (in /usr/lib/libgobject-2.0.so.0.1000.2)
   by 0xF4067B0: itdb_device_new (in /usr/lib/libgpod.so.0.302.0)
   by 0xF3FC3FC: itdb_set_mountpoint (in /usr/lib/libgpod.so.0.302.0)
   by 0x1002D744: init_data (in /usr/bin/gtkpod)
   by 0x10044178: main (in /usr/bin/gtkpod)
 Address 0x0 is not stack'd, malloc'd or (recently) free'd

Cheers!

Jeremy

Revision history for this message
Joachim Beckers (jbeckers) wrote :

I can confirm this on daper x86 with gtkpod 0.99.2-1ubuntu1 and libgpod 0.3.2-0ubuntu1. It doesn't really segfault instantly here, only eventually. I do get I/O errors however, that are likely caused by this problem.

I suggest updating libgpod to version 0.3.3 (available here: http://www.gtkpod.org/stuff/libgpod-0.3.3.tar.gz) as suggested by the gtkpod authors themselves.

Also worth mentioning: syncing gtkpod with debian (they're at version 0.99.4-blabla won't resolve the problem.

Revision history for this message
Joachim Beckers (jbeckers) wrote :

This bug causes gtkpod (and possibly other apps relying on libgpod) to not work at all.

Changed in libgpod:
status: Unconfirmed → Confirmed
Revision history for this message
Matt Zimmerman (mdz) wrote :

Debian unstable is at 0.3.2-1, which is what our package is based on.

This bug doesn't seem to affect rhythmbox, only gtkpod (universe).

I'm not very comfortable about pulling in a new upstream version, where significant amounts of code are said to have been rewritten, this late in the release cycle, but if someone can do some regression testing with it, that would help.

Revision history for this message
Jeremy Kerr (jk-ozlabs) wrote :

It also seems to affect the amaroK 1.4 beta though (installed packages from kubuntu.org), but I'm not sure about the vanilla amaroK in Dapper. I can give it a go if you need another data point.

I'd be happy to test the new libgpod, if it helps.

Revision history for this message
Joachim Beckers (jbeckers) wrote :

just a follow up:

I don't see errors any longer, with libgpod 0.3.2-0ubuntu1 and gtkpod 0.99.2-1ubuntu2. the I/O-errors I had were caused by https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/37163

I'm marking this needinfo (if I have the permission to do so) so that someone can check wether powerpc is still affected.

Changed in libgpod:
status: Confirmed → Needs Info
Revision history for this message
Jeremy Kerr (jk-ozlabs) wrote :

Works fine on edgy - amarok can sync just fine now.

Revision history for this message
Sebastien Bacher (seb128) wrote :

works fine on edgy according to comment, marking fixed

Changed in libgpod:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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