Bug 6610 - libxul.so.0 segfaults with gnome-python-gtkmozembed (mga1 & 2) or perl-Gtk2-MozEmbed (mga1)
Summary: libxul.so.0 segfaults with gnome-python-gtkmozembed (mga1 & 2) or perl-Gtk2-M...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-28 18:58 CEST by claire robinson
Modified: 2013-11-23 16:16 CET (History)
1 user (show)

See Also:
Source RPM: xulrunner
CVE:
Status comment:


Attachments
python scripts used for testing (698 bytes, application/x-gzip)
2012-06-28 19:33 CEST, claire robinson
Details

Description claire robinson 2012-06-28 18:58:20 CEST
This affects both mga1 and mga2, also probably cauldron. It could also date back to 2008.

Please refer to the firefox 10.0.5 update on bug 6548 comment 15 for mga2 and bug 6389 comment 9 onwards for mga1.

$ python moz.py

** (process:7640): WARNING **: Trying to register gtype 'GMountMountFlags' as
enum when in fact it is of type 'GFlags'

** (process:7640): WARNING **: Trying to register gtype 'GDriveStartFlags' as
enum when in fact it is of type 'GFlags'

** (process:7640): WARNING **: Trying to register gtype 'GSocketMsgFlags' as
enum when in fact it is of type 'GFlags'
Segmentation fault


syslog says:
kernel: [ 4909.279373] python[7688]: segfault at 0 ip 00007f5d881df6f7 sp
00007fffbca28890 error 4 in libxul.so[7f5d87c0e000+19d3000]

$ perl moz.pl
Segmentation fault


We were not sure if this was relevant:
http://mandriva.598463.n5.nabble.com/Bug-30801-perl-Gtk2-MozEmbed-ASSIGNED-perl-Gtk2-MozEmbed-crash-unless-the-firefox-path-is-added-to-ef-td649829.html
Comment 1 claire robinson 2012-06-28 19:33:12 CEST
Created attachment 2502 [details]
python scripts used for testing

perl-Gtl2-MozEmbed test script found at 

http://search.cpan.org/~tsch/Gtk2-MozEmbed-0.06/MozEmbed.pm#SEE_ALSO
claire robinson 2012-06-28 19:39:20 CEST

Assignee: bugsquad => dmorganec

Comment 2 Olivier Blin 2012-09-08 20:38:21 CEST
Does it still happen if you uninstall lib64proxy-mozjs? (install lib64proxy-webkit first to satisfy the libproxy dependencies)

If so, it is a dup of bug 6299

CC: (none) => mageia

D Morgan 2013-09-18 00:03:51 CEST

Assignee: dmorganec => bugsquad

Comment 3 Manuel Hiebel 2013-10-22 12:21:07 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 4 Manuel Hiebel 2013-11-23 16:16:37 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


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