Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Firefox password fields and file URLs broken by multiprocess setting
Date: Tue, 23 Jul 2019 11:16:35 +0200	[thread overview]
Message-ID: <20190723091635.2IGSoxukPdEeD28hdwXdWo7Uz7pwUAxFqquCq646lDs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12885@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 447 bytes --]

New comment by jnbr on void-packages repository

https://github.com/void-linux/void-packages/issues/12885#issuecomment-514126336
Comment:
Shared memory shouldn't be an issue according to these numbers.
The graphics stack is identical to mine, so this doesn't seem to be the case either.

I'm not sure on how to debug this. I will push the update for firefox-68.0.1 later today, I don't expect it to fix your issues but it might be worth a try.

  parent reply	other threads:[~2019-07-23  9:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07 14:18 [ISSUE] Firefox password fields broken by IBus voidlinux-github
2019-07-18  2:15 ` Firefox password fields broken voidlinux-github
2019-07-19 22:41 ` Firefox password fields and file URLs broken by multiprocess setting voidlinux-github
2019-07-19 23:38 ` voidlinux-github
2019-07-20  0:01 ` voidlinux-github
2019-07-20  0:03 ` voidlinux-github
2019-07-20  0:06 ` voidlinux-github
2019-07-20  0:06 ` voidlinux-github
2019-07-20  0:08 ` voidlinux-github
2019-07-20  0:31 ` voidlinux-github
2019-07-20  0:33 ` voidlinux-github
2019-07-20  0:36 ` voidlinux-github
2019-07-20  0:37 ` voidlinux-github
2019-07-20  0:45 ` voidlinux-github
2019-07-20 10:12 ` voidlinux-github
2019-07-20 13:51 ` voidlinux-github
2019-07-20 13:52 ` voidlinux-github
2019-07-20 15:59 ` voidlinux-github
2019-07-20 16:43 ` voidlinux-github
2019-07-20 17:28 ` voidlinux-github
2019-07-20 17:28 ` voidlinux-github
2019-07-21 22:40 ` voidlinux-github
2019-07-21 23:36 ` voidlinux-github
2019-07-22  0:16 ` voidlinux-github
2019-07-22  0:36 ` voidlinux-github
2019-07-23  9:16 ` voidlinux-github [this message]
2019-07-25 18:27 ` voidlinux-github
2019-07-30 13:29 ` voidlinux-github
2019-07-30 13:43 ` voidlinux-github
2019-07-30 13:59 ` voidlinux-github
2019-09-20 22:03 ` voidlinux-github
2019-09-28  2:28 ` voidlinux-github
2019-10-21  2:09 ` voidlinux-github
2020-01-12 18:30 ` voidlinux-github
2020-01-25 21:05 ` voidlinux-github
2020-04-12 20:10 ` zeliklil
2020-04-13  7:42 ` svenper
2020-04-21 20:36 ` [ISSUE] [CLOSED] " jnbr
2020-04-21 20:36 ` jnbr
2020-04-21 20:56 ` svenper
2020-04-22  7:17 ` PureTryOut
2020-04-22  8:58 ` svenper
2020-04-22  9:56 ` PureTryOut
2020-04-22 10:49 ` svenper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190723091635.2IGSoxukPdEeD28hdwXdWo7Uz7pwUAxFqquCq646lDs@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).