http://bugs.winehq.org/show_bug.cgi?id=12458
Summary: MySQL Workbench 5 aborts with NotImplementedException
ITextDocument.Range(Int32 cp1, Int32 cp2)
Product: Wine
Version: CVS/GIT
Platform: Other
URL: http://dev.mysql.com/downloads/workbench/5.0.html
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: richedit
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
http://www.bytebot.net/blog/archives/2007/11/27/workbench-beta-adventure-on…
complained that MySQLWorkbench didn't work on Wine, so I gave it a whirl.
On an empty .wine directory, it complained that it needed .net 2.
With 'winetricks dotnet20', it complained
"The operating system is not adequate for running MySQL Workbench 5.0 OSS"
(it requires WinNT version 502, and we're at 500).
With 'winetricks dotnet20 vista', it installed. Running failed early with
Unhandled Exception: System.NotImplementedException: The method or operation is
not implemented.
at System.Windows.Forms.UnsafeNativeMethods.ITextDocument.Range(Int32 cp1,
Int32 cp2)
at System.Windows.Forms.TextBoxBase.ScrollToCaret()
at MySQL.GUI.Shell.GrtPromptForm.ScrollToBottom()
at MySQL.GUI.Shell.GrtPromptForm.PrintText(String text)
at MySQL.GUI.Shell.GrtShellForm.PrintShellOutput(String text)
With "winetricks dotnet20 riched20 vista", it worked much better;
there was a fatal error dialog without much info, but if you ignore it,
the interface comes up and seems to work.
(Though all I really tried was Help.)
So my main complaint is our riched20 doesn't support com text services.
[Oddly, if Tahoma is installed (e.g. winetricks tahoma), it crashes hard
and early with
Unhandled Exception: System.ArgumentException: Parameter is not valid.
at System.Drawing.Font.GetHeight(Graphics graphics)
at System.Drawing.Font.get_SizeInPoints()
at System.Drawing.SystemFonts.FontInPoints(Font font)
at System.Drawing.SystemFonts.get_MenuFont()
but that's another bug, maybe.]
--
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=47386
Bug ID: 47386
Summary: Not tracked mouse cursor in the game
Product: Wine-staging
Version: 4.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: duponamk(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 64719
--> https://bugs.winehq.org/attachment.cgi?id=64719
File with bug
Drakensang Online:
Good day.
In the online game Drakensang Online has long observed the following
bug: when you start the game is not visible the cursor of the mouse,
i.e. the cursor appears, but does not move. And in the background you
can see that it is still moving, but it is not displayed correctly. As a
result, there is no way to play the game normally.
This is also evident in the stable wine.
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.
http://bugs.winehq.org/show_bug.cgi?id=25496
Summary: Fotowall: Crash at Test GL
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: lukasz.wojnilowicz(a)gmail.com
Steps to reproduce:
1) remove ~/.wine
2) winetricks gecko
3) wine Fotowall 0.9 WinXP Vista 7.exe
4) press "SETUP" in right upper corner and then press "Test GL"
Behaviour:
Application crashes.
Expected behaviour:
Application shouldn't crash.
--
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=42955
Bug ID: 42955
Summary: ffxiv dx11 fixme:msctf:ThreadMgrSource_AdviseSink
(0xbcf3ee0) Unhandled Sink:
{ea1ea136-19df-11d7-a6d2-00065b84435c}
Product: Wine
Version: 2.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ssbkm(a)icloud.com
Distribution: ---
ffxiv dx11
--
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=38059
Bug ID: 38059
Summary: MechCommander 2: 0x887602eb: D3DERR_SURFACENOTINVIDMEM
Product: Wine
Version: 1.7.34
Hardware: x86
URL: http://www.sarna.net/files/info/programs/games/mechcom
mander_2/demo/mc2trial.exe
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhansonxi(a)gmail.com
Distribution: Ubuntu
During operation several error dialogs appear, most are related to this error.
They appear to be triggered by display changes (videos starting, window size,
full-screen transitions). Occurs with the CD and trial versions.
Tested on two different systems with different GPUs, Intel GM965/GL960
(xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3) and Radeon HD 7340 (fglrx
2:13.350.1-0ubuntu2), on Xubuntu 14.04 x86_64. The Intel GPU is too slow to
play but the same errors occur.
The game attempts to play full-screen but fails (more error dialogs) and falls
back to windowed.
Native components installed:
winetricks -q directplay dsound
--
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=49567
Bug ID: 49567
Summary: Warframe launcher ntdll dead locking since 5.10
staging, problem persists in 5.11 staging
Product: Wine-staging
Version: 5.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: katharine.chui(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 67707
--> https://bugs.winehq.org/attachment.cgi?id=67707
log at default log level, wine staging 5.11
Since wine 5.10 staging, warframe launher can no longer get through it's
checking for new content stage and would get stuck there seemingly indefinitely
with log message similar with
```
0330:err:ntdll:RtlpWaitForCriticalSection section 0x7f0c224d64c0
"../../../dlls/ntdll/unix/virtual.c: csVirtual" wait timed out in thread 0330,
blocked by 02e4, retrying (60 sec)
```
The said problem was not encountered on wine 5.9 staging, and is also observed
on wine 5.11 staging
below attaches log at default log level
--
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=48836
Bug ID: 48836
Summary: Movies in 'BlazBlue Calamity Trigger' play without
audio
Product: Wine
Version: 5.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: lvb.crd(a)protonmail.com
Distribution: ---
Created attachment 66755
--> https://bugs.winehq.org/attachment.cgi?id=66755
+amstream,+devenum,+evr,+quartz,+qcap,+qedit,+strmbase,+wineqtdecoder,+gstreamer,+timestamp,+seh,+tid
output
Movies in 'BlazBlue Calamity Trigger' play without audio
maybe this output lines from log important
warn:strmbase:filter_inner_QueryInterface
{2dd74950-a890-11d1-abe8-00a0c905f375} not implemented, returning
E_NOINTERFACE.
warn:strmbase:filter_inner_QueryInterface
{36b73880-c2c8-11cf-8b46-00805f6cef60} not implemented, returning
E_NOINTERFACE.
warn:strmbase:filter_inner_QueryInterface
{37d84f60-42cb-11ce-8135-00aa004bb851} not implemented, returning
E_NOINTERFACE.
For this output I used
https://github.com/wine-staging/wine-staging/commit/f9d1798edb5aea67db49ba4…
because BlazBlue need 'xactengine-initial' patchset
https://bugs.winehq.org/show_bug.cgi?id=48684
--
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=43396
Bug ID: 43396
Summary: Microsoft Outlook 2010 crashes after loading profile
Product: Wine
Version: 2.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: marceloalmeida(a)inb.gov.br
Distribution: ---
Created attachment 58739
--> https://bugs.winehq.org/attachment.cgi?id=58739
normal start, with crash
Microsoft Outlook 2010 crashes after loading the profile, but if I start whit
the WINEDEBUG="+relay" option, it works, slowly but works.
Commands used to configure the environment:
- download, install and configure WineHQ
$> sudo dnf config-manager --add-repo
https://dl.winehq.org/wine-builds/fedora/25/winehq.repo
$> sudo dnf install winehq-stable samba-common-tools samba-winbind-clients
$> WINEPREFIX=~/wine/office2010 WINEARCH=win32 wineboot
$> wget
https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetric…
$> chmod +x winetricks
$> WINEPREFIX=~/wine/office2010 ./winetricks dotnet20 msxml
- installl Office
$> WINEPREFIX=~/wine/office2010 wine control
open add/remove apps and do the Office2010 install, (optional) add the email
profile
(optional)
$> WINEPREFIX=~/wine/office2010 winecfg
change the "riched20" to native, to correct the input boxes
- enabling WINEDEBUG="+relay" make the app to run with slow performance, but it
works
#> WINEPREFIX=~/wine/office2010 WINEDEBUG="+relay" wine
~/wine/office2010/drive_c/Office2010/Office14/OUTLOOK.EXE
#> WINEPREFIX=~/wine/office2010 WINEDEBUG="+relay" wine
~/wine/office2010/drive_c/Office2010/Office14/OUTLOOK.EXE
>~/wine/outlooklogdebug.txt 2>&1
- with this commands it crash after load the profile
#> WINEPREFIX=~/wine/office2010 WINEDEBUG="+relay" wine
~/wine/office2010/drive_c/Office2010/Office14/OUTLOOK.EXE > /dev/null 2>&1
#> WINEPREFIX=~/wine/office2010 wine
~/wine/office2010/drive_c/Office2010/Office14/OUTLOOK.EXE
>~/wine/outlooklog.txt 2>&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.
http://bugs.winehq.org/show_bug.cgi?id=36893
Bug ID: 36893
Summary: Spin IDE (for Spin Semiconductor FV-1 DSP chip)
crashes when you try to assemble your code.
Product: Wine
Version: 1.7.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: faultline1989(a)yahoo.com
Created attachment 49001
--> http://bugs.winehq.org/attachment.cgi?id=49001
The backtrace generated when this issue was encountered.
I'm using Linux Mint version 15. Wine version is 1.7.17.
The Windows installer for this program may be found here:
http://www.spinsemi.com/Products/software/spn1001-dev/SpinSetup_1_1_31.exe
Here is the main page describing the system:
http://www.spinsemi.com/products.html
After installing the program, download any of the ".spn" files at this page:
http://www.spinsemi.com/programs.php
Launch the SpinASM IDE and then open the .spn file so you are looking at the
code.
Click on the "a" icon at the top right of the tool bar to begin assembly of the
code. It crashes at this point.
--
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=47397
Bug ID: 47397
Summary: Altium Designer 13.3.4 cannot render DirectX 3D on
second monitor in Wine 4.10
Product: Wine
Version: 4.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: brian.mccarter.ctr(a)navy.mil
Distribution: ---
I have been running Altium Designer 13 on Wine successfully for some time,
using these packages installed with winetricks: gdiplus, corefonts, riched20,
mdac28, msxml16. That list was compiled from suggestions on the AppDB and may
include unnecessary packages, but it's been working fine for me through Wine
4.7. The wineprefix is otherwise unmodified, and contains only the Altium
installation. I use PlayOnLinux to manage the wineprefix and launch the
application. The WINEARCH is win32.
I recently upgraded to Wine 4.10 (vanilla, not staging), and found that Altium
is no longer able to render DirectX 3D on my second monitor. Rendering on my
primary monitor still works fine, and Wine does not crash or otherwise throw an
error when I move the Altium window to my second monitor. The only error is
reported by Altium, and reads: "Graphics adapter for this display does not meet
DirectX requirements (DirectX 9.0c, Shader Model 3.0). Unable to switch to 3D."
Doing some digging, I found that the last version of Wine that renders
correctly on the second monitor is Wine 4.7. Versions 4.8, 4.9, and 4.10 all
cause Altium to display the error.
My system uses an NVIDIA Quadro M4000 and the proprietary driver, version
430.14. The OS is Gentoo Linux, kernel 5.1.5, mesa 18.3.6. I have also tried
a recent Radeon card with mesa drivers and found the same problem, though I
haven't tested that configuration as extensively.
Nothing notable appears the debugger window when I launch the application
through PlayOnLinux.
I have tried to install several other programs with simple 3D displays in an
attempt to duplicate the error with other software, but I haven't been
successful.
Please let me know how I can help resolve this issue.
--
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.