[Bug 50198] New: SHMEM_FAILURE on Blizzard products on FAT32

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50198

            Bug ID: 50198
           Summary: SHMEM_FAILURE on Blizzard products on FAT32
           Product: Wine-staging
           Version: 5.17
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: blc+wine at mail.vanade.com
                CC: leslie_alistair at hotmail.com, z.figura12 at gmail.com
      Distribution: ---

Created attachment 68712
  --> https://bugs.winehq.org/attachment.cgi?id=68712
Battle.net application log showing failure near end.

I noticed that WoW and Battle.net applications have stopped working properly
when running off of FAT32 formatted partitions in Linux.  The application
logfiles seem to indicate that the software was unable to create and access
shared memory files which had been working in the past, at least with older
versions of Wine.

Attached is from battle.net application when it's trying to update WoW.  WoW
also gives an apparently similar error when it tries top open the CAS
datafiles.

I had not upgraded the kernel so supposedly shared memory files that worked in
the past on FAT32 should still work.  I don't know if this was a deliberate
change because of security issues where anyone can open files on FAT32 and thus
invade shared memory.

Windows 7 does not exhibit this problem on the same disk and Battle.net updates
fine.

As this is on a limited space SSD, I don't have enough disk space to try this
on ext4fs to see if the problem goes away or not.  I do have another machine
that does not exhibit this problem on ext4fs.  The WoW installation is on FAT32
so I could easily test on Windows 7 with limited disk space.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.