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.
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.
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.
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.
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.
http://bugs.winehq.org/show_bug.cgi?id=30193
Bug #: 30193
Summary: Crysis Wars ded server doesn't resize with wineconsole
(curses backend)
Product: Wine
Version: 1.4-rc6
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquitsnake(a)gmx.net
Classification: Unclassified
Created attachment 39410
--> http://bugs.winehq.org/attachment.cgi?id=39410
screen
The Crysis Wars dedicated server, when running under wineconsole with the
curses backend, does not resize its viewport. It is stuck at the default 80x25,
even if the terminal is considerably larger (see attachment).
This produces some unexpected output, as some commands expect a larger size but
have to be split over 2 lines via \
My terminal and wineconsole interact just fine, as I have verified with cmd.
It's just this app that sticks to 80x25 no matter what.
On Windows, it would normally spawn a console window with a size of 132x60 (or
less if the desktop resolution can't fit that)
Could it be that wineconsole first starts at 80x25 and only later resizes to
terminal size? In that case, I can imagine that the app polls the size once
during startup and sticks to that, thus limiting itself to 80x25.
--
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=13624
Summary: Lineage 2 - The Chaotic Throne - Hellbound
Product: Wine
Version: 1.0-rc3
Platform: All
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: eryk-rutkowski(a)o2.pl
Created an attachment (id=13604)
--> (http://bugs.winehq.org/attachment.cgi?id=13604)
Log from Terminal
Problem is in Lineage 2 Hellbound and regarding npkycrypt - dll file. This dll
is not work fine and don't recognize keyboard and i can't log in. There is
communicate: "The keyboard security module has failed to load. please exit the
game and try again"
Sorry for my bad english but i'm from other country ;p
--
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=17124
Summary: MSYS installer doesn't pop up cmd window?
Product: Wine
Version: 1.1.13
Platform: Other
URL: http://www.mingw.org/wiki/msys
OS/Version: other
Status: NEW
Keywords: download, Installer, source
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
When install msys, it floods the terminal with:
This is a post install process that will try to normalize betweenyour MinGW
install if any as well as your previous MSYS installs if any. I don't have any
traps as aborts will not hurt anything.Do you wish to continue with the post
install? [yn ] pi.sh: [: ==: unary operator expectedDo you have MinGW
installed? [yn ] pi.sh: [: ==: unary operator expectedWhen you install MinGW I
suggest you install it to C:/mingw(replace C: with the drive of your choice).
Then create an/etc/fstab file with a line that has a value similar to:C:/mingw
/mingwPress ENTER to continue Normalizing your MSYS environment.You
have script /bin/awkYou have script /bin/cmdYou have script /bin/echoYou have
script /bin/egrepYou have script /bin/exYou have script /bin/fgrepYou have
script /bin/printfYou have script /bin/pwdYou have script /bin/rviYou have
script /bin/rviewYou have script /bin/rvimYou have script /bin/viYou have
script /bin/viewMinGW-1.1 has a version of make.exe within it's bin/
directory.Please be sure to rename this file to mingw32-make.exe once youve
echo installed MinGW-1.1 because it\s very deficient in function.Press ENTER to
continue.C:\msys\1.0\postinstall>pause
Press Return key to continue:
Towards the end. It looks like something that should be in a cmd prompt
(haven't tested on windows yet). The line endings are also wrong, but that's
another bug.
--
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=22634
Summary: Yahoo! Widgets will not display EULA
Product: Wine
Version: 1.1.43
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wwarsin(a)gmail.com
Created an attachment (id=27820)
--> (http://bugs.winehq.org/attachment.cgi?id=27820)
$wine YahooWidgets.exe
After the Yahoo! widget engine is install the first time it runs it asks you to
accept the EULA, which will not show... This is kind of hard to explain but its
like the yahoowidgets.exe does open, and you can mouse over the area and you
can click the "I accept" button and it will the go to open the widgetengine
(from what i breifly saw it worked fine)
--
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=11955
Summary: NoteTab Pro 5.5 Cursor Display Issue
Product: Wine
Version: 0.9.57.
Platform: PC
URL: http://www.notetab.com
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lm_hamilton(a)yahoo.com
When the cursor is at the last line of a file and the user presses ENTER to
create a new line, it adds the line, but the cursor does not move. If the user
starts typing, the text and cursor does go on the last line of the file.
I used to have this issue on any file, but for the last several Wine releases,
it has only affected outline files. Outlines are just text files with the
extension otl. If you open the file in a text editor the topic for each outline
starts with H=". I use Slackware 12.0 and Debian.
Other users on the Yahoo Group for NoteTab on Linux are using Ubuntu and have
the display issue at the top and bottom of the file. I have never had it at the
top no matter what I have tried.
Following is a text representation of the problem I have, numbers used for
lines in the file, and a vertical bar "|" used to show the cursor position
after pressing enter to get a new line.
1|Text on line one.
2Line added when press enter.
3Line added when press enter. If you start typing the cursor acts normally and
starts adding text at the beginning of the last line added by pressing enter.
In this example the text is added after "3".
FYI - NoteTab Pro uses a different input control than NoteTab Light or
Standard. Light and Standard use richedit. NoteTab is developed in Delphi. I
have been a NoteTab user for ten years and beta tester for as long. The
anti-cracker controls in NoteTab's trial version may prevent it from working in
Wine.
--
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.