[Bug 38667] New: DAZ3D 4.8 cant start it's private Postgres as it sees Wine accounts as admin. Note line 18269. NtReadFile, NtWrfile (privilege check kluge) or NtQueryTokenProcess are cause. Want to downgrade privilege for groupname 'postgres' only. Where shall I patch?

wine-bugs at winehq.org wine-bugs at winehq.org
Tue Jun 2 01:39:14 CDT 2015


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

            Bug ID: 38667
           Summary: DAZ3D 4.8 cant start it's private Postgres as it sees
                    Wine accounts as admin. Note line 18269.
                    NtReadFile,NtWrfile (privilege check kluge) or
                    NtQueryTokenProcess are cause.  Want to downgrade
                    privilege for groupname 'postgres' only. Where shall I
                    patch?
           Product: Wine
           Version: 1.7.44
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: ntdll
          Assignee: wine-bugs at winehq.org
          Reporter: eternalsquire at hotmail.com
      Distribution: ---

I rebuilt latest WINE 1.77.44 on ThinkPad laptop running on 32-bit Anti-X
Version 5 Beta 2.

DAZ3D 4.8 (PRO free limited time beta) cant start it's private Postgres as it
sees Wine accounts as admin. Note line 18269.  NtReadFile,NtWrfile (privilege
check kluge) or NtQueryTokenProcess are cause.  Like to downgrade privilege for
username 'postgres' only. Where shall I patch?

If I can fix this with your help, DAZ3D free promotions will be instant
Platinum.  They're Gold already but for the Postrgres, but it has a backup
obsolete database so COULD do without, but even as a hack distribution I could
make more people than you can ever know very happy, including myself. happy.

I saw the existing reports on Administrative privilege problems.  I know you
believe having all processes running as Admin from WINE for simplicity, but
Postgres is the one product justifying an exception, and that goes double when
DAZ3D built it proprietary without source.  WINE has to give way here because
no one else will.

I won't ask you to find and fix the bug.  I just need some of your expertise on
WINE (no internal software documentation!!!) knowing what to look for and
zooming in on the root cause, or worst case, put in a root kluge.  I'm a
retired software designer and systems programmer.

-- 
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.



More information about the wine-bugs mailing list