Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=387441.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
** Changed in: exaile (Fedora)
Status: Confirmed => Fix Released
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: exaile (Fedora)
Status: Unknown => Confirmed
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Bug watch added: Red Hat Bugzilla #387441
https://bugzilla.redhat.com/show_bug.cgi?id=387441
** Also affects: exaile (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=387441
Importance: Unknown
Status: Unknown
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.laun
FYI, bug 157126 is fixed in Hardy starting to 2.0.0.8+2nobinonly-0ubuntu2.
Gutsy will be updated with the next security upload.
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
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
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.
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ub
** Tags added: mozilla
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
** Changed in: exaile
Status: Fix Committed => Fix Released
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
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 Fabi
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/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because
oops, it was complete in my local tree.
** Attachment added: "fix v2"
http://launchpadlibrarian.net/9979811/fix_crash_in_gtkembedmoz_bug123409.patch
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member o
Note that the patch is incomplete and does not modify the makefile.
** Changed in: exaile
Importance: Undecided => High
Assignee: (unassigned) => Adam Olsen (arolsen)
Status: New => Fix Committed
Target: None => 0.2.11
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs
Attached the fix against exaile 0.2.10+debian-1.1ubuntu1
** Attachment added: "fix_crash_in_gtkembedmoz_bug123409.patch"
http://launchpadlibrarian.net/9979679/fix_crash_in_gtkembedmoz_bug123409.patch
** Changed in: exaile (Ubuntu)
Status: New => Confirmed
--
[exaile/gutsy] crash in l
I have no idea how to link this to bug #136202, but it's marked fixed
upstream.
** Also affects: exaile
Importance: Undecided
Status: New
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubu
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
--
[exaile/gutsy] crash in lib gtkembedmoz
https:
setting both LD_LIBRARY_PATH=/usr/lib/firefox *and*
MOZILLA_FIVE_HOME=/usr/lib/firefox before starting python fixed it.
[EMAIL PROTECTED]:~$ LD_LIBRARY_PATH=/usr/lib/firefox python /tmp/foo
Segmentation fault (core dumped)
[EMAIL PROTECTED]:~$ MOZILLA_FIVE_HOME=/usr/lib/firefox python /tmp/foo
Seg
Seems related to bug #22487
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
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.
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/12340
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.sho
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
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.
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.n
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.
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bug
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
ch
isn't launchpad capable of doing so ?
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
In that case, I'd suggest filing a bug with the upstream and linking it
here when you've done so.
--
[exaile/gutsy] crash in lib gtkembedmoz
https://bugs.launchpad.net/bugs/123409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
26 matches
Mail list logo
