Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18233 - [xulrunner] libxul.so segfaults when application tries to use GtkMozEmbed
Attached to Project:
Arch Linux
Opened by Pavel (heavyrail) - Monday, 08 February 2010, 12:19 GMT
Last edited by Jan de Groot (JGC) - Thursday, 05 May 2011, 10:36 GMT
Opened by Pavel (heavyrail) - Monday, 08 February 2010, 12:19 GMT
Last edited by Jan de Groot (JGC) - Thursday, 05 May 2011, 10:36 GMT
|
DetailsDescription: libxul.so segfaults when application tries to use GtkMozEmbed
Additional info: glib2 2.22.4-1 xulrunner 1.9.2—2 firefox 3.6-2 Steps to reproduce: Here is a test application in Python, although I tried C and PHP, and all of these segfaults as well. Create a text file called test.py and put the following code in it: #!/usr/bin/python import gtk import gtkmozembed win = gtk.Window() browser = gtkmozembed.MozEmbed() win.add(browser) win.show_all() gtk.main() Make the file executable by issuing chmod +x test.py Execute the file and you would get 'Segmentation fault' at the console and something like test.py[1589]: segfault at 0 ip b56c87ab sp bf80f198 error 4 in libxul.so[b552b000+bd0000] at the bottom of dmesg output. Temporary fix: This problem may be fixed by issuing export MOZILLA_FIVE_HOME=`grep moz_libdir= /usr/bin/xulrunner | cut -d= -f 2` before executing test.py, but that's no good, and there should be another way to fix it correct. |
This task depends upon
Closed by Jan de Groot (JGC)
Thursday, 05 May 2011, 10:36 GMT
Reason for closing: Won't fix
Additional comments about closing: Besides setting MOZILLA_FIVE_HOME, the other suggested workaround no longer fixes this. We won't fix this anymore, as gtkmozembed will be unsupported upstream.
Thursday, 05 May 2011, 10:36 GMT
Reason for closing: Won't fix
Additional comments about closing: Besides setting MOZILLA_FIVE_HOME, the other suggested workaround no longer fixes this. We won't fix this anymore, as gtkmozembed will be unsupported upstream.
edit: I can still reproduce this.