https://bugs.winehq.org/show_bug.cgi?id=44575
Bug ID: 44575
Summary: installing dotnet452 failed: echo '%ProgramFiles%'
returned empty string
Product: Wine
Version: 1.8.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kenorb(a)gmail.com
Distribution: ---
This is happens when installing dotnet452. I'm using Wine installed from
http://winebottler.kronenberg.org/
###BOTTLING### applywinetricks.sh
###BOTTLING### Gathering debug Info...
Versions
OS...........................: darwin17
Wine.........................: 1.8.3
WineBottler..................: 1.8.3
Wineticks....................: 20180217-next - sha256sum:
6dd23a6c59febc56a2c5a31aabc0c1b92545ec176c64b494aa088c5d993bf588
BUNDLERESOURCEPATH...........:
/var/folders/32/4w12jr5s07jbl07_wm7jgc8c0000gn/T/AppTranslocation/6B7D7A6D-60A2-47C6-A121-D2240DF5E30F/d/Wine.app/Contents/Frameworks/WBottler.framework/Resources
INETRICKS_ITEMS.............: dotnet452 vcrun6 vcrun2017 winhttp wininet
DLL_OVERRIDES................:
EXECUTABLE_PATH..............: notneeded
EXECUTABLE_ARGUMENTS.........:
EXECUTABLE_VERSION...........: 1.0.0
BUNDLE_COPYRIGHT.............:
BUNDLE_IDENTIFIER............: org.kronenberg.winebottler
BUNDLE_CATEGORYTYPE..........: public.app-category.utilities
SILENT.......................:
Hardware:
Hardware Overview:
Model Name: MacBook Pro
###BOTTLING### installing dotnet452
### LOG ### Command 'source
/private/tmp/winebottler_1519248378/nospace/winetricks.sh --no-isolate
dotnet452' returned status 1.
warning: taskset/cpuset not available on your platform!
------------------------------------------------------
/private/tmp/winebottler_1519248378/nospace/wine cmd.exe /c echo
'%ProgramFiles%' returned empty string, error message "wine: chdir to
/private/tmp/winebottler_1519248378/nospace/wineprefix
: No such file or directory"
------------------------------------------------------
###ERROR### Command 'source
/private/tmp/winebottler_1519248378/nospace/winetricks.sh --no-isolate
dotnet452' returned status 1.
Task returned with status 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=43948
Bug ID: 43948
Summary: d3dx9 effects - pixel shader 2.0 does not render well
Product: Wine
Version: 2.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: havran.jan(a)email.cz
Distribution: ArchLinux
Created attachment 59587
--> https://bugs.winehq.org/attachment.cgi?id=59587
d3dx9 effects
I have strange behaviour of effects in d3dx9 application where I have access to
source code. I tried to reduce code size to the minimum where this bug is still
reproduciable. The problem is, when I apply attached shaders.fx effects (VS +
PS) on some objects (triangle for example), then the object is black in Wine,
while in Windows or Gallium Nine it is grey.
Here is list of configuration where it works as expected (expected = how it
works on native Windows):
Windows 7 + D3D9 + AMD graphics
Windows 7 + D3D9 + Intel graphics
Linux + Wine + Gallium Nine + AMD graphics (Mesa)
Here is list of configuration where it does not work (renders black objects):
Windows 7 + WineD3D + AMD graphics
Windows 7 + WineD3D + Intel graphics
Linux + Wine + WineD3D + AMD graphics (Mesa)
Linux + Wine + WineD3D + Intel graphics (Mesa)
There are possibly two issues in attached pixel shader:
1) uninitialized IN.lightVec
2) usage of normalize() function (and possible division by zero)
But here is the strange behaviour:
1) when I set IN.lightVec red, green or blue to 0.0 (one or two of them, but
not all of them, because it cause crash), then it is rendered black in Windows
and in Wine as well.
2) when I set IN.lightVec.r (for example) to "IN.lightVec.r + 0.0f", then it
has no effect.
>From point 2 it looks like IN.lightVec default values are 0.0f, but from point
1 it looks opposite. So I have no idea what are values of uninitialized vector.
I thought that it could be related to bug #34266 [1], but:
1) created patch did not work for me
2) when I set IN.lightVec to zero, the bug disappears
I can upload simple d3d app which use these effect and also binary file (exe).
I have no D3D (and D3D shaders) deep knowledge, so maybe I something understand
wrong.
I also used native d3dcompiler_43 so Wine could compile these shaders.
[1] https://bugs.winehq.org/show_bug.cgi?id=34266
--
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=39148
Bug ID: 39148
Summary: Guild Wars 2: Hangs on Close
Product: Wine
Version: 1.7.50
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: soulhuntor(a)gmail.com
Distribution: ---
Guild Wars 2: Hangs on Close
Starting with 1.7.50 when trying to close Guild Wars 2 the program looks like
it closes but the Gw2.exe is still running.
--
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=44523
Bug ID: 44523
Summary: When visual style is enabled wine explorer column
header doesn't draw until mouseover
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: uxtheme
Assignee: wine-bugs(a)winehq.org
Reporter: stu.axon(a)gmail.com
Distribution: ---
Using current wine from git:
9d897b73a877e5eaae26df87930c951ff8273c14
First open wine explorer using no theme, and notice the column headers are
drawn correctly.
Next - set a visual style using winecfg (I confirmed with Royale Noir and
ubuntu light).
Royale Noir theme
http://www.istartedsomething.com/20061029/royale-noir/
This time the column headers are not drawn until you mouseover them - as shown
in the linked video
Video of bug
https://www.youtube.com/watch?v=YBcduwqQt48&feature=youtu.be
Terminal output while reproducing the bug -
$ wine explorer
0086:fixme:nstc:NSTC2_fnSetControlStyle2 mask & style (0x00000004) contains
unsupported style(s): 0x00000004
0086:fixme:shell:IShellBrowser_fnSendControlMsg stub, 0x1351a0 (2, 1026, a003,
0, 0x33f508)
0086:fixme:shell:IShellBrowser_fnSendControlMsg stub, 0x1351a0 (2, 1026, a004,
1, 0x33f508)
0086:fixme:shell:IShellBrowser_fnSendControlMsg stub, 0x1351a0 (2, 1025, a003,
1, 0x33f508)
0086:fixme:shell:IShellBrowser_fnSendControlMsg stub, 0x1351a0 (2, 1025, a004,
1, 0x33f508)
0086:fixme:uxtheme:DrawThemeTextEx unsupported flags 0x002100f2
0086:fixme:uxtheme:DrawThemeTextEx unsupported flags 0x002100f2
[repeated]
--
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=44569
Bug ID: 44569
Summary: Winecfg - new desktop colour doesn't apply immediately
Product: Wine
Version: 2.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stu.axon(a)gmail.com
Distribution: ---
Run winecfg with wine set to emulate a desktop.
Open Winecfg, go to desktop integration
choose Item->Desktop
Choose a new colour and click apply or OK.
The new colour does not show up until you start wine 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=44568
Bug ID: 44568
Summary: wine 3.0 ends with "wine_kernel_init boot event wait
timed out" on Mac OS X 10.13.3
Product: Wine
Version: 3.0
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: teenylasers(a)gmail.com
Created attachment 60536
--> https://bugs.winehq.org/attachment.cgi?id=60536
on-screen output after executing "wine <my.exe>"
Hello,
I recently updated wine to 3.0 using Homebrew on Mac OS X High Sierra. What
used to work with wine 2.0.2 now produce the attached error when I try to do
"wine <my.exe>". At the same time, Wine launches with a window that says "“The
Wine configuration in /home/user/.wine is being updated, please wait…”, but it
never exits.
I have tried deleting ~/.wine and ~/.local/share/<wine-related>, brew uninstall
wine and then reinstall xquartz and wine. The result is the same. Can you
please help?
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=44522
Bug ID: 44522
Summary: Window titlebar doesn't support visual style
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: uxtheme
Assignee: wine-bugs(a)winehq.org
Reporter: stu.axon(a)gmail.com
Distribution: ---
Created attachment 60477
--> https://bugs.winehq.org/attachment.cgi?id=60477
Screenshot of current wine with unthemed titlebars + royale noir visual style
Using wine from current git:
9d897b73a877e5eaae26df87930c951ff8273c14
And the freely available Royale Noir theme
http://www.istartedsomething.com/20061029/royale-noir/
Titlebars are not themed at all (trying with desktop emulation and without, and
also toggled the setting to allow the window manager to manager windows)
--
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=44555
Bug ID: 44555
Summary: Native windows file associations (not Linux's) are
automatically replaced with winebrowser
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: magiblot(a)hotmail.com
Distribution: ---
Hi there.
So I want to open image files with a Windows application, e.g. Microsoft Photo
Editor, provided by Office 97.
After installation, the file association is created in the registry. Thus, a
key is written in the entry 'HKEY_CLASSES_ROOT\pngfile\shell\open\command' with
the value 'C:\Program Files\Common Files\Microsoft Shared\PhotoEd\PhotoEd.exe
"%1"'.
With this registry configuration, the wine-extension-png.desktop file which
runs 'wine start /ProgIDOpen pngfile %f' properly opens files with Microsoft
Photo Editor from the Linux file manager.
In certain conditions, such as after a wine update, a 'The configuration in
($WINEPREFIX) is being updated, please wait...' dialog box appears and, from
then on, the value of the key I mentioned above is changed back to '"C:\Program
Files\Internet Explorer\iexplore.exe" -nohome'.
Therefore, 'wine start /ProgIDOpen pngfile %f' does no longer open Microsoft
Photo Editor, but winebrowser.
I would like not to have my file associations replaced anytime wine wants to.
--
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=36014
Bug ID: 36014
Summary: secur32/{negotiate,ntlm} tests fail with debian's
samba/winbind 4
Product: Wine
Version: 1.7.16
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: secur32
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Follow up to bug 35965.
The secur32 tests fail on a default installation of samba/winbind4 on Debian 7
(wheezy):
../../../tools/runtest -q -P wine -T ../../.. -M secur32.dll -p
secur32_test.exe.so negotiate && touch negotiate.ok
WARNING: gnome-keyring:: couldn't connect to:
/home/austin/.cache/keyring-mD4V6F/pkcs11: No such file or directory
ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information
available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so)
fixme:secur32:nego_AcquireCredentialsHandleW forwarding to NTLM
fixme:secur32:nego_AcquireCredentialsHandleW forwarding to NTLM
ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information
available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so)
ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information
available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so)
Unable to setup messaging listener for
'/var/lib/samba/private/smbd.tmp/msg/msg.10803.179872511':NT_STATUS_OBJECT_NAME_NOT_FOUND
negotiate.c:295: Test failed: server returned 80090304, more tests will fail
negotiate.c:305: Tests skipped: authentication failed, skipping remaining tests
negotiate.c:349: Test failed: DeleteSecurityContext returned 80090301
make: *** [negotiate.ok] Error 2
that lack of version information message seems bad, and makes the tests fail
even worse later (in ntlm.c):
../../../tools/runtest -q -P wine -T ../../.. -M secur32.dll -p
secur32_test.exe.so ntlm && touch ntlm.ok
WARNING: gnome-keyring:: couldn't connect to:
/home/austin/.cache/keyring-mD4V6F/pkcs11: No such file or directory
ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information
available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so)
..
ntlm_auth: /usr/lib/i386-linux-gnu/libwbclient.so.0: no version information
available (required by /usr/lib/i386-linux-gnu/samba/libauth4.so)
===============================================================
INTERNAL ERROR: Signal 11 in pid 10826 (4.0.0beta2)
Please read the Trouble-Shooting section of the Samba HOWTO
===============================================================
PANIC: internal error
but, as Dmitry points out in https://bugs.winehq.org/show_bug.cgi?id=35965#c9,
the wiki says that only ntlm_auth needs to be available, nothing is said about
the configuration:
"To get access to all the features while using NtlmSigningAndSealing, you need
an up-to-date version of ntlm_auth. Samba 3.0.26 or later will do. In some
distributions, you need to install the "winbind" package to get ntlm_auth.
If you want client mode NTLM for Wine, e.g. reading your email using Outlook
over a connection with NTLM encryption, that's all you need. "
--
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.