https://bugs.winehq.org/show_bug.cgi?id=49840
Bug ID: 49840 Summary: chromium fails to load (--no-sandbox is a workaround) Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dark.shadow4@web.de Distribution: ---
Linking old version of chromium, since the newer versions have issues with d3d as well. Download: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.ht...
As noted, the sandbox errors and no page loads.
The latest working wine version is wine-staging-5.4. This could either be a syscall issue again, since the patchset was changed a lot during integration into Wine - or maybe it's an unrelated regression.
https://bugs.winehq.org/show_bug.cgi?id=49840
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Summary|chromium fails to load |chromium 32bit fails to |(--no-sandbox is a |load (--no-sandbox is a |workaround) |workaround) URL| |https://commondatastorage.g | |oogleapis.com/chromium-brow | |ser-snapshots/index.html?pr | |efix=Win/580746/
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Note: This bugreport is only about chromium 32bit, not (google) chrome nor CEF.
https://bugs.winehq.org/show_bug.cgi?id=49840
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com Regression SHA1| |6b498d98a86b5179a025afbaaea | |a3d60a8bd74ec
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- I did a bisect between wine-staging-5.4 and wine-staging-5.5:
commit 6b498d98a86b5179a025afbaaeaa3d60a8bd74ec Author: Zebediah Figura z.figura12@gmail.com Date: Fri Mar 20 12:15:25 2020 -0500
ntdll: Consider mount points to be reparse points in get_file_info().
Signed-off-by: Zebediah Figura zfigura@codeweavers.com Signed-off-by: Alexandre Julliard julliard@winehq.org
@Zebediah Figura Would you mind taking a look at that?
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #3 from Fabian Maurer dark.shadow4@web.de --- Created attachment 68180 --> https://bugs.winehq.org/attachment.cgi?id=68180 Patch to revert the commit and fix the issue
The commit in question does not revert cleanly, attaching an edited revert-version.
Reverting the commit that way makes chromium work fine again. This issue has nothing to do with syscall.
https://bugs.winehq.org/show_bug.cgi?id=49840
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=49840
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=49840
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |ntdll
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #4 from Zebediah Figura z.figura12@gmail.com --- 32-bit chromium seems to work fine for me with upstream Wine, after working around bug 44985 and bug 32342. That's after downloading "chrome-win32.zip", running "chrome.exe", and visiting winehq.org.
Can you confirm whether this is fixed, or perhaps there's a difference in setup? In particular, given the regression hash, it might make a difference if you're running from a separate file system.
hazel@watership:~/Downloads$ sha1sum Win_580746_chrome-win32.zip 5d7f28aaa294b1a439fdb8fea414dad5f61116a1 Win_580746_chrome-win32.zip
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- Good point. It works for me as well when run from .wine. But usually I run wine programs from my Ramdisk (/tmp/ramdisk/) which is a tmpfs, and that's where the issue appears again.
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #6 from Zebediah Figura z.figura12@gmail.com --- I checked Windows, and it fails in a similar manner there when run from a mounted folder. I think this is a WONTFIX.
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #7 from Fabian Maurer dark.shadow4@web.de --- (In reply to Zebediah Figura from comment #6)
I checked Windows, and it fails in a similar manner there when run from a mounted folder.
What exactly do you mean by "mounted folder"? I tried running chromium from "E:" on my windows install, and it works fine. But that won't work on wine, because of that regression. Linux does not have the concept of drive letter, still I'd expect the "Z:" drive in Wine to work properly.
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #8 from Zebediah Figura z.figura12@gmail.com --- Win32 volumes can be mounted to folders other than drive letters; this can be done from diskmgmt.msc. The attached patch, in a manner of speaking, maps Unix mount points to Win32 mounted folders, because the concepts match up quite nicely.
It is not particularly surprising that Windows programs don't account for mounted folders; it seems they are quite a little-known feature. On the other hand, simply ignoring filesystem boundaries doesn't particularly help us; one example of this is bug 38114.
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #9 from Fabian Maurer dark.shadow4@web.de --- And aren't files under dosdevices/z:/ not mapped to Z:\ inside Wine? Because that should work, no?
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- In general, yes, and the general case works for me. /tmp/, however, is a separate file system (generally of type tmpfs).
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #11 from Fabian Maurer dark.shadow4@web.de --- Ah, that's what you mean. I can confirm it works in /var/cache/ (directly on root) but not on /home/fabian/. Presumably because that is mounted into / as well. Is that how things should be? I'd hope it atleast works for my home folder...
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #12 from Zebediah Figura z.figura12@gmail.com --- I'm not entirely sure what you mean; but I'd guess it fails because /home is a separate file system?
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #13 from Fabian Maurer dark.shadow4@web.de --- Yes, my /home is a different filesystem from / So this is a works-as-intended?
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #14 from Zebediah Figura z.figura12@gmail.com --- As far as I can tell, yes. It's a bit unfortunate, but I don't see any good way to work around it in Wine.
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #15 from Fabian Maurer dark.shadow4@web.de --- Alrighty then, feel free to close.
https://bugs.winehq.org/show_bug.cgi?id=49840
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED
--- Comment #16 from Zebediah Figura z.figura12@gmail.com --- Resolving WONTFIX.
https://bugs.winehq.org/show_bug.cgi?id=49840
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #17 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
What are the files that need not be on a mount point for chromium to work? The whole wineprefix, only chromium itself, or other?
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49840
--- Comment #18 from Zebediah Figura z.figura12@gmail.com --- At least the executable itself apparently can't be inside a separate mount point. That said, I suspect (though haven't tested) that things *will* just work if you manually assign a drive letter to the root of the mounted drive, or to any subdirectory thereof; for example, putting Chromium anywhere inside drive_c will work even if drive_c resides on a different file system than the root.
https://bugs.winehq.org/show_bug.cgi?id=49840
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #19 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=49840
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #20 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=49840
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #21 from Gijs Vermeulen gijsvrm@gmail.com --- Closing WONTFIX.