http://bugs.winehq.org/show_bug.cgi?id=25535
Summary: .NET Framework 4.0 Fails to install with HRESULT
0x80070643
Product: Wine
Version: 1.3.9
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pjdowson(a)gmail.com
Wine version is 1.3.9, compiled with no parameters on Fedora 13.
Installing dotNetFx40_Full_x86_x64.exe downloaded from the MS website, the
installer will open and verify the integrity of files. The next stage will
attempt to install the .NET Framework 4.0 Client Profile. Towards the end of
this install the installer will fail with HRESULT 0x80070643, leaving little or
no information in the %TEMP% folder as to the cause.
The installer will only run if wine is set to WinXP.
Process used to reproduce:
WINEPREFIX=~/.wine-net40 sh winetricks gecko
WINEPREFIX=~/.wine-net40 sh winetricks windowscodecs ie7 msxml3
WINEPREFIX=~/.wine-net40 wineboot
WINEDEBUG=+relay WINEPREFIX=~/.wine-net40 wine
Downloads/net40/dotNetFx40_Full_x86_x64.exe &> net-out
I also attempted to install the .NET Framework 4.0 Client Profile prior to
installing the Full package. This provides the same error, the only difference
to the above process used was the filename of the Client Profile installer
dotNetFx40_Client_x86_x64.exe.
Each time I attempted to install I used a clean WINEPREFIX, deleting the prior
one before attempting again.
Screenshot of error:
http://www.stimpy.org/wine/net-error.png
Logs referenced in above screenshot, in %TEMP% dir:
http://www.stimpy.org/wine/net-install-logs.tar.gz
Output of installer debug:
http://www.stimpy.org/wine/net-out.tar.gz
This is my first bug report, I apologize if I have missed anything out.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=12401
Summary: Support junction points, i.e.
DeviceIoCtl(FSCTL_SET_REPARSE_POINT/FSCTL_GET_REPARSE_PO
INT)
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Junction points are one of Microsoft's answers to symlinks.
Unix symlinks could be mapped into junction points.
This would allow applications (e.g. Picasa) avoid following
symlinks if they wanted to.
Also, the .net 2 installer would be happier in winxp mode if wine supported
junction points (see bug 10601):
"The .NET 2.0 Framework installer checks if the target volume is NTFS
filesystem
type and then uses the FSCTL_SET_REPARSE_POINT ioctl (used for mount points and
junctions) to create junction points for each registered assembly in Windows
SxS directory to GAC assembly directory (link target).
Basically the junction point is used to redirect access from one directory to
another."
Tommy Kho posted a patch to add a conformance test for
getting and setting junction points,
http://www.winehq.org/pipermail/wine-patches/2006-March/024956.html
but it was not accepted.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=33997
Bug #: 33997
Summary: win86emu needs Unimplemented function
KERNEL32.dll.CreateSymbolicLinkA
Product: Wine
Version: 1.6-rc4
Platform: arm
URL: http://forum.xda-developers.com/showthread.php?t=20959
34
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nerv(a)dawncrow.de
CC: focht(a)gmx.net
Classification: Unclassified
PostInstall.exe from win86emu says:
wine: Call from 0xb6b71868 to unimplemented function
KERNEL32.dll.CreateSymbolicLinkA, aborting
I already checked that it doesn't try to import something from kernel32 per
ordinal.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=32523
Bug #: 32523
Summary: CreateSymbolicLinkW() is not implemented
Product: Wine
Version: 1.5.17
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alexey.pushkin(a)mererand.com
Classification: Unclassified
It looks like Vista+ CreateSymbolicLinkW() is not implemented:
wine: Unimplemented function KERNEL32.dll.CreateSymbolicLinkW called at
address..., starting debugger...
I suppose it's fairly trivial to implement it with normal unix symlinks, isn't
it ?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=23319
Summary: cmd thinks shift.exe is an internal command
Product: Wine
Version: 1.2-rc4
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
On Windows, 'shift' is an internal command, and 'shift.exe' is an
external command.
Wine's cmd mistakenly thinks 'shift.exe' is a synonym for 'shift'.
This makes it somewhat hard to play EA's Need For Speed: Shift.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=38652
Bug ID: 38652
Summary: VMR9 Owner and Clipping hwnd
Product: Wine
Version: 1.7.38
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: jasonwinter(a)hotmail.com
Distribution: ---
VMR9 - Windows quartz seems to set Owner (I.E. put_Owner) if not already set
when SetVideoClippingWindow is called.
Wine creates a window at monitor position 0,0 (top, left) outside the
application if this isn't explicitly done.
--
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=38924
Bug ID: 38924
Summary: Crash on copy/paste running Tapps2
Product: Wine
Version: 1.7.47
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thomas(a)fehige.de
Distribution: ---
Created attachment 51858
--> https://bugs.winehq.org/attachment.cgi?id=51858
Wine crash report
I'm trying to run Tapps 2 on wine version 1.7.44. My OS is Xubuntu 15.04,
64-bit. It is a graphic programming tool for a series of controllers for
heating, solar heat, warm water and similar that are made by the Austrian
company "Technische Alternative".
The programme can be downloaded from their website at
http://www.ta.co.at/de/download/software/tapps-2.html . I'm using the German
language version.
The programme seems to run fine, apart from the one point: Whenever I try to
copy/paste an Object, wine crashes as soon as I select "paste" from the menu or
type Ctrl-V on the keybord.
The problem persists in wine 1.7.47; cf. discussion on
https://forum.winehq.org/viewtopic.php?f=8&t=24953&sid=cea1d4583ec853e13e85…
.
Attached is wine's crash report.
Thank You -- Thomas
--
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.
http://bugs.winehq.org/show_bug.cgi?id=36514
Bug ID: 36514
Summary: MCIWndCreate does not create a child window if parent
is specified
Product: Wine
Version: 1.7.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvfw32
Assignee: wine-bugs(a)winehq.org
Reporter: nicode(a)gmx.net
WS_CHILD is commented out in the default style for MCIWnd child windows (parent
window specified). But it should be included.
At least one application (King's Quest: Mask of Eternity) depends on the
documented API behavior.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=23015
Summary: PL\SQL Developer: shows standard message boxes behind
main window
Product: Wine
Version: 1.2-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: comdlg32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: chaostya(a)gmail.com
When I write a query in PL\SQL Developer window, then issue it against DB and
then want to close the window I click [x] and it looks like nothing happens,
but if I move main window down I would see a standard "question" message dialog
box asking me if I want to save my changes. I'm on 1.2-rc2 and it's a
regression from 1.2-rc1
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=30853
Bug #: 30853
Summary: Wine doesn’t always handle "right alt" properly
Product: Wine
Version: 1.5.5
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sloonz(a)gmail.com
Classification: Unclassified
Created attachment 40410
--> http://bugs.winehq.org/attachment.cgi?id=40410
workaround/quick and dirty fix
I’m trying to get World of Warcraft working under Wine. However, I have huge
trouble with key bindings (I use unusual key bindings : I use the right half of
my keyboard, whereas most players use the left half).
After investigation, I found 3 bugs (different behaviors between Wine and my
Windows installation). The first one is the management of the right "Alt" key
(labeled "Alt-Gr" on my keyboard). When I press AltGr+l under Windows with
Spy++, I get the followings events :
<03637> 0007045A P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D
fExtended:0 fAltDown:0 fRepeat:0 fUp:0
<03638> 0007045A P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38
fExtended:1 fAltDown:1 fRepeat:0 fUp:0
<03639> 0007045A P WM_KEYDOWN nVirtKey:'L' cRepeat:1 ScanCode:18
fExtended:0 fAltDown:1 fRepeat:0 fUp:0
<03640> 0007045A P WM_DEADCHAR chCharCode:'002F' (47) cRepeat:1 ScanCode:18
fExtended:0 fAltDown:1 fRepeat:0 fUp:0
<03641> 0007045A P WM_KEYUP nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0
fAltDown:1 fRepeat:1 fUp:1
<03642> 0007045A P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D
fExtended:0 fAltDown:1 fRepeat:1 fUp:1
<03643> 0007045A P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38
fExtended:1 fAltDown:0 fRepeat:1 fUp:1
Under Wine 1.5.5 however (WINEDEBUG=+msg), I get those :
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x6007e wp eb
lp 760001 [note: wp = VK_OEM_PA2]
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp 4c lp
c0260001 [note: wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp eb lp
c0760001 [note: wp = VK_OEM_PA2]
With xev, I get :
KeyPress event, serial 93, synthetic NO, window 0x4000001,
root 0xbc, subw 0x0, time 5086996, (1585,410), root:(2578,425),
state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 93, synthetic NO, window 0x4000001,
root 0xbc, subw 0x0, time 5087052, (1585,410), root:(2578,425),
state 0x80, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XFilterEvent returns: False
After "setxkbmap us", AltGr is bound to Alt_R under X (checked with xev), and I
get this under Wine :
trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp
a5 lp 21380001 [wp = VK_RMENU]
trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp
4c lp 20260001 [wp = 'L']
trace:msg:peek_message got type 6 msg 106 (WM_SYSCHAR) hwnd 0x10046 wp 6c
lp 20260001 [wp = 'l']
trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10046 wp 4c
lp e0260001 [wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10046 wp a5 lp
c1380001 [wp = VK_RMENU]
(yes, I have a KEYUP without KEYDOWN)
Wich is still not the same as Windows. So I think there is two problems here :
- ISO_Level3_Shift is not properly recognized by Wine
- "AltGr" doesn't have the same behavior under Wine and Windows
FYI, attached patch is a workaround to have the same behavior than Windows.
With it, I get this under Wine :
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a2
lp 1d0001 [note: wp = VK_LCONTROL]
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a4
lp 20380001 [note: wp = VK_LMENU]
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp 4c
lp 20260001 [note: wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp 4c lp
e0260001
trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10062 wp a2
lp e01d0001
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp a4 lp
c0380001
Which is still not the same as Windows :
- Windows uses (right) control + menu (with fExtended flag for menu) whereas
Wine uses left control + left menu. Not investigated if this is related to
TranslateMessage.
- AltGr+L is a dead symbol on my keymap. Windows send a DEADCHAR message,
wheras Wine send nothing. Note that I had to disable the XFilterEvent test in
event.c to have those messages, otherwise nothing is sent to the program (but
that’s another story for another bug report)
But it suffice for my use case (WoW key bindings with right alt)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.