On 10/1/22 18:33, SlackerNET UK wrote:
....that makes sense. The D-bus bus system is very complex to me.
Question: What's the webkitfix.conf file content?

On Sat, Oct 1, 2022 at 6:37 PM Charadon via SlackBuilds-users <slackbuilds-users@slackbuilds.org <mailto:slackbuilds-users@slackbuilds.org>> wrote:

    On 10/1/22 13:30, Dave W. wrote:
     > On 01/10/22 13:21,
     > Charadon via SlackBuilds-users <slackbuilds-users@slackbuilds.org
    <mailto:slackbuilds-users@slackbuilds.org>> put forth the proposition:
     >> On 10/1/22 11:19, SlackerNET UK wrote:
     >>> I am working in a little group of people to provide GNOME 43 for
     >>> Slackware current and Slackware 15.0.
     >>> I didn't change the session.conf and org.gnome.Epiphany.desktop
    file. I
     >>> just created two files in /etc/profiles.d.
     >>> epiphany.sh
     >>>
     >>> #!/bin/sh
     >>> export  WEBKIT_FORCE_SANDBOX=0  export  GIGACAGE_ENABLED=0  export
     >>> G_SLICE=always-malloc
     >>> export  Malloc=1
     >>>
     >>> epiphany.csh
     >>>
     >>> #!/bin/csh
     >>> setenvWEBKIT_FORCE_SANDBOX=0  setenvGIGACAGE_ENABLED=0
     >>> setenvG_SLICE=always-malloc
     >>> setenvMalloc=1
     >>>
     >>>
     >>>
     >>>
     >>>
     >>> On Sat, Oct 1, 2022 at 2:13 PM Charadon via SlackBuilds-users
     >>> <slackbuilds-users@slackbuilds.org
    <mailto:slackbuilds-users@slackbuilds.org>
     >>> <mailto:slackbuilds-users@slackbuilds.org
    <mailto:slackbuilds-users@slackbuilds.org>>> wrote:
     >>>
     >>>      Hey all,
     >>>
     >>>      If it's alright with everyone, I want to patch the
    .desktop file for
     >>>      the
     >>>      Epiphany Browser to add the environment variable Malloc=1.
    It fixes a
     >>>      lot of web page crashes that are related to
    xdg-desktop-portal crashing
     >>>      constantly while using it.
     >>>
     >>>      ~ Charadon
     >>>      _______________________________________________
     >>>      SlackBuilds-users mailing list
     >>> SlackBuilds-users@slackbuilds.org
    <mailto:SlackBuilds-users@slackbuilds.org>
     >>>      <mailto:SlackBuilds-users@slackbuilds.org
    <mailto:SlackBuilds-users@slackbuilds.org>>
     >>>
    https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
    <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>>> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
    <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
     >>>      Archives -
     >>> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
    <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>>> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/
    <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
     >>>      FAQ - https://slackbuilds.org/faq/
    <https://slackbuilds.org/faq/> <https://slackbuilds.org/faq/
    <https://slackbuilds.org/faq/>>
     >>>
     >>>
     >>>
     >> Hmm, but would the WEBKIT_FORCE_SANDBOX=0 not make the browser
    less secure?
     >> Or does it mean something else than what I think (sandboxing
    tabs and all
     >> that)
     >
     > It also means that the file would need to be sourced first.
     >
     > IMO the .desktop patch idea is much easier to implement and, as you
     > said, safer too.
     >
     > --
     > Dave
     >
     > sbo-maintainer-tools (sbolint, sbopkglint):
     >
    https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
    <https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/>
     >
     > SBo templates:
     > https://slackbuilds.org/templates/
    <https://slackbuilds.org/templates/>
     >
     > How to format github downloads:
     > https://slackbuilds.org/GITHUB_URLs.txt
    <https://slackbuilds.org/GITHUB_URLs.txt>
     > _______________________________________________
     > SlackBuilds-users mailing list
     > SlackBuilds-users@slackbuilds.org
    <mailto:SlackBuilds-users@slackbuilds.org>
     > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
    <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
     > Archives -
    https://lists.slackbuilds.org/pipermail/slackbuilds-users/
    <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
     > FAQ - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>

    I do know that WEBKIT_FORCE_SANDBOX=0 is required without adding the
    dbus session config.

    Anyways, when libportal updates, which is required for Epiphany 43.
    I'll
    need to modify the desktop file to change

    exec=epiphany
    to
    exec=env Malloc=1 epiphany

    and, i'll need to include a dbus session config that'll go into
    /etc/dbus-1/session.d/webkitfix.conf
    _______________________________________________
    SlackBuilds-users mailing list
    SlackBuilds-users@slackbuilds.org
    <mailto:SlackBuilds-users@slackbuilds.org>
    https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
    <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
    Archives -
    https://lists.slackbuilds.org/pipermail/slackbuilds-users/
    <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
    FAQ - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>


_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


webkitfix.conf:
<!--
This fixes an issue, where webkit can't use abstract sockets.
-->
<busconfig>
        <listen>unix:dir=/tmp</listen>
</busconfig>
--------------------------------------------
Is all that's in there. It doesn't even get rid of the old directive to use an abstract socket. It just makes programs tries to use the non-abstract one, and use the abstract socket as a fallback.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to