https://bugs.winehq.org/show_bug.cgi?id=48012
Bug ID: 48012
Summary: Rebelbetting: clicking on “Goto” has no effect
Product: Wine
Version: 4.18
Hardware: x86-64
URL: http://rebelbetting.com/files/RebelBettingSetup.exe
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 65544
--> https://bugs.winehq.org/attachment.cgi?id=65544
Wine 4.18 console log
Rebelbetting has a “Goto” button that opens some internal browsers. This button
currently does nothing.
The last time I have a report of this working was way back in 2015.
Rebelbetting auto-updates so if there is a regression it will be way back, and
will take a while to find.
Workarounds:
WINEARCH=win32 winetricks -q dotnet45
Same in Vanilla and 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.
http://bugs.winehq.org/show_bug.cgi?id=24945
Summary: font is not drawn in synth1 instrument selection
window
Product: Wine
Version: 1.3.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: fonts
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: armandsl(a)gmail.com
Created an attachment (id=31583)
--> (http://bugs.winehq.org/attachment.cgi?id=31583)
synth1 on wine 1.3.4
Starting with wine version 1.2.0 font is not drawn in synth1 instrument
selection window anymore. Synth1 is free VST software synthesizer
(http://www.geocities.jp/daichi1969/softsynth/).
OS used: Linux (Fedora 14)
Dll is loaded by LMMS (Linux Multi Media System) version 0.4.8
It worked with wine 1.1.38 (with old font subsystem).
--
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=46517
Bug ID: 46517
Summary: Warcraft III: Installation fails (trouble launching
Battle.net Update Agent)
Product: Wine
Version: 4.0-rc7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)iooioio.hadar.uberspace.de
Distribution: Ubuntu
Created attachment 63372
--> https://bugs.winehq.org/attachment.cgi?id=63372
Console output
I am currently unable to install Warcraft III via the installer provided by
Blizzard. It's a web installer (used to work in the past) so the problem might
be related to wine network code.
Attached you will find the console output and a screenshot of the error message
in the application.
--
Some additional info about my system (just in case):
Distro: elementary OS Juno
Kernel: 4.15.0-43-generic
Graphics: Proprietary NVIDIA 410.78
--
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=38521
Bug ID: 38521
Summary: Unhandled exception: page fault on read access to
0x00000000 in 32-bit code (0x7
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: ettl.martin78(a)gmail.com
Distribution: ---
Created attachment 51390
--> https://bugs.winehq.org/attachment.cgi?id=51390
backtrace from wine
Steps to reproduce:
1) Install SourceNavigator from
(http://sourceforge.net/projects/sourcenav/?source=typ_redirect) on Ubuntu
Linux 15.04 (32-Bit) with wine.
2) Execute SourceNaviator
3) Close SourceNaviator
4) The exception message is shown. Please refer to the backtrace.
If you have questions, please feel free to ask.
Many thanks for working so hard on wine.
Best regards
Martin Ettl
--
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=41580
Bug ID: 41580
Summary: Vegas Pro 11
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cosminvonsovici(a)gmail.com
CC: winetest(a)luukku.com
Distribution: ---
Created attachment 55916
--> https://bugs.winehq.org/attachment.cgi?id=55916
Log file at the end
Ubuntu 16.04.1 64 bit (x86 Prefix)
I successfully managed to install and authenticate Sony Vegas Pro 11 without
errors. .NET 3.5 SP1 installed with no issue along with the other dependencies.
Upon opening, ErrorReportClient.exe crashes and gives an error. I disabled this
in the config file and when I open it as it gets to the stage "Creating IO
manager" a popup appears and I am forced to close.
I have installed this app in windows (same exe file) and it works without
issues. I followed the guide at
https://appdb.winehq.org/objectManager.php?sClass=version&iId=33292 without the
dlls and with Windows version set to Windows XP, having followed all steps. I
would be so appreciative if you can help with this issue as I would absolutely
need and love Vegas in Wine. This is my first report so I hope I did it right!
Thank you for your time. I got the install exe from
http://www.afterdawn.com/software/audio_video/video_editing/vegas_pro_32.cfm
If you need any more information please contact me.
--
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=41571
Bug ID: 41571
Summary: Vegas Pro 11
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cosminvonsovici(a)gmail.com
Distribution: ---
Created attachment 55907
--> https://bugs.winehq.org/attachment.cgi?id=55907
Log file outputted after has generated an exception that could not be handled
Ubuntu 16.04.1 64 bit (x86 Prefix)
I successfully managed to install and authenticate Sony Vegas Pro 11 without
errors. .NET 3.5 SP1 installed with no issue along with the other dependencies.
Upon opening, ErrorReportClient.exe crashes and gives an error. I disabled this
in the config file and when I open it as it gets to the stage "Initializing UI"
a popup appears saying "Application has generated an exception that could not
be handled" Process ID=0x7a(122) Thread ID=0x41(65)and I am forced to close.
I have installed this app in windows (same exe file) and it works without
issues. I followed the guide at
https://appdb.winehq.org/objectManager.php?sClass=version&iId=33292 without the
dlls and with Windows version set to Windows 7. I would be so appreciative if
you can help with this issue as I would absolutely need and love Vegas in Wine.
This is my first report so I hope I did it right! Thank you for your time. I
got the install exe from
http://www.afterdawn.com/software/audio_video/video_editing/vegas_pro_32.cfm
If you need any more information please contact me.
--
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=27211
Summary: runtime error R6025 while start usbclient.exe
Product: Wine
Version: 1.3.20
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
A free demo can be downloaded from http://www.usb-over-network.com/
$ wget http://www.usb-over-network.com/usb-over-network-client.msi
Install:
$ msiexec /i usb-over-network-client.msi
make sure use the git source to avoid bug 27033
Start:
$ wine usbclient.exe
Then a runtime error message display:
Program: C:\windows\system32\ftusbsrvc.exe
R6025
-pure virtual function call
After click the "OK" button, the program will crash.
All log is below:
fixme:win:RegisterDeviceNotificationA (hwnd=0x12d998,
filter=0x99e9c8,flags=0x00000001) returns a fake device notification handle!
wine: Unhandled exception 0x40000015 at address 0x7bc90073:0x00409026 (thread
0015), starting debugger...
not sure whether this is a duplicate of bug 25869 or Bug 26835.
winetricks vcrun2005 vcrun2008 vcrun2010 not work.
--
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=43639
Bug ID: 43639
Summary: "Log In" and "Forgot Password" links on main page are
broken
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)der-ingo.de
CC: austinenglish(a)gmail.com
Distribution: ---
On the main page https://bugs.winehq.org/ there are two links:
- Log In
- Forgot Password
I mean the actual links and not the buttons.
The "Log In" link has no effect.
The "Forgot Password" link actually changes the "Log In" button above.
Probably those two links are unnecessary. They are confusing at least.
I suggest to either fix them or probably better, remove them.
Cheers, Ingo =;->
--
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=39709
Bug ID: 39709
Summary: winmm:mci makes a buzzing sound
Product: Wine
Version: 1.8-rc2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Running winmm:mci makes a buzzing sound. The first line (of many) where this
happens is the line below from test_playWAVE():
/* A second play caused Wine<1.1.33 to hang */
err = mciSendStringA("play mysound from 500 to 220:5:0 wait", NULL, 0,
NULL);
This is because the test records sound to tempfile.wav before playing it back.
So if the recording levels are set a bit high tempfile.wav can record
electrical noise, the buzzing sound, and thus makes noise when playing it back.
This is confirmed by changing the recording level in the KDE mixer prior to
running the test:
* Setting it all the way down avoids the buzzing sound.
* Setting it even moderately high causes the buzzing sound.
Conformance tests are supposed to not make noises when not run in interactive
mode so this should be fixed. I see two ways for this:
* Set and restore the recording level in test_recordWAVE().
* Create tempfile.wav by hand instead of relying on the output of
test_recordWAVE().
--
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=47855
Bug ID: 47855
Summary: Run tests in more than one VM at a time
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Some Wine tests have pretty stringent timing requirements:
* Some audio tests play a short sound bite and make sure the playback lasted
for the expected time within a few tens of seconds as a way to ensure audio is
played at the right rate. But VMs are not always very good at respecting
precise timing requirements when there is other activity on the host.
* Some tests (msi) generate quite a bit of disk traffic and take a while to
run. Running two of those simultaneously can sometimes push them over the 2
minutes limit, causing them to time out. That said there may be something else
afoot here as these run times vary from ~20s to ~100s depending on the VM for
seemingly no reason.
As a consequence the TestBot is configured to only do one thing at a time: run
at most one test or revert one VM. This is at odds with hardware evolution and
new TestBot requirements:
* SSDs are much faster than hard drives and thus should solve the disk
bottleneck issues.
* The builds for the Wine VMs take a lot more time than just producing PE
executables for the Windows VMs. To speed up compilation it is necessary to
increase the parallelism which means buying a machine with as many cores as
possible and assigning as many as possible to the Wine VMs.
* But while running single threaded tests in a single VM on a quad-core machine
is bad enough, doing the same thing on a 16+ threads machine would truly be a
waste.
So a way to be able to run tests in more than one VM at a time should be found.
The first step would be to verify that these issues still exist (this means
distinguishing them from the usual random failures). If they don't then problem
solved!
Otherwise CPU-pinning is a solution that's usually mentioned in gaming circles.
The questions are:
* Would it actually help?
* How to integrate it with the TestBot. Is this something that should be
configured through Libvirt when restoring a live snapshot? Or is this something
that should be defined 'statically' in the VM's configuration?
* What happens if two VMs are pinned to the same CPU core? Will Libvirt prevent
us from starting both at the same time or is it up to the TestBot Engine to
make sure this does not happen? How?
* What happens when a VM that's is pinned to CPU core 7 is moved to a 4 core
host? Is the pinning ignored or does the administrator have to manually change
its configuration?
--
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.