maintainer-feedback requested: [Bug 258679] www/chromium: Unable to download files with chromium-92.0.4515.159_2

From: <>
Date: Wed, 22 Sep 2021 15:30:28 UTC
Bugzilla Automation <> has asked freebsd-chromium (Nobody)
<> for maintainer-feedback:
Bug 258679: www/chromium: Unable to download files with

--- Description ---
On chromium-92.0.4515.159_2 I am unable to download files to alternate
directories if they are on different filesystems.

I can download to ~/Downloads which is inside my home directory on the same
disk, but not to a different directory I have on another ZFS dataset. This
worked previously until the most recent major version of Chromium (92.x).
Permissions are correct and my user can create files in the target without

It's simple to reproduce by going to and attempting a download of a
FreeBSD installer image. If I download to ~/Downloads it succeeds but if I
attempt to place it into the directory I export to hypervisors (/data/apps/OS)
it fails. The browser displays "Failed - Download Error" but does not log
anything on the console or stderr. The browser leaves an empty file ending in
".crdownload" behind when it fails.

If I go to chrome://downloads/ and click "Resume" on the failed entry it may
randomly work. Sometimes it works on a single retry sometimes it takes 10 or
more tries before it succeeds. Each failed attempt results in a new empty
".crdownload" file

This happens in regular mode and in incognito mode. The problem also persists
even if I set the main Download folder to the desired target location.

System is on 13.0 with all available updates applied.

FreeBSD <blah> 13.0-RELEASE-p4 FreeBSD 13.0-RELEASE-p4 #0: Tue Aug 24 07:33:27
UTC 2021 

This is not the same issue as bug #258232 as my dbus machine ID is present and

As a temporary workaround I can download files to my home dir and move them but
it's a weird and arbitrary limitation that has not been present in the past,
and it gets more irritating each time I have to take the extra steps that were
unnecessary before.

There are others reporting similar issues on the -stable mailing list and in
the comments on closed bug #25832