http://bugs.winehq.org/show_bug.cgi?id=25412
Summary: Shareaza does not save certain preferences [RE: Bug
14269]
Product: Wine
Version: 1.3.8
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: trapdoor6(a)gmail.com
This is a similar issue as described in bug #14269 [still open] but it's
related to different Wine versions: 1.3.8. I also noticed it on a few earlier
developer and stable versions, I guess it's been never fixed in Wine. Please
find details below:
------------------
Software: Shareaza
project page: http://shareaza.sourceforge.net/
version: 2.5.3.0
Problem details:
1) Under 'Tools > Shareaza Settings > General > Library'
option: 'Quick hashing (Uses more CPU)'
Enabling it works only for one session. After restarting Shareaza it's disabled
again.
2) Under 'Tools > Shareaza Settings > Networks > Gnutella' and '~ > eDonkey'
option: 'Always connect to Gnutella / eDonkey'
Enabling these won't be saved. After restarting Shareaza both are disabled
again (which means that Shareaza connects only to Gnutella1 and I need to
connect to the other networks manually in the 'Network' tab in the main
window).
--
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=41354
Bug ID: 41354
Summary: PDF-XChange Editor
Product: Wine
Version: 1.9.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sb56637(a)gmail.com
Distribution: ---
Hello, PDF XChange Editor has a bug in wine where it only accepts form input a
few times. When in a PDF document with several forms, it stops accepting form
input after editing several form elements. For example, try typing in one text
field, and then move into another text field. It will no longer accept input.
This is an important bug, because native PDF readers under Linux are pathetic,
and PDF XChange Editor works flawlessly otherwise under Wine.
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.
http://bugs.winehq.org/show_bug.cgi?id=32326
Bug #: 32326
Summary: DirectSound output in SNES9x gives crackling/glitchy
audio
Product: Wine
Version: 1.5.18
Platform: x86-64
URL: http://files.ipherswipsite.com/snes9x/snes9x-1.53-win3
2.zip
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-dsound
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
This bug applies to the SNES9x Super NES emulator. I'm testing with Wine
1.5.18-72-g0c0b229, Lubuntu 11.10 x86-64, Nvidia driver 304.64, SNES9x 1.53.
(I set the bug component to directx-dsound, but that might not be correct.)
Sound output using DirectSound is very CPU-intensive, and the sound
crackles/glitches. Or rather, something about the sound output takes a
relatively long time. According to "top" the CPU usage of SNES9x itself doesn't
go through the roof with sound enabled.
Emulation speed easily reaches 60fps with sound output disabled. On native
Windows that's the case with DirectSound output (as opposed to the default is
enabled too. CPU usage with sound disabled is ~26%.
However on Wine with 48kHz DirectSound output the frame rate I see drops to
~45fps, CPU usage in top ~24% (lower usage because fewer frames per second are
being emulated). If I disable the "Sync Sound" option frame rate returns to
60fps, ~30% CPU, but the sound still crackles.
That's with the default buffer length of 64ms. Increasing that to 210ms helps a
bit; I get 60fps even with Sync Sound enabled, though the sound still crackles.
Decreasing buffer length to 16ms I get about 10fps with Sync Sound enabled.
I don't think this problem is due to my hardware; other sound-producing
programs like Audacious, flash plugin etc. seem to be fine. And by comparison,
the Nestopia NES emulator in Wine produces (almost) glitch-free sound
regardless of the program's latency setting.
$ lspci -vv -s00:1b.0
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)
Subsystem: Lenovo Device 384e
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 47
Region 0: Memory at fc300000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
To hopefully reproduce the issue:
- Download and unzip SNES9x
- Download a ROM image, e.g. from
http://pdroms.de/files/supernintendoentertainmentsystem/skipp-and-friends-p…
- Run SNES9x. Choose Sound->Settings... and change Sound Driver to Snes9x
DirectSound and Playback Rate to 48 KHz. (Selecting any other rate causes a
crash for me, see bug 32312.)
- Select Video->Display Configuration... and change Output Method to
DirectDraw. (The default Direct3D just gives a blank screen, see bug 32319.)
- Select File->Load Game... and choose the ROM image.
- You should see graphics in the window and hear crackling/glitching sound.
- In the sound settings, you can experiment with changing the buffer length and
toggling the "Synchronize with sound core" option. I couldn't find any
combination which gave artifact-free sound.
For a +dsound log see the one I uploaded for bug 32312 at
http://bugs.winehq.org/attachment.cgi?id=42668
--
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=42549
Bug ID: 42549
Summary: Tibia 11: crashes when trying install
Product: Wine
Version: 2.0
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: daniel.docki(a)gmail.com
Created attachment 57453
--> https://bugs.winehq.org/attachment.cgi?id=57453
backtrace
Wine crashes when I trying install Tibia 11
--
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=39260
Bug ID: 39260
Summary: Audible Manager device activation dialog window is
blank
Product: Wine
Version: 1.7.50
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: torsten.crass(a)eBiology.de
Distribution: Debian
Hi,
I'm able to install Audible's Manager.exe using ActiveSetupN.exe. So far, so
good.
However, when trying to register or activate the Manager via "Devices /
Activate",
- I first get a Dialog saying 'To activate your Audible Desktop Player please
press "OK" button',
- and when doing so, a maximized, blank window appears (titled 'Audible
Activation'),
- and nothing further happens.
This used to work some time ago.
Any ideas what might be the problem?
Best regards --
-- Torsten
--
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=37552
Bug ID: 37552
Summary: Delphi car diagnostic software DS150E (equal Autocom
CDP) doesn't run
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: artur.byte(a)gmail.com
Distribution: ---
Created attachment 49977
--> https://bugs.winehq.org/attachment.cgi?id=49977
bug report
Delphi car diagnostic software DS150E (equal Autocom CDP) doesn't run
All requarements is ok. NetFramework 3.5 installed.
Bug report is attached.
--
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=41698
Bug ID: 41698
Summary: Two worlds crash report
Product: Wine
Version: unspecified
Hardware: Other
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: winemac.drv
Assignee: wine-bugs(a)winehq.org
Reporter: peasgood3(a)googlemail.com
Created attachment 56101
--> https://bugs.winehq.org/attachment.cgi?id=56101
crash report
Two worlds, played via Steam, crashed created the attached report and told me
to file it with you. I have no technical knowledge of the things asked above
except that i am playing via Steam on a MacBook Pro with the latest OS
software.
I don't know enough about the above questions to ensure that the info I've
given you is correct. Please contact me if there is anything that you wish
clarified, and you might want to ask me in laymans terms rather than tech
speak.
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=42853
Bug ID: 42853
Summary: Can not lunch the game.
Product: Wine
Version: 2.0-rc6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thithib.cohergne(a)gmail.com
Distribution: ---
Created attachment 57949
--> https://bugs.winehq.org/attachment.cgi?id=57949
The log of the crash wine made.
I can't even lunch UEBS (Ultimate Epic Battle Simulator), which is a game. It
might be because the developer has made his own engine.
--
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=38999
Bug ID: 38999
Summary: Intel graphics card has glitches in Aarklash Legacy
Product: Wine
Version: 1.7.47
Hardware: Other
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ipickert55(a)gmail.com
Using my intel Iris Pro graphics card, Aarklash has a glitch where almost
everything in the game is black, don't know why. Here are some images:
http://i.imgur.com/MlGZ5jK.pnghttp://i.imgur.com/jPLQZKo.png
It works fine on my Nvidia graphics card.
--
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=38113
Bug ID: 38113
Summary: Unity3D is not running well on NVIDIA GPU.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: antek6jutka(a)gmail.com
Distribution: ---
Created attachment 50794
--> https://bugs.winehq.org/attachment.cgi?id=50794
Output from wine [...]Unity.exe command.
OS: ArchLinux x86_64
GPU: NVIDIA GeForce GT 630
CPU: 4-cores (i5) x3.10GHz
RAM: 16GB DDR3
Wine release: latest (1.7.36)
Running Unity ends with crash. Main window and loading screen is
very...strange. Usually it not loads and then I need to kill it with CTRL+Z,
killall Unity.exe, fg.
--
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=41823
Bug ID: 41823
Summary: dxwsetup.exe
Product: Wine
Version: 1.9.24
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: artemy.bobrov(a)yandex.ru
Distribution: ---
Created attachment 56237
--> https://bugs.winehq.org/attachment.cgi?id=56237
backtrace
This bug occurs during installation game Avatarika
--
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=39548
Bug ID: 39548
Summary: fixme:d3d_surface:wined3d_surface_blt Using fallback
for cross-swapchain blit.
Product: Wine
Version: 1.7.54
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: evolutionv8(a)yandex.ru
Distribution: ---
fixme:d3d_surface:wined3d_surface_blt Using fallback for cross-swapchain blit.
fixme:d3d_surface:surface_blt_special Implement hardware blit between two
different swapchains
fixme:d3d9:D3DPERF_GetStatus (void) : stub
Current errors occur trying to run Sonic Lost World. The game is blinking and
loads first intro scenes VERY slowly.
--
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=39446
Bug ID: 39446
Summary: Spotify installs but only gives a black screen when
launched
Product: Wine
Version: 1.7.52
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 52563
--> https://bugs.winehq.org/attachment.cgi?id=52563
Spotify 1.7.52 output - openSUSE Tumbleweed
Hello everyone,
I would like to report that Spotify installs fine now but only gives a black
screen when launched. Console output is attached.
Regards,
Maik
--
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=35137
Bug ID: 35137
Summary: Hitman: Blood Money demo needs native d3dx9_27
Product: Wine
Version: 1.7.8
Hardware: x86
URL: http://www.gamershell.com/download_13964.shtml
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
Demo crashes without native d3dx9_36
fixme:d3dx:ID3DXEffectCompilerImpl_CompileEffect iface 0x6fd8e660, flags 0x500,
effect 0x122a56c, error_msgs 0x122a564 stub
and also needs native d3dx9_27 because after intro movie I can't see the main
menu.
--
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=17836
Summary: Motocross Madness 2 crashes at start
Product: Wine
Version: 1.1.17
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
Created an attachment (id=20098)
--> (http://bugs.winehq.org/attachment.cgi?id=20098)
trace and disassembly of crash location
In AppDB, people have reported Motocross Madness 2 (mcm2) crashing in the intro
but nobody had filed a bug yet. The backtrace makes it look like mcm2 crashes
in, or immediately after, quartz.dll or amstream, after accessing ui\events.avi
at the start of the program, after displaying for some seconds the stunt &
warnings picture also known from the demo.
The demo is not affected and proceeds from the intro picture to the menu.
A log extract (+almost-all,-relay,-nls) from around the exception is attached.
The processed file UI/events.avi is an Intel Indeo v5 video. The installer did
not complain that Indeo is mising! Replacing it with a Cinepak avi, with an
empty file, deleting it or installing iv5 still produces crashes at the same
location in mcm2. Same with clicking to skip the intro picture or disabling
quartz.dll.
MCM2 suffers from SafeDisk 1.41.000 protection so it would not run as is in
wine (or rather, it crashes much earlier). I tried 2 different cracks, both
produced the same exception.
--
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=37913
Bug ID: 37913
Summary: Inconsistent rounding behaviour for sprintf
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: christopherwuy(a)gmail.com
Distribution: ---
sample source code and output demonstrating the problem:
#include <iostream>
#include <stdio.h>
using namespace std;
int main()
{
double a;
a = 3.5;
char *tmp = new char(100);
char fmt[18] = " is %.0f";
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = -4.5;
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = -0.5;
sprintf(tmp, fmt, a);
cout<<endl<<a<<tmp<<endl<<endl;
a = 2597.625;
printf("%.3f", a);
sprintf(tmp, " is %.2lf", a);
cout<<tmp<<endl<<endl;
}
This code running by wine 's Output is:
3.5 is 4
-4.5 is -4
-0.5 is -0
2597.625 is 2597.62
while windows' output is:
3.5 is 4
-4.5 is -5
-0.5 is -1
2597.625 is 2597.63
It indicated that Wine's sprintf used rounding rule which is Round half to
even, while windows used Round half away from zero.
You can find a detailed discussion of 'similar bug' form
https://sourceware.org/bugzilla/show_bug.cgi?id=4943
--
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=24320
Summary: Unexpected DetectEnvStatus.exe crash with Cisco Quick
VPN Client (QVPN 1.4.1.2)
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ethanfharris(a)gmail.com
Cisco QVPN v1.4.1.2 does not work under Wine. QVPN is used to establish an
IPSec Virtual Private Network tunnel from a client computer to a Cisco
Router/Gateway to facilitate secure communication over the internet.
There appear to be 3 errors when running the Cisco QVPN application under Wine:
(a) an apparent crash / closure of DetectEnvStatus.exe
(b) a failure to resolve a DDNS domain name, and
(c) QVPN is not able to ping the gateway router, and all data transfer over the
VPN fails.
In all cases a popup box appears (see attached screenshot) indicating that
DectectEnvStatus.exe has a serious problem and has closed.
If anyone wants to debug this, I can supply a copy of QVPN, and I can set up a
temporary guest account on my WRVS4400N small business router for testing
purposes. QVPN works fine under Windows Vista SP2, and works fine on a Ununtu
10.04LTS host with a Vista guest running under Oracle VirtualBox. So the QVPN
application itself is OK, and the problem is related somehow to Wine or various
underlying services.
On the attached screenshot the DetectEnvStatus popup appears immediately when I
attempt to connect the VPN. If I use the IP address of the gateway router I am
connecting to in lieu of the DDNS domain name, QVPN will create the VPN, but
the tunnel verification ping test fails and the tunnel will not transmit data,
which is why the "remote gateway not responding" message also appears on the
screenshot. If I specify the DDNS domain name of the remote gateway router,
the VPN tunnel is not established (not shown), suggesting a dynamic DNS
name-to-IP address resolution related problem in Wine.
Any help would be appreciated.
--
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=39881
Bug ID: 39881
Summary: d3dx9_36/tests/mesh.ok: failed on line 4145 Test text
Product: Wine
Version: 1.9.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: litimetal(a)gmail.com
Distribution: ---
Created attachment 53245
--> https://bugs.winehq.org/attachment.cgi?id=53245
terminal_output.txt
run $ make mesh.ok, got
mesh.c:4145: Test failed: Test text ('wine', 1.000000, 0.000000), glyph 4, face
280 normal, result (0, -0, -1), expected (0, 0, 1)
Is this related to bug 28810?
--
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=39712
Bug ID: 39712
Summary: AirDC++: Crash after finishing setup wizard
Product: Wine
Version: 1.8-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: archee(a)tuta.io
Distribution: ---
Created attachment 52965
--> https://bugs.winehq.org/attachment.cgi?id=52965
wine terminal output
In the setup wizard, when it says "The wizard has completed successfully", then
press Cancel (Next doesn't work), now it will show splash screen and then a
dialog "AirDC++ just encountered a fatal bug and should have written
exceptioninfo.txt the same directory as the executable"
Download:
https://github.com/airdcpp/airgit/releases/download/3.00/AirDC_Installer_3.…
$ sha1sum AirDC_Installer_3.00.exe
bdaef50c9388135b9e326ea03118a1254f2ecd82 AirDC_Installer_3.00.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=43203
Bug ID: 43203
Summary: Crashing Devil Mac Cry 5
Product: Wine-staging
Version: 2.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tall89(a)mail.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
WINEDEBUG=fixme-all,err+loaddll,err+dll,err+file,err+reg
------ Program jamp.exe ------
err:seh:setup_exception_record stack overflow 1312 bytes in thread 014b eip
7bc68356 esp 01330e10 stack 0x1330000-0x1331000-0x1b30000
--
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=23950
Summary: MPQEdit: Opening a folder results in the wrong error
message
Product: Wine
Version: 1.3.0
Platform: x86
URL: http://zezula.net/download/mpqediten32_beta.zip
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: adys.wh(a)gmail.com
Attachment #30066 showcases the expected error message ("The system cannot find
the path specified"). Instead, running wine mpqedit c:\\ results in "Access
denied" error message.
--
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=42436
Bug ID: 42436
Summary: Wine Wiki: Building Wine - Memory & Address Checkers
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wylda(a)volny.cz
Distribution: ---
I don't know, if anyone tried recently follow wiki link:
https://wiki.winehq.org/Building_Wine#Memory_.26_Address_Checkers
This link mentions "...you only need to pass the -fsanitize=address flag to the
compiler when building"
../wine-source/configure CFLAGS="-g -O1 -fsanitize=address -other-flags"
But this fails soon in make_xftmpl.o: In function fatal_error':
..../tools/make_xftmpl.c:116: undefined reference to
`__asan_option_detect_stack_use_after_return'
..../tools/make_xftmpl.c:116: undefined reference to `__asan_stack_malloc_1'
Passing LIBS="-lasan" to configure fixes this, but build fails anyway at cca
63%:
..../dlls/ntdll/loader.c:2979: undefined reference to `pthread_sigmask'
Per some gentoo wiki:
Some configure scripts test the need of the -lpthread compiler flag by testing
whether the function pthread_create() is available without it. The Address
Sanitizer library (libasan) provides this function. However it does not have a
full pthread implementation, more advanced pthread functions aren't provided.
Therefore the compilation fails. A workaround is to add the -lpthread compiler
flag manually.
Passing LIBS="-lasan -lpthread" to configure fixes this issue, but anyway fails
at the end:
../tools/sfnt2fon/sfnt2fon -o coue1255.fon ../../wine_git_src/fonts/courier.ttf
-d 128 13,1255,8
Makefile:174: recipe for target 'coue1255.fon' failed
==16755==ASan runtime does not come first in initial library list; you should
either link runtime to your application or manually preload it with LD_PRELOAD.
make[1]: *** [coue1255.fon] Error 1
make: *** [fonts] Error 2
Did anyone tried to follow that Wiki? I tried that on Debian Stretch.
Gcc (Debian 6.3.0-6) 6.3.0 20170205
--
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=39380
Bug ID: 39380
Summary: test.winehq.org: Provide a way to know why a report
was rejected
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
When WineTest submits a report that report can get thrown away. Either because
it's too big, because it has too many failures, because too many tests were
skipped or because of other reasons unknown.
The WineTest.exe is never notified of this because the report analysis is run
asynchronously with respect tot he submission process. But annoyingly there is
no way for the submitter to know why the report was rejected even later,
levaing him to guess as to what needs fixing.
One way to plug this hole would be to send an email with the reason to the
address field in the report. But that could probably be abused to send emails
to arbitrary persons.
A very simple alternative would be to create a per-commit text file containing
one line per ignored report with the report's tag, timestamp of when it was
analyzed and the reason why it was ignored.
--
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.