http://bugs.winehq.org/show_bug.cgi?id=5852
heiko(a)kom.at changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|NoAppDBEntry |
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5846
------- Additional Comments From alex(a)thehandofagony.com 2006-05-08 06:51 -------
Have you enabled the apropriate mouse grab option in winecfg?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5863
Summary: automating binary packages build for each release
Product: Wine
Version: 0.9.18.
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-ports
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jerome.bouat(a)wanadoo.fr
I wonder if binary packages could not be automatically build each time a new
wine version is released.
I mostly test applications running with Wine. I always have to wait for binary
packages before I can test a new release. At the present time, the delay before
I can test is made of the delay that the binary package maintainer needs plus
the delay that I need according to my diary.
What already appened to me (dates are not true) :
- day 1 : A developper asks me for a new test
- day 7 : I see the message and check for a new release.
A new version was released at day 6
but no binary package is yet available.
I wait the binary package.
- day 12 : A new binary package is build.
- day 15 : I see that a new package is available.
- day 21 : I have time to perform the test
but I see a new release is available.
Thus I wait for a new binary package.
According to possibly side effects of one bug fixing, this highly decreases the
global wine bugs fixing efficiency.
I mean the binary package maintainer would always have a key role. When the
maintainer is not available, a default package could be generated with the
specification file of the latest release (but the version number). You could
wait 1 day before you automatically generate the binary package. This give a
chance for the maintainer to proprely generate its own one.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5558
------- Additional Comments From grahame(a)regress.homelinux.org 2006-05-08 04:13 -------
I get the following for the latest cvs version of wine with dk2 1.7 with nocd
crack applied:
$ wine explorer.exe /desktop=name winedbg Dkii.exe
WineDbg starting on pid 0xc
fixme:dbghelp:elf_load_debug_info_from_map Alpha-support for Dwarf2 information
for kernel32<elf>
start_process () at /home/grahame/wine/dlls/kernel/process.c:822
0x7eec6427 start_process+0xe7 [/home/grahame/wine/dlls/kernel/process.c:822] in
kernel32: movl %edi,0x0(%esp)
822 ExitProcess( entry( peb ) );
Wine-dbg>c
fixme:vxd:VXD_Open Unknown/unsupported VxD L"sice.vxd". Try setting Windows
version to 'nt40' or 'win31'.
fixme:vxd:VXD_Open Unknown/unsupported VxD L"siwvid.vxd". Try setting Windows
version to 'nt40' or 'win31'.
fixme:vxd:VXD_Open Unknown/unsupported VxD L"ntice.vxd". Try setting Windows
version to 'nt40' or 'win31'.
First chance exception: page fault on read access to 0x00000000 in 32-bit code
(0x004262a2).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:006b GS:0063
EIP:004262a2 ESP:0034da8c EBP:0034dad8 EFLAGS:00010246( - 00 -RIZP1)
EAX:80304000 EBX:00000001 ECX:0034db00 EDX:0034dbd0
ESI:00000000 EDI:00400000
Stack dump:
0x0034da8c: 00400000 7eece250 0034dad8 0034daac
0x0034da9c: 00000001 0034dbd0 0034db00 00001010
0x0034daac: 00400000 7eece250 00000001 00001010
0x0034dabc: 00000023 fae4ff41 40001000 00008030
0x0034dacc: 00000000 fae4f131 00000002 0034db9c
0x0034dadc: 0042641f 00001010 0034db00 00400000
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for c0000119
Backtrace:
=>1 0x004262a2 in dkii (+0x262a2) (0x004262a2)
2 0x0042641f in dkii (+0x2641f) (0x0042641f)
3 0x00422d9c in dkii (+0x22d9c) (0x00422d9c)
4 0x00421e56 in dkii (+0x21e56) (0x00421e56)
5 0x0042111e in dkii (+0x2111e) (0x0042111e)
6 0x00420bea in dkii (+0x20bea) (0x00420bea)
7 0x0042087e in dkii (+0x2087e) (0x0042087e)
8 0x00422506 in dkii (+0x22506) (0x00422506)
9 0x0040e279 in dkii (+0xe279) (0x0040e279)
10 0x004169b2 in dkii (+0x169b2) (0x004169b2)
11 0x7eec642c start_process+0xec(arg=0x0)
[/home/grahame/wine/dlls/kernel/process.c:822] in kernel32 (0x7eec642c)
fixme:dbghelp:elf_load_debug_info_from_map Alpha-support for Dwarf2 information
for libwine.so.1
12 0xf7e31677 wine_switch_to_stack+0x17 in libwine.so.1 (0xf7e31677)
0x004262a2: movl 0x0(%esi),%edi
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5856
------- Additional Comments From ekkehard.morgenstern(a)onlinehome.de 2006-05-08 02:29 -------
One thing I noticed about the Ctrl-C signal handler is, that the comment states
that it can get run from a system signal handler. On UNIX-like systems (like
GNU/Linux, AIX, Solaris), signal handling is implemenented very differently. The
lowest common denominator is "don't do anything more than setting a flag". This
is especially true on GNU/Linux, where signal handling varies between kernel
versions. While Kernel 2.6 has native threads, Kernel 2.4 doesn't, which also
changes the way signals are handled. Wine's console module starts a thread in a
signal handler, which is not allowed, and leads to a crash (at least on Kernel
2.6). The right way to do it would be to start a thread when the console is
opened that periodically checks signal flags set by the console. I.e. the
console signal handler would do nothing more than setting a flag, and hence
conforming to the signal handler rules of any UNIX-like platform. When I find
time, I will try to make some enhancements to the console.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5859
------- Additional Comments From julliard(a)winehq.com 2006-05-08 02:25 -------
This is very much the right place, he's clearly running on Intel (and in any
case this is the right place for Wine bugs on Power PC too).
Josh, you need to build with a gcc that supports the force_align_arg_pointer
attribute, otherwise the stack isn't properly aligned for the Mac libs.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5280
------- Additional Comments From jeremielapuree(a)yahoo.fr 2006-04-08 23:39 -------
Bug still here with current git (2006-08-05).
Joaopa
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4619
------- Additional Comments From yuriy.kozlov(a)gmail.com 2006-04-08 23:37 -------
Created an attachment (id=3174)
--> (http://bugs.winehq.org/attachment.cgi?id=3174&action=view)
WINEDEBUG=+winsock log
This also happens to me. Just tried it with latest wine from git (2006-08-04).
I waited about 5 minutes, and nothing. The game doesn't freeze, but
everything but the scroll bar is disabled.
This also happens in windows, but the timeout is about a minute at most.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5759
jeremielapuree(a)yahoo.fr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From jeremielapuree(a)yahoo.fr 2006-04-08 23:36 -------
fixed with current git (2006-08-05).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5749
jeremielapuree(a)yahoo.fr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From jeremielapuree(a)yahoo.fr 2006-04-08 21:22 -------
With current git (2006-08-05), bug is gone. So, one can close it as marking FIXED.
Joaopa
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.