From: svenper <svenper@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Firefox file directories broken by multiprocess setting
Date: Wed, 22 Apr 2020 13:23:11 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21245@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
New issue by svenper on void-packages repository
https://github.com/void-linux/void-packages/issues/21245
Description:
(split off from #12885 since the separate password field bug was fixed)
# System
* xuname:
Void 5.4.33_2 x86_64-musl GenuineIntel uptodate hold rrnFFFFFFFFF
* package:
firefox-75.0_1
### Expected behavior
file listing views are broken by dconf
### Actual behavior
file listing views are not broken by dconf
### Steps to reproduce the behavior
navigate to `file:///` or `ftp://*` (e.g. ftp://ftp.fr.debian.org/debian/)
next reply other threads:[~2020-04-22 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 11:23 svenper [this message]
2020-04-22 18:11 ` Firefox directory list views broken by multiprocess setting or dconf jnbr
2020-04-27 16:45 ` jnbr
2020-04-27 17:09 ` svenper
2020-04-27 17:13 ` jnbr
2020-05-02 8:35 ` [ISSUE] [CLOSED] " jnbr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21245@inbox.vuxu.org \
--to=svenper@users.noreply.github.com \
--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).