http://bugs.winehq.org/show_bug.cgi?id=16227
Summary: Tooltips on mouse hover in EMS SQL Manager block the
mouse click
Product: Wine
Version: 1.1.9
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P1
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ksfreitas(a)gmail.com
Created an attachment (id=17473)
--> (http://bugs.winehq.org/attachment.cgi?id=17473)
Screenshot of a tooltip bloocking the mouse click
In EMS SQL Manager (Free and Full), the tooltips block the mouse click, having
to resize to see all item without tooltip for click. The link for freeware
software download:
http://www.sqlmanager.net/en/products/postgresql/manager/download
--
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=27502
Summary: app freezes when WM_KILLFOCUS creates modal dialog
Product: Wine
Version: unspecified
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: efrias(a)syncad.com
Created an attachment (id=35159)
--> (http://bugs.winehq.org/attachment.cgi?id=35159)
simple example which produces the error
When a program brings up a modal dialog box in response to a WM_KILLFOCUS
message, the program will freeze. I've attached a simple test case, all
boilerplate except for:
case WM_KILLFOCUS:
MessageBox(hWnd, _T("Killing Focus"), _T("Note"), MB_OK);
in the main event loop. If you run the program and then give focus to another
application, the messagebox will pop up and then the program will become
unresponsive.
What is happening is:
- x11drv gets a FocusOut event and calls the event handler, which ends up
SendMessage-ing a WM_KILLFOCUS to the program.
- The programs's code creates a modal dialog like the MessageBox above, and
enters the dialog's event loop, which winds up calling GetMessage which calls
MsgWaitForMultipleObjectsEx to get more X11 events.
- X11DRV_MsgWaitForMultipleObjectsEx executes this:
if (data->current_event) mask = 0; /* don't process nested events
*/
where data->current_event is true since we're still handling the FocusOut
event. Since we're not processing nested events, we'll never be able to
process the usual events like keys or mouse events which could exit this nested
event loop.
This type of error occurs in a few places in our application, where a
WM_KILLFOCUS message to an edit box triggers some input validation and displays
an error on failure. This works correctly in the normal case, where the user
tabs out or clicks on another control in the dialog box containing the edit
control -- since everything stays in the same top-level window, there is no
FocusOut event from X11 and the WM_KILLFOCUS is generated internally by wine in
response to, say, a KeyEvent. I think these key or mouse events are just
posted to the windows message queue, and the X11 event handler has already
exited by the time the application gets around to processing the ensuing
WM_KILLFOCUS. But in the case where focus is lost by clicking outside the
dialog containing the edit control, the WM_KILLFOCUS is generated by the
FocusOut handler which is still executing, and we lock up.
I suspect this is related to bug 11595 "Notepad++ freezes if native application
changes a file it has open (dogfood)". My guess is in that case, a FocusIn
event triggers something like a WM_ACTIVATE, in which notepad++ notices a file
is changed and displays a messagebox asking if you want to reload. Since wine
is still processing the FocusIn event, the modal message loop's call to
MsgWaitForMultipleObjectsEx will never process any useful events because it's a
nested event. Our application's built-in text editor has this same problem.
I don't understand the event handling code well enough to propose a solution.
As a test, I allowed nested event processing and it solved the problem without
introducing any obvious errors, but I'm sure that check was in there for a
reason. It's probably better to keep the application code from being executed
from inside the event handler, if that's possible.
Note: this bug was also posted as a message to wine-devel here:
http://www.winehq.org/pipermail/wine-devel/2011-June/090652.html
--
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=32058
Bug #: 32058
Summary: Guild Wars 2 launcher freezes/hangs (unable to launch
game)
Product: Wine
Version: 1.5.15
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: x.egam.wodahs.x(a)gmail.com
CC: julliard(a)winehq.org
Classification: Unclassified
Once I updated wine to version 1.5.15, the Guild Wars 2 launcher can no longer
launch the game because it just freezes/hangs. This was not an issue in 1.5.14,
and in order to run the game for now I'm using wine 1.5.14 compiled from
source.
In wine 1.5.14, the launcher is black (can't see UI at all, but it's still
functional) unless using the -dx9single flag. Using -dx9single, the background
is black instead of transparent but the UI inside is properly rendered. This
information is important because, before submitting this bug report, I
performed two separate git bisects between 1.5.14 and 1.5.15: one without any
command-line parameters, and one using -dx9single.
Technical details follow:
=======================================================================
1) git bisect for running the game without any parameters:
In the last good commit (8dcbeff760115834656f3f1fc85922e3a9af14d0), the
launcher is still black but it still works. You cannot see the UI but by
blindly logging in, the game does launch. In the first bad commit
(f12c1c6630f0bf842dde9af10da4ab188ff16e94), the behavior is different from the
wine 1.5.15 release and the other commits tested: here, instead of locking up,
the window just disappears. It's still there, but I guess it's fully
transparent. Because this leaves us even more "blind", I considered this "bad"
in the git bisect, yielding the following result:
---
f12c1c6630f0bf842dde9af10da4ab188ff16e94 is the first bad commit
commit f12c1c6630f0bf842dde9af10da4ab188ff16e94
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Sep 26 13:12:17 2012 +0200
winex11: Switch to an ARGB visual for layered windows with per-pixel alpha.
:040000 040000 e9933c28f3e50c52d2cee37a43b06a2f5cb5a497
3870099a31a68a69cd7c022857794700c2343aa9 M dlls
---
If, however, we consider f12c1c6630f0bf842dde9af10da4ab188ff16e94 "good" in the
git bisect, we get:
---
d8247efd5ecb8c4604624eb2bbf47e194ce59e7e is the first bad commit
commit d8247efd5ecb8c4604624eb2bbf47e194ce59e7e
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Thu Sep 27 20:47:08 2012 +0200
winex11: Take the alpha channel into account to compute the region of
layered windows.
:040000 040000 3870099a31a68a69cd7c022857794700c2343aa9
d9ec62b63405f910db90b095145a7910cc124eef M dlls
---
In this case, the launcher does indeed lock up in the first bad commit
(d8247efd5ecb8c4604624eb2bbf47e194ce59e7e).
2) git bisect for running the game using -dx9single:
Using the -dx9single flag, we seem to be able to get to a later commit before
it stops working (but does not work in the 1.5.15 release). In the last good
commit (dbff4f422c943a837f0098e921f831eb4a94ac11), everything seems to be fine
(when using the -dx9single flag) and even the transparency seems to be working.
However, in the first bad commit (6f3b097a203d9ca248732cb45eed462599ca3af1),
things start to lock up. This yields the following git bisect result:
---
6f3b097a203d9ca248732cb45eed462599ca3af1 is the first bad commit
commit 6f3b097a203d9ca248732cb45eed462599ca3af1
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Oct 3 00:09:01 2012 +0200
winex11: Fix a typo in the surface region computation with an alpha
channel.
:040000 040000 fa11ac3c80763b81911ba999d8302029d2c6d147
566c9c06b11f8785c870a1e09ec53d42e13d1524 M dlls
---
--
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=21987
Summary: Acrobat 7 tryout complains: This Postscript Driver or
Windows Platform (Win9x/Me) not supported
Product: Wine
Version: 1.1.40
Platform: x86
URL: http://www.adobe.com/products/acrobatpro/tryreg.html
OS/Version: Linux
Status: NEW
Keywords: download
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jeffz(a)jeffz.name
When installing the Acrobat 7 trial AcTR7EFG.exe, the installer produces a
dialog:
Devmode
This Postscript Driver or Windows Platform (Win9x/Me) not supported
It doesn't prevent the installer from progressing, but the same thing doesn't
happen on Vista.
--
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=23237
Summary: DirectX SDK Nov 2006 unzip progress bar full of
symbols
Product: Wine
Version: 1.2-rc3
Platform: x86
URL: http://www.microsoft.com/downloads/details.aspx?displa
ylang=en&FamilyID=c72d9f1e-53f3-4747-8490-6801d8e8b4ef
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
The winzip self-extractor's progress bar should show the filename
being extracted, but it's in a funny symbol font.
--
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=11661
Summary: Confusing error message when executing application on
noexec fs
Product: Wine
Version: 0.9.55.
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: ntoskrnl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquid.acid(a)gmx.net
Hi there,
I'm suggesting to make some checks prior to loading and executing applications.
The problem I encountered yesterday was that when trying to start applications
from a filesystem with the noexec parameter enabled the whole app pagefaults.
That was really my mistake because I accidentally changed some lines in the
fstab after changing the encryption engine of my system. I only have the exec
parameter enabled on the games filesystem, all other data filesystem don't have
it enabled.
It would be a good thing to output a somehow more informative error message
when such a configuration is encountered (executing code from noexec fs).
I suggest this because I was quite confused seeing the application to pagefault
that was running two days ago (and I didn't do any package updates in these two
days).
Thanks,
Tobias
--
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=14025
Summary: Heroes of Might Magic V: camera does not move well
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P5
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mkstoyanov(a)hotmail.com
Heroes of Might and Magic V (original) and HOMMV: Hammers of Fate, on should be
able to swing the camera left and right by pressing the right mouse button and
move the mouse. It works under windows. In wine (9.58 on, until 1.0 inclusive)
the camera moves only barely, in order to make a 90 degree change of view, I
need to swipe the mouse over the pad several time, in windows I can make 180
with half a pad. The game has no mouse sensitivity option. (camera moves
normally from the keyboard, so the game still plays OK)
--
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=28254
Summary: Problem with activation program pm_fastrack-pmp.exe
Product: WineHQ Apps Database
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lavir.2010(a)gmail.com
After installing the program pm_fastrack_pmp version 6.0 when trying to enable
execution of the program he presents an information stating that the
program-pm_fastrack pmp.exe found a serious problem and needs to close.
--
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=35824
Bug ID: 35824
Summary: UltraISO 'ISODrive.sys' crashes in entry point (SCM
doesn't start SERVICE_FILE_SYSTEM_DRIVER type services
with winedevice hosting process)
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Hello folks,
found during bug 35755
--- snip ---
$ WINEDEBUG=+tid,+seh,+relay,+winedevice,+ntoskrnl,+service wine ./uiso9_pe.exe
>>log.txt 2>&1
...
0016:Call KERNEL32.CreateNamedPipeW(00119d70
L"\\\\.\\pipe\\net\\NtControlPipe2",40000003,00000000,00000001,00000100,00000100,00002710,00000000)
ret=7eded4ac
0016:Ret KERNEL32.CreateNamedPipeW() retval=000000d8 ret=7eded4ac
...
0016:Call KERNEL32.ExpandEnvironmentStringsW(0011a038 L"C:\\Program
Files\\UltraISO\\drivers\\ISODrive.sys",00000000,00000000) ret=7edecacd
0016:Ret KERNEL32.ExpandEnvironmentStringsW() retval=0000002f ret=7edecacd
...
0016:Call KERNEL32.ExpandEnvironmentStringsW(0011a038 L"C:\\Program
Files\\UltraISO\\drivers\\ISODrive.sys",00119d70,0000002f) ret=7edecb39
0016:Ret KERNEL32.ExpandEnvironmentStringsW() retval=0000002f ret=7edecb39
0016:Call KERNEL32.CreateProcessW(00000000,00119d70 L"C:\\Program
Files\\UltraISO\\drivers\\ISODrive.sys",00000000,00000000,00000000,00000400,00540000,00000000,0084e4c8,0084e50c)
ret=7edecd84
...
0037:Call KERNEL32.__wine_kernel_init() ret=7bc5a3aa
0016:Ret KERNEL32.CreateProcessW() retval=00000001 ret=7edecd84
...
0037:Starting process L"C:\\Program Files\\UltraISO\\drivers\\ISODrive.sys"
(entryproc=0x253b3f)
0037:trace:seh:raise_exception code=c0000005 flags=0 addr=0x2537a9 ip=002537a9
tid=0037
0037:trace:seh:raise_exception info[0]=00000000
0037:trace:seh:raise_exception info[1]=00000061
0037:trace:seh:raise_exception eax=00000061 ebx=00000000 ecx=0000bb40
edx=7edfefe4 esi=7edd4ce0 edi=00251d4c
0037:trace:seh:raise_exception ebp=0035fe20 esp=0035fd5c cs=0023 ds=002b
es=002b fs=0063 gs=006b flags=00010246
...
--- snip ---
The random crashes during relay trace are the result from the driver entry
point accessing the second parameter which ought to be 'RegistryPath.
The binary is started as plain win32 process (not loaded in winedevice hosting
process) hence the driver entry point params are not setup.
The kernel driver is a file system driver service, currently not handled with
Wine's service manager.
MSDN:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms682450%28v=vs.85%…
--- quote ---
dwServiceType [in]
The service type. This parameter can be one of the following values.
Value Meaning
SERVICE_ADAPTER 0x00000004
Reserved.
SERVICE_FILE_SYSTEM_DRIVER 0x00000002
File system driver service.
SERVICE_KERNEL_DRIVER 0x00000001
Driver service.
SERVICE_RECOGNIZER_DRIVER 0x00000008
Reserved.
SERVICE_WIN32_OWN_PROCESS 0x00000010
Service that runs in its own process.
SERVICE_WIN32_SHARE_PROCESS 0x00000020
Service that shares a process with one or more other services. For more
information, see Service Programs.
--- quote ---
Registry export of driver service:
--- snip ---
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ISODrive]
"DisplayName"="ISO DVD/CD-ROM Device Driver"
"ErrorControl"=dword:00000000
"ImagePath"="C:\\Program Files\\UltraISO\\drivers\\ISODrive.sys"
"ObjectName"="LocalSystem"
"PreshutdownTimeout"=dword:0002bf20
"Start"=dword:00000001
"Type"=dword:00000002
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ISODrive\Parameters]
"AutoMount"=dword:00000001
"ExcludeDrives"="CDEZ"
--- snip ---
Type -> 0x2 -> SERVICE_FILE_SYSTEM_DRIVER
Source:
http://source.winehq.org/git/wine.git/blob/debd1346b003ae34013a04318e7105f8…
--- snip ---
606 static DWORD service_start_process(struct service_entry *service_entry,
HANDLE *process)
607 {
...
634
ExpandEnvironmentStringsW(service_entry->config.lpBinaryPathName,path,size);
635
636 if (service_entry->config.dwServiceType == SERVICE_KERNEL_DRIVER)
637 {
638 static const WCHAR winedeviceW[] =
{'\\','w','i','n','e','d','e','v','i','c','e','.','e','x','e',' ',0};
...
--- snip ---
$ sha1sum uiso9_pe.exe
77d93c41f45530e58892b276a3fa92c7128b7539 uiso9_pe.exe
$ du -sh uiso9_pe.exe
4.2M uiso9_pe.exe
$ wine --version
wine-1.7.14-185-g5cf20ce
Regards
--
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.