[Bug 40613] New: WhatsApp Desktop application not working
https://bugs.winehq.org/show_bug.cgi?id=40613 Bug ID: 40613 Summary: WhatsApp Desktop application not working Product: Wine Version: 1.9.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: sh.yaron(a)gmail.com Distribution: --- Created attachment 54470 --> https://bugs.winehq.org/attachment.cgi?id=54470 Stack trace as appears on cli WhatsApp for Windows Desktop was released and I tried to install it. Apparently it requires Windows 8 and greater, I've set it correctly in Winecfg. Trying to run the WhatsApp installation (ver 0.2.684) renders the error in the attached file. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox_xerox2000(a)yahoo.co.uk --- Comment #1 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> --- Hoi , i tried this app but got a slightly different backtrace. Anyway, there is a bug. Could you try the hack below? It gets me a bit further, where it complains about .net not installed. After installing .net (winetricks dotnet452) i get a GUI up, but shortly after it crashes : err:process:create_process L"C:\\users\\louis\\Local Settings\\Application Data\\WhatsApp\\app-0.2.684\\WhatsApp.exe" not supported on this installation (x86_64 binary) Apperently it`s a x86_64-binary, so i cannot test any further as i have 32-bit wine. hack: diff --git a/dlls/ntdll/nt.c b/dlls/ntdll/nt.c index 47d7b31..2ad44dd 100644 --- a/dlls/ntdll/nt.c +++ b/dlls/ntdll/nt.c @@ -504,7 +504,7 @@ NTSTATUS WINAPI NtQueryInformationToken( { TOKEN_ELEVATION_TYPE *elevation_type = tokeninfo; FIXME("QueryInformationToken( ..., TokenElevationType, ...) semi-stub\n"); - *elevation_type = TokenElevationTypeFull; + *elevation_type = TokenElevationTypeDefault;//TokenElevationTypeFull; } break; case TokenElevation: -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #2 from Yaron Shahrabani <sh.yaron(a)gmail.com> --- I can't compile on this thing, lets see if someone else will assist us. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Michael Müller <michael(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael(a)fds-team.de --- Comment #3 from Michael Müller <michael(a)fds-team.de> --- Louis is correct about the cause of the problem. WhatsApp stops the installation if you run the installer with administrator rights. The installer also tries to explain this: 0042:Call KERNEL32.lstrlenW(00423cd0 L"Please re-run this installer as a normal user instead of \"Run as Administrator\".") ret=0040253e which is most probably not shown because of the incomplete implementation of TaskDialogIndirect (see bug 34850). There is not much we can do about this now. Changing the value will break a lot of other applications which would need administrator rights for the installation. The correct way to solve this would require implementing something like UAC in Wine. If you really need to use WhatsApp in Wine: 1. Apply Louis NtQueryInformationToken hack 2. Install .NET (winetricks dotnet452) 3. Start the WhatsApp installer and let it crash (The installer executes a .NET application which will not work in Wine with windows version set >= XP, .NET tries to use uiautomationcore.dll on newer versions.) 4. Set the windows version back to XP. 5. Install the 2010 and 2013 VC runtime (winetricks vcrun2013 vcrun2010) 6. Create a copy of msvcr100.dll and name it msvcr100_clr0400.dll in system32 7. Go to drive_c/users/$USER/Local Settings/Application Data/WhatsApp/app-0.2.684 8. Run WhatsApp.exe --squirrel-install 0.2.684 Now you can run WhatsApp.exe without parameters and it should work. I didn't check what point 8 does, but it is what the original installer intended to do. @Louis: There is a 32 and 64 bit download available and the 32 bit version works in a 32 bit only prefix, so I guess you downloaded the wrong version. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #4 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> --- Hi Michael, thanks for info and howto. Your comment reminded me that app Smartflix https://bugs.winehq.org/show_bug.cgi?id=39986 suffers apparently from exactly the same bug (at least the installer). So probably a duplicate bug of this one -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thierry.salmon(a)gmail.com --- Comment #5 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> --- *** Bug 39986 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Summary|WhatsApp Desktop |WhatsApp Desktop, Smartflix |application not working |installers don`t run | |(Please re-run this | |installer as a normal user | |instead of Run as | |Administrator) Ever confirmed|0 |1 --- Comment #6 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> --- changed title and confirming -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=41925 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=39262 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|WhatsApp Desktop, Smartflix |WhatsApp Desktop, Smartflix |installers don`t run |(Squirrel Installers) don`t |(Please re-run this |run (Please re-run this |installer as a normal user |installer as a normal user |instead of Run as |instead of Run as |Administrator) |Administrator) --- Comment #7 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> --- Added ``Squirrel`` to summary to collect similar bugs -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #8 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> --- Spotify has the same problem. Maybe as a hack we could add a registrykey that if present returns the TokenElevationTypeDefault? Would that be acceptable in Staging? Sidenote: I now have a Spotify account and apart from this installer-issue, it seems to run quite fine in Staging -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Staged patchset| |https://github.com/wine-com | |pholio/wine-staging/tree/ma | |ster/patches/advapi32-Token | |_Integrity_Level CC| |dmitry(a)baikal.ru, | |erich.e.hoover(a)wine-staging | |.com, sebastian(a)fds-team.de Status|NEW |STAGED -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #9 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Louis Lenders from comment #8)
Maybe as a hack we could add a registrykey that if present returns the TokenElevationTypeDefault? Would that be acceptable in Staging?
Michael Müller has been working on a more complete solution, which has been added in Wine Staging 2.14. This is basically a full UAC implementation including token inheritance and official ways to elevate rights / drop privileges. The main differences compared to Windows are that (1) there are no confirmation dialogs yet and (2) admin privileges are still default for backwards compatibility. To start a installer with limited privileges, you can use: wine runas /trustlevel:0x20000 installer.exe Does this fix the issue with Spotify? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #10 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> ---
To start a installer with limited privileges, you can use:
wine runas /trustlevel:0x20000 installer.exe
Does this fix the issue with Spotify?
Hi Sebastian, The installer starts now with wine-Staging 2.14 with the commandline given above. Nice job! However there`s one annoyance: I first tried to start the installer from another directory than where it resides (I was in my home directory and tried to start the installer that was in directory Downloads: /opt/wine-staging/bin/wine runas /trustlevel:0x20000 ~/Downloads/SpotifyFullSetup\.exe) This doesn`t work: /opt/wine-staging/bin/wine runas /trustlevel:0x20000 ~/Downloads/SpotifyFullSetup.exe fixme:winediag:start_process Wine Staging 2.14 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. fixme:runas:parse_command_line Ignoring parameter L"/home/louis/Downloads/SpotifyFullSetup(1).exe" Usage of RUNAS: RUNAS /trustlevel:<trustlevel> program /showtrustlevels Show possible trustlevels /trustlevel <trustlevel> should be listed in /showtrustlevels program Program to start The installer doesn`t start. Maybe the switches are not parsed correctly? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 danqi <danqi(a)iscas.ac.cn> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danqi(a)iscas.ac.cn --- Comment #11 from danqi <danqi(a)iscas.ac.cn> --- (In reply to Michael Müller from comment #3)
Louis is correct about the cause of the problem. WhatsApp stops the installation if you run the installer with administrator rights. The installer also tries to explain this:
0042:Call KERNEL32.lstrlenW(00423cd0 L"Please re-run this installer as a normal user instead of \"Run as Administrator\".") ret=0040253e
which is most probably not shown because of the incomplete implementation of TaskDialogIndirect (see bug 34850).
There is not much we can do about this now. Changing the value will break a lot of other applications which would need administrator rights for the installation. The correct way to solve this would require implementing something like UAC in Wine.
Hi Michael, I am confused about why WhatsApp can be installed by normal user but can't be installed by Administrator? I think Administrator have more privilege to install application. And I don't understand why most application can be installed by Administrator just this application can be installed by normal user? What's the different between WhatsApp and other applications? Does this bug message(0042:Call KERNEL32.lstrlenW(00423cd0 L"Please re-run this installer as a normal user instead of \"Run as Administrator\".") ret=0040253e) is the primary reason cause WhatsApp crashed？ I hope to receive your favors at early date. Thanks very much. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #12 from Nikolay Sivov <bunglehead(a)gmail.com> --- Some applications/installers specifically check if your ran them under Admin user account, and stop, as a security measure for example or some other reasons. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Robert Walker <bob.mt.wya(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Danil <dannevergame(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dannevergame(a)gmail.com --- Comment #13 from Danil <dannevergame(a)gmail.com> --- Created attachment 59619 --> https://bugs.winehq.org/attachment.cgi?id=59619 Backtrace of running whatsapp setup using `runas` Backtrace of running whatsapp setup using `runas` -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #14 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Danil from comment #13)
Created attachment 59619 [details] Backtrace of running whatsapp setup using `runas`
You have to install native dotnet to be able to run these apps like Whatsapp. ``winetricks dotnet462`` should do the trick I guess -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikhail.v.gavrilov(a)gmail.co | |m --- Comment #15 from Fabian Maurer <dark.shadow4(a)web.de> --- *** Bug 44090 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Chris.Samberg(a)Gmail.com --- Comment #16 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- *** Bug 44323 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.whatsapp.com/do | |wnload/?l=en Keywords| |download, Installer CC| |focht(a)gmx.net -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kazidozaf(a)lucyu.com --- Comment #17 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- *** Bug 43227 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jebeld17(a)gmail.com --- Comment #18 from Anastasius Focht <focht(a)gmx.net> --- *** Bug 44535 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Staged patchset|https://github.com/wine-com |https://github.com/wine-sta |pholio/wine-staging/tree/ma |ging/wine-staging/tree/mast |ster/patches/advapi32-Token |er/patches/advapi32-Token_I |_Integrity_Level |ntegrity_Level Summary|WhatsApp Desktop, Smartflix |Multiple applications |(Squirrel Installers) don`t |require UAC implementation |run (Please re-run this |to run installer/app as a |installer as a normal user |normal user instead of |instead of Run as |administrator (WhatsApp |Administrator) |Desktop, Smartflix, | |Squirrel Installers, | |OneDrive) --- Comment #19 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, obviously still present. Adjusting some fields. @Danil comment #13 - as already said by others: install MS .NET Frameworks 4.5/4.6 using 'winetricks' before running the installer. Wine-Mono is a dead end here. $ sha1sum WhatsAppSetup.exe dbfeb1afbd04c4a59927e2a2673866ed6cde2977 WhatsAppSetup.exe $ du -sh WhatsAppSetup.exe 126M WhatsAppSetup.exe $ wine --version wine-3.9 Regards -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |45780 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rpeccolo(a)pratura.io --- Comment #20 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- *** Bug 45780 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 tim110011(a)163.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tim110011(a)163.com --- Comment #21 from tim110011(a)163.com --- RUNAS don't work with start /d The folling command just show runas usage wine runas /trustlevel:0x20000 start /d 'D:\' dzclient-1.7.85.exe Usage of RUNAS: RUNAS /trustlevel:<trustlevel> program /showtrustlevels Show possible trustlevels /trustlevel <trustlevel> should be listed in /showtrustlevels program Program to start -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #22 from Anastasius Focht <focht(a)gmx.net> --- Hello tim, --- quote --- RUNAS don't work with start /d ... wine runas /trustlevel:0x20000 start /d 'D:\' dzclient-1.7.85.exe --- quote --- you didn't quote properly hence all parameters after 'start' are interpreted as belonging to 'runas' command. On modern NT-based Windows, 'start' is a builtin of Windows command shell. Wine's external 'start.exe' program is a Win9x legacy and doing more harm than good, especially in WoW64 prefixes. I would even consider removing this - but that will likely break many crappy scripts. Doesn't work in 64-bit WINEPREFIX: --- snip --- $ wine runas /trustlevel:0x20000 "start /d c:\\ notepad" RUNAS-Error: start /d c:\ notepad could not be started 2: File not found. --- snip --- Works in 64-bit WINEPREFIX: --- snip --- $ wine64 runas /trustlevel:0x20000 "start /d c:\\ notepad" --- snip --- I would suggest you use 'start' properly as 'cmd.exe' builtin which avoids the aforementioned issues. --- snip --- $ wine runas /trustlevel:0x20000 "cmd /c start /d c:\\ notepad" --- snip --- In your case it would be: --- snip --- $ wine runas /trustlevel:0x20000 "cmd /c start /d D:\\ dzclient-1.7.85.exe" --- snip --- Regards -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 tinywrkb <tinywrkb(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tinywrkb(a)gmail.com --- Comment #23 from tinywrkb <tinywrkb(a)gmail.com> --- With wine-staging 4.2 and runas StreamJar can be installed. It also needs winetricks' dotnet452 and disabling dx11 or installing dxvk. Download link to latest release: https://cdn.streamjar.tv/packages/bootstrap/stable/win32/2.0.1/StreamJar%20S... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 gloomfairy(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gloomfairy(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #24 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Still present in Staging-5.15 Any chance the Staging patch-set gets re-enabled soon? Regards -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #25 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Louis Lenders from comment #24)
Still present in Staging-5.15
Any chance the Staging patch-set gets re-enabled soon?
I'm not sure what you mean; advapi32-Token_Integrity_Level isn't disabled. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #26 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Zebediah Figura from comment #25)
(In reply to Louis Lenders from comment #24)
I'm not sure what you mean; advapi32-Token_Integrity_Level isn't disabled.
Well, it*** used to work in Staging up to about wine-5.11 (???, this is a guess ) but right now it doesn`t work anywork. I thought a patchset was disabled; if not, then there is some regression ivolved I guess ***: wine runas /trustlevel:0x20000 ./installer.exe -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Eivind Eide <xenofil(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xenofil(a)gmail.com --- Comment #27 from Eivind Eide <xenofil(a)gmail.com> --- Per recommendation I moved to wine-staging to solve my problem. Now running wine-staging 5.15.2-1 on Arch Linux current. The command I wanted to execute was: wine runas /trustlevel:0x20000 ./SpotifySetup.exe However this is not working as advertised, nothing happens except SpotifySetup.exe still throwing the same old error message: "Please install Spotify using a normal account instead of an Administrator account." Is there any way forward from this....? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #28 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Eivind Eide from comment #27)
Per recommendation I moved to wine-staging to solve my problem. Now running wine-staging 5.15.2-1 on Arch Linux current. The command I wanted to execute was: wine runas /trustlevel:0x20000 ./SpotifySetup.exe However this is not working as advertised, nothing happens except SpotifySetup.exe still throwing the same old error message: "Please install Spotify using a normal account instead of an Administrator account." Is there any way forward from this....?
For now I fell back to stupid hack from comment1 https://bugs.winehq.org/show_bug.cgi?id=40613#c1 i don`t know how to do a "wine-staging regression test", but atm word "Staged" is not valid... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #29 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- *** Bug 44439 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #30 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- *** Bug 49430 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Eliyahu Orzitzer <e_orz(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |e_orz(a)yahoo.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 quentin grimaud <quentin.grimaud(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |quentin.grimaud(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #31 from Erich E. Hoover <erich.e.hoover(a)gmail.com> --- (In reply to Louis Lenders from comment #28)
... i don`t know how to do a "wine-staging regression test", but atm word "Staged" is not valid...
1) Find the major version where things go from working to broken, since this saves a lot of time and effort narrowing in. 2) Once you have the major versions involved the easiest thing to do is to check out Wine for the working version and apply all of the staging patches to it and confirm that that still works (no issues from being compiled differently). 3) Export all the patches in mbox format so that they are easy to add and remove 4) Reset to the working major version and start a bisect between the working and broken versions 5) At each step along the bisect apply the mbox patches (rework them if necessary), test, and then unapply them (git bisect [good|bad] doesn't work on a modified tree) 6) Once you have found the "broken" Wine commit then try to determine if the problem is related to the Wine commit or an unintentional/rebase change in a Wine-Staging commit. Usually it's pretty obvious if it's a rebase problem because the "broken" commit touches some code that you had to rework to get the Wine-Staging patches to apply. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #32 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Erich E. Hoover from comment #31)
(In reply to Louis Lenders from comment #28)
... i don`t know how to do a "wine-staging regression test", but atm word "Staged" is not valid...
1) Find the major version where things go from working to broken, since this saves a lot of time and effort narrowing in.
Hi Erich, thanks for the info; though it looks like last nights rebase fixed the regression as far as i can see. Anyone can confirm? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 david.sitsky+bugzilla(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.sitsky+bugzilla(a)gmail | |.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #33 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Louis Lenders from comment #32)
it looks like last nights rebase fixed the regression as far as i can see. Anyone can confirm?
Uuuh, I was too optimistic, it think I had hack from comment 2 applied. The bug is actually still present in current Staging.... Tested SpotifySetup. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Ikky <mimajeri(a)163.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mimajeri(a)163.com --- Comment #34 from Ikky <mimajeri(a)163.com> --- *** Bug 50186 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #35 from Ikky <mimajeri(a)163.com> --- Did we remove the runas from winehq-staging 5.22? I get the following error stating that runas.exe was not found: $ wine runas /trustlevel:0x20000 ~/Downloads/OneDriveSetup.exe 002c:fixme:winediag:LdrInitializeThunk wine-staging 5.22 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0024:err:module:process_init L"C:\\windows\\system32\\runas.exe" not found $ wine --version wine-5.22 (Staging) $ ls .wine32/drive_c/windows/system32/runas.exe ls: cannot access '.wine32/drive_c/windows/system32/runas.exe': No such file or directory $ ls .wine/drive_c/windows/system32/runas.exe ls: cannot access '.wine/drive_c/windows/system32/runas.exe': No such file or directory If yes, how can I add it back, or which latest version of winehq-staging shall I use that has runas.exe still included? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #36 from Zebediah Figura <z.figura12(a)gmail.com> --- It's been broken and disabled for a while; I believe the latest version that still includes it is wine-staging 5.15.2. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Robert Wilhelm <sloper42(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sloper42(a)yahoo.com --- Comment #37 from Robert Wilhelm <sloper42(a)yahoo.com> --- (In reply to Louis Lenders from comment #1) This hack still works. Please note location has changed after port to PE: diff --git a/dlls/ntdll/unix/security.c b/dlls/ntdll/unix/security.c index ad85020d6c0..b5864b411d9 100644 --- a/dlls/ntdll/unix/security.c +++ b/dlls/ntdll/unix/security.c @@ -393,7 +393,7 @@ NTSTATUS WINAPI NtQueryInformationToken( HANDLE token, TOKEN_INFORMATION_CLASS c { TOKEN_ELEVATION_TYPE *type = info; FIXME("QueryInformationToken( ..., TokenElevationType, ...) semi-stub\n"); - *type = TokenElevationTypeFull; + *type = TokenElevationTypeDefault;//TokenElevationTypeFull; } break; -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Staged patchset|https://github.com/wine-sta |https://github.com/wine-sta |ging/wine-staging/tree/mast |ging/wine-staging/tree/mast |er/patches/advapi32-Token_I |er/patches/server-default_i |ntegrity_Level |ntegrity -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |toadfield(a)tutanota.com --- Comment #38 from Zebediah Figura <z.figura12(a)gmail.com> --- *** Bug 50518 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #39 from Eivind Eide <xenofil(a)gmail.com> --- (wine-staging 6.11 on Arch Linux current.) After the patches went in I can now install Spotify with SpotifySetup.exe. However there is a new problem: Trying to update existing foobar2000 1.6.4 to 1.6.6 I get a "run as" dialogue that wants me to log in as Administrator? This is how that looks: https://imgur.com/8Hu2j56 https://imgur.com/TfzB0jd And I can't get past that. I have no password for Administrator and the update just dies... Anybody who can share any information regarding this? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #40 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Eivind Eide from comment #39)
(wine-staging 6.11 on Arch Linux current.) After the patches went in I can now install Spotify with SpotifySetup.exe. However there is a new problem: Trying to update existing foobar2000 1.6.4 to 1.6.6 I get a "run as" dialogue that wants me to log in as Administrator? This is how that looks: https://imgur.com/8Hu2j56 https://imgur.com/TfzB0jd And I can't get past that. I have no password for Administrator and the update just dies... Anybody who can share any information regarding this?
If your prefix was created with upstream wine or with an older version of wine-staging, you'll need to modify the registry manually. Open regedit.exe, find the key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System, and change the value of EnableLUA from 0 to 1. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #41 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Zebediah Figura from comment #40)
(In reply to Eivind Eide from comment #39)
(wine-staging 6.11 on Arch Linux current.) After the patches went in I can now install Spotify with SpotifySetup.exe. However there is a new problem: Trying to update existing foobar2000 1.6.4 to 1.6.6 I get a "run as" dialogue that wants me to log in as Administrator? This is how that looks: https://imgur.com/8Hu2j56 https://imgur.com/TfzB0jd And I can't get past that. I have no password for Administrator and the update just dies... Anybody who can share any information regarding this?
If your prefix was created with upstream wine or with an older version of wine-staging, you'll need to modify the registry manually. Open regedit.exe, find the key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System, and change the value of EnableLUA from 0 to 1.
I've pushed an update to the relevant wine-staging patch that should make this change automatic in the future. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #42 from Eivind Eide <xenofil(a)gmail.com> --- (In reply to Zebediah Figura from comment #40)
If your prefix was created with upstream wine or with an older version of wine-staging, you'll need to modify the registry manually. Open regedit.exe, find the key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System, and change the value of EnableLUA from 0 to 1.
Thanks! That's it. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 gsd <gsd.zak(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gsd.zak(a)gmail.com --- Comment #43 from gsd <gsd.zak(a)gmail.com> --- Hi, I have been following this bug as I am trying to get WeMod (gaming app that uses Squirrel Installer) working on winehq-staging (now 6.12). I successfully installed it a few winehq-staging versions ago, back when the "runas" command still worked, but I had to wipe my prefix since then, so I'm trying to reinstall. EnableLUA is set to 1 in the regedit, and the error to 'please install as normal user' is no longer showing up. However, once the GUI installer finishes its downloading work, it shortly disappears, and the terminal output goes into a loop of errors including: err:virtual:virtual_setup_exception stack overflow fixme:ntdll:NtFilterToken support for restricting sids not yet implemented The app seems to halfway install. Icons are created and a black box shows up when it is launched, but I have to close it with wineserver -k, or else it just hangs there. I have done this a couple of times and manually uninstalled by finding and deleting the relevant files, but I can run it again if you need full cli output. Since WeMod successfully installed and was working before with 'runas', I'm hoping that the problem is related to this bug, but I can look elsewhere if you all would be kind enough to point me in the right direction. Thank you. (FWIW, I had winecfg set to Win7 when WeMod successfully installed/ran, but I have it set to Win10 now, and would like to keep it that way if possible.) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #44 from Zebediah Figura <z.figura12(a)gmail.com> --- I can't reproduce the reported errors with WeMod, in a clean prefix, with wine-staging 6.12. I do get a warning that .NET isn't installed; did you install native .NET beforehand? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #45 from gsd <gsd.zak(a)gmail.com> --- Thank you! Making a clean prefix and installing only .NET (winetricks dotnet48) first worked. To be specific I did some overkill steps since I like to only have one prefix at a time if possible and to be double sure: I uninstalled winehq-staging and all dependencies using apt, used winetricks annihilate to get rid of my current prefix, then reinstalled winehq-staging and ran winetricks dotnet48, then wine WeMod-setup.exe. This worked fine. I had used winetricks dotnet48 in my last prefix, but maybe something else I had installed was gumming up the works. Absolutely worth making a new prefix to get WeMod working again, a program I can't recommend highly enough. Thanks again! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 gsd <gsd.zak(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|gsd.zak(a)gmail.com | -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 gsd <gsd.zak(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gsd.zak(a)gmail.com --- Comment #46 from gsd <gsd.zak(a)gmail.com> --- For anyone with the WeMod problem, it turned out to be a conflict with dxvk. I was able to use both with this trick: If you have neither installed, install WeMod first, then dxvk. If you already have dxvk, run winecfg, then click Libraries and edit the override entries d3d11 and dxgi to 'Builtin then native' and hit apply (don't close winecfg). Now you can install and run WeMod. Think of this as 'WeMod mode'. Once you have WeMod running, change those library overrides back to 'Native'. Think of this as 'game mode'. WeMod should stay open, but now you can run dxvk games, even launch them from WeMod. Whenever you quit WeMod, you will have to switch the library overrides to 'WeMod mode', launch WeMod, then switch them to 'game mode' again, but it's not much trouble really, and it's worth it imo. Sorry if this went too off topic. Thanks again for your help. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 gsd <gsd.zak(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|gsd.zak(a)gmail.com | -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 jorge santos <jorgemtds(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jorgemtds(a)gmail.com --- Comment #47 from jorge santos <jorgemtds(a)gmail.com> --- (In reply to gsd from comment #46) I still can't install WEMOD on STAGING 6.12. With your instructions I was able to install .NET 4.8 but when trying to install WEMOD I get another error that prevents it from installing. If I don0t install .NET 4.8 when trying to install WEMOD I am informed that .NET is not installed. So, it seems to me that my problem must be with the .NET installation. Would you mind trying to make a more complete step by step tutorial on what you've done. I followed everything you've said and I still get that final WEMOD error. I must be missing something else not written down. Thank you. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |AlvinSeville7cf(a)gmail.com --- Comment #48 from Zebediah Figura <z.figura12(a)gmail.com> --- *** Bug 51488 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Thierry Salmon <thierry.salmon(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|thierry.salmon(a)gmail.com | -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 someuniquename(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |someuniquename(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=52280 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Graham Perrin <grahamperrin(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grahamperrin(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Julian Rüger <jr98(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jr98(a)gmx.net -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 soredake <gi85qht0z(a)relay.firefox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gi85qht0z(a)relay.firefox.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 huntantr <huntantr(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |huntantr(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Hamish McIntyre-Bhatty <winehq(a)regd.hamishmb.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq(a)regd.hamishmb.com --- Comment #49 from Hamish McIntyre-Bhatty <winehq(a)regd.hamishmb.com> --- Have we got a timescale for this? There seem to have been patches in WINE-staging for a really long time, but runas still isn't around on WINE-dev. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #50 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Hamish McIntyre-Bhatty from comment #49)
Have we got a timescale for this? There seem to have been patches in WINE-staging for a really long time, but runas still isn't around on WINE-dev.
The plan is to implement this differently, using basically the reverse logic as in the old wine-staging patch set. Programs will be run as a normal user by default, and automatically elevated when requested. I.e. using "runas" should not be necessary anymore. Currently the blocker is at least one program which needs to be manually run as administrator. Annoyingly I can't actually find the bug (maybe it was reported to me privately, or I happened upon it?), but I think the program was Paint Tool Sai. I think we want to do this basically like Windows, by implementing the "run as administrator" menu option in our shell32. Probably we should also add a command-line option, although I don't think we want it to look like runas (which isn't really meant to work that way). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 --- Comment #51 from Hamish McIntyre-Bhatty <winehq(a)regd.hamishmb.com> --- I see, and that makes sense - running as normal user by default matches Windows
XP behaviour anyway IIRC.
Thanks :) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Guilherme Maeda <guimaeda(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guimaeda(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 kaan.batin.tr(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kaan.batin.tr(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 harkamalsr(a)gmail.com <harkamalsr(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harkamalsr(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maiktapwagner(a)aol.com --- Comment #52 from Zeb Figura <z.figura12(a)gmail.com> --- *** Bug 54768 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 demicorn <bugs.winehq.org(a)boson.nom.za> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs.winehq.org(a)boson.nom.z | |a -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|STAGED |RESOLVED Fixed by SHA1| |e92ba2de43d7afbe0704b11b29f | |7c30f44dfaeca Resolution|--- |FIXED --- Comment #53 from Zeb Figura <z.figura12(a)gmail.com> --- Fixed upstream in <https://source.winehq.org/git/wine.git/commitdiff/e92ba2de43d7afbe0704b11b29f7c30f44dfaeca>. As stated in comment 50, applications requiring unelevated privileges can be run directly, without the need for "runas" or any similar manual intervention. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joel.s.barnes(a)gmail.com --- Comment #54 from Zeb Figura <z.figura12(a)gmail.com> --- *** Bug 39262 has been marked as a duplicate of this bug. *** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 soredake <broaden_acid002(a)simplelogin.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|broaden_acid002(a)simplelogin | |.com | -- 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.
https://bugs.winehq.org/show_bug.cgi?id=40613 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #55 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 9.5. -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla