Subject: | |
From: | |
Reply To: | ~Stack~ |
Date: | Mon, 16 Jul 2018 16:49:47 -0500 |
Content-Type: | multipart/signed |
Parts/Attachments: |
|
|
On 07/12/2018 05:34 PM, Akemi Yagi wrote:
> On Thu, Jul 12, 2018 at 3:04 PM, Akemi Yagi <[log in to unmask]> wrote:
>> On Thu, Jul 12, 2018 at 11:19 AM, Jesse Bren <[log in to unmask]> wrote:
>>> I've reports of the same, have not yet had a chance to test a rollback of
>>> firefox.
>>>
>>> Mozilla Firefox 60.1.0
>>>
>>> /var/log/messages at time of crash:
>>> Jul 12 13:15:51 hydra kernel: firefox[58474] trap int3 ip:7fd8e93eb5bf
>>> sp:7ffe5c4556a0 error:0
>>> Jul 12 13:15:51 hydra kernel: Chrome_~dThread[58622]: segfault at 0 ip
>>> 00007f53afa4cf9d sp 00007f53ad1eeaf0 error 6 in
>>> libxul.so[7f53af561000+532a000]
>>> Jul 12 13:15:51 hydra kernel: Chrome_~dThread[58700]: segfault at 0 ip
>>> 00007f593d24cf9d sp 00007f593a9eeaf0 error 6 in
>>> libxul.so[7f593cd61000+532a000]
>>> Jul 12 13:15:51 hydra kernel: Chrome_~dThread[58728]: segfault at 0 ip
>>> 00007fd05fe4cf9d sp 00007fd05d5eeaf0 error 6 in
>>> libxul.so[7fd05f961000+532a000]
>>>
>>> kernel version info:
>>> Linux hydra 2.6.32-754.2.1.el6.x86_64 #1 SMP Tue Jul 10 13:23:59 CDT 2018
>>> x86_64 x86_64 x86_64 GNU/Linux
>>
>>> On Wed, Jul 11, 2018 at 7:46 PM Franchisseur Robert <[log in to unmask]>
>>> wrote:
>
>> Maybe this upstream bug:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugzilla.redhat.com_show-5Fbug.cgi-3Fid-3D1596852&d=DwIBaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=X9unDwqvB-8suHJh2rQJ3FtCUONoQQfYfTeRgWDQnMc&s=S8y5nL-c9ztjpJV3nj8D2U7X9Xd8R1zGo1nbn-ktWBw&e=
>>
>> Akemi
>
> I confirm that the patch provided in the above RHBZ fixes the problem.
> In short, open /usr/bin/firefox and change the last line:
>
> exec $MOZ_LAUNCHER $script_args $MOZ_PROGRAM "$@"
>
> to
>
> exec env XDG_DATA_DIRS="$MOZ_LIB_DIR/firefox/bundled/share"
> $MOZ_LAUNCHER $script_args $MOZ_PROGRAM "$@"
> (note this is one line)
>
> Akemi
Thanks for posting this. Just had users report this issue to me today.
The fix worked for me. :-)
~Stack~
|
|
|