[exaile/gutsy] crash in lib gtkembedmoz

In that case, I'd suggest filing a bug with the upstream and linking it here when you've done so.

isn't launchpad capable of doing so ?

Only for projects that are also hosted in Launchpad, which it appears exaile is not.

What Launchpad can do is create a link to an existing (in this case reported by you) bug in the upstream bug tracker, you just need to feed it a url, and then keep status of the upstream bug current in LP as it changes.

In that case, I don't see the point of using launchpad at all as I always have to explain everything twice. LP has no added value for that kind of project (same for most of gnome). I'd better stick to upstream bug systems.

As long as you are certain you know which errors are Ubuntu specific and
which are Debian's or upstream's then there is no great harm in that. In
the case since the bug is in LP, please link the upstream bug when you file
it.

I think it's ubuntu specific.
I have the exact same crash with 'listen' (another audio player) while doing similar action. Exact same gdb stack.

So it may not be exaile's or listen's fault. Maybe it's firefox, maybe gobject, maybe something else.
I've provided as much details as I could think of. I'm no good at debugging python so if someone wants me to try something to move forward, I'm all hears.

I can confirm it happens with a simple script like this:

import gtk
import gtkmozembed

class TinyGecko:
    def __init__(self):
        self.moz = gtkmozembed.MozEmbed()
        self.moz.load_url('about:plugins')

        win = gtk.Window()
        win.add(self.moz)
        win.show_all()

if __name__ == '__main__':
  TinyGecko()
  gtk.main()

Same here. From what I can see, python/gtkmozembed tries to read firefox files from the user home dir, which is wrong.
Ex: it tries to use the components dir in ~/components/ instead of /usr/lib/firefox/components.

Seems related to bug #22487

setting both LD_LIBRARY_PATH=/usr/lib/firefox *and* MOZILLA_FIVE_HOME=/usr/lib/firefox before starting python fixed it.

fta@ix:~$ LD_LIBRARY_PATH=/usr/lib/firefox python /tmp/foo
Segmentation fault (core dumped)
fta@ix:~$ MOZILLA_FIVE_HOME=/usr/lib/firefox python /tmp/foo
Segmentation fault (core dumped)
fta@ix:~$ MOZILLA_FIVE_HOME=/usr/lib/firefox LD_LIBRARY_PATH=/usr/lib/firefox python /tmp/foo
LoadPlugin: failed to initialize shared library libXt.so [libXt.so: cannot open shared object file: No such file or directory]
LoadPlugin: failed to initialize shared library libXext.so [libXext.so: cannot open shared object file: No such file or directory]
LoadPlugin: failed to initialize shared library /usr/lib/jvm/java-6-sun-1.6.0.02/jre/plugin/i386/ns7/libjavaplugin_oji.so [/usr/lib/jvm/java-6-sun-1.6.0.02/jre/plugin/i386/ns7/libjavaplugin_oji.so: undefined symbol: _ZTVN10__cxxabiv121__vmi_class_type_infoE]

I had the same problem (there is another bug submission here: https://bugs.launchpad.net/ubuntu/+source/python2.5/+bug/148370) and starting exaile with |MOZILLA_FIVE_HOME=/usr/lib/firefox LD_LIBRARY_PATH=/usr/lib/firefox exaile" seems to work fine

I have no idea how to link this to bug #136202, but it's marked fixed upstream.

Attached the fix against exaile 0.2.10+debian-1.1ubuntu1

Note that the patch is incomplete and does not modify the makefile.

oops, it was complete in my local tree.

Uploaded. Now will need a release manager ack before having it published inside the archive. Thanks to everyone for reporting this issue, I can say "it has been fixed" now.

exaile (0.2.10+debian-1.1ubuntu2) gutsy; urgency=low

  * 03_gtkembedmoz_crash_fix: added to fix a crash related to lib gtkembedmoz
    when trying to display any sub-tab like Artist/lyrics using the
    latest exaile release. Steps to reproduce it can be found on the bug report.
    Thanks to Fabien Tassin for reporting and fixing this issue. (LP: #123409)

 -- Andrea Veri <email address hidden> Sun, 14 Oct 2007 21:15:49 +0200

The root cause of this is bug 157126, ie empty --with-default-mozilla-five-home passed to firefox configure.
It's getting fixed by the mozilla team.

Marking this invalid in Exaile; I didn't know this was an Ubuntu- (and Debian-?) specific bug, and that the "fix" breaks other distros that correctly specifies the default MOZILLA_FIVE_HOME (bug 162430). I might re-break this upstream, but I'll wait a while to give bug 157126 some time to get fixed.

FYI, bug 157126 is fixed in Hardy starting to 2.0.0.8+2nobinonly-0ubuntu2.
Gutsy will be updated with the next security upload.