http://bugs.winehq.org/show_bug.cgi?id=15950
Summary: wine won't build with bison 2.4
Product: Wine
Version: 1.1.8
Platform: Macintosh
OS/Version: Mac OS X 10.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine-2008(a)ryandesign.com
With bison 2.3 installed (using MacPorts), wine bulids, but with bison 2.4, it
doesn't. It says:
/usr/bin/gcc-4.0 -c -I. -I. -I../../include -I../../include -D__WINESRC__
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -I/mp/include -O2
-o parser.tab.o parser.tab.c
parser.y: In function 'parser_parse':
parser.y:320: error: parse error before '}' token
make[2]: *** [parser.tab.o] Error 1
make[1]: *** [jscript] Error 2
make: *** [dlls] Error 2
Here is the MacPorts project's ticket about this issue:
http://trac.macports.org/ticket/17135
Here's a description of a backwards-incompatible change made in bison 2.4 by
the developer of pure, another program that won't build with bison 2.4
(actually I don't know if that's the same reason wine won't build):
http://groups.google.com/group/pure-lang/browse_thread/thread/60593b93dc8fc…
--
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=15944
Summary: mountmgr only assign drive letters for up to two
removable devices
Product: Wine
Version: 1.1.8
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: regression
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
It used to be the case that if hal reports a device as a floppy, it gets
assigned to a: or b:, otherwise, the device gets assigned a drive letter
between c and z.
With the changes in mountmgr just before Wine 1.1.7, all removable devices that
are not cdroms are limited to a: or b:, which means if I hot-plug 3 usb thumb
drives, the third one does not get a drive letter.
--
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=19877
Summary: Zeta Minibrowser crashes (because of stubbed
CreateHardLinkW)
Product: Wine
Version: 1.1.28
Platform: PC
URL: http://www.brothersoft.com/zeta-minibrowser-110447.htm
l
OS/Version: Linux
Status: NEW
Keywords: dotnet, download
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xerox_xerox2000(a)yahoo.co.uk
I've seen this bug in more apps, so probably a bug covering several
applications
Prerequisites:
'winetricks dotnet20'
The mini-browser crashes after CreateHardLinKW is printed in the console.
Returning TRUE instead of false, or setting last error in CreateHardlink to
ERROR_ALREADY_EXISTST makes the app start fine, but that's just a hack, somehow
we should have more then this stub, to get the app running. I'll attach console
info hereafter
--
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=15452
Summary: Freewire aborts due to incorrect handling of COLORRES
nIndex in winex11's GetDeviceCaps()
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://www.freewiretv.com/downloadTVWin.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nodisgod(a)yahoo.com
Created an attachment (id=16345)
--> (http://bugs.winehq.org/attachment.cgi?id=16345)
Freewire relay log (rzipped)
With current Git (wine-1.1.5-207-gc425c8a), when attempting to launch Freewire
after installation, Freewire aborts with a message box complaining about the
currently set bit depth. From relay trace:
0009:Call user32.GetDC(00000000) ret=005808ac
0009:Ret user32.GetDC() retval=0000030c ret=005808ac
0009:Call gdi32.GetDeviceCaps(0000030c,0000006c) ret=005808b5
0009:Ret gdi32.GetDeviceCaps() retval=00000000 ret=005808b5
0009:Call user32.LoadStringA(00000000,00000095,0032f8d4,00000180) ret=005808f3
0009:Ret user32.LoadStringA() retval=0000015d ret=005808f3
0009:Call user32.LoadStringA(00000000,00000097,0032f754,00000180) ret=00580910
0009:Ret user32.LoadStringA() retval=0000001c ret=00580910
0009:Call user32.MessageBoxA(00000000,0032f8d4 "Unfortunately, it has not been
possible to start Freewire Television due to your graphics mode.\nPlease set
the color depth to 32 bit in the display control panel and restart the
application\nIf the problem continues please contact Freewire customer services
on 0333 123 0190.\nOr visit the Freewire s"...,0032f754 "We've encountered a
problem!",00000030) ret=00580927
The problem seems to lie in:
0009:Call gdi32.GetDeviceCaps(0000030c,0000006c) ret=005808b5
0009:Ret gdi32.GetDeviceCaps() retval=00000000 ret=005808b5
GetDeviceCaps() is being called with the DC handle returned from GetDC(NULL)
and the COLORRES value for nIndex. In dlls/winex11.drv/init.c lines 259 and
268:
case COLORRES:
/* ... */
return 0;
Freewire apparently does not like the returned value, and thus aborts with the
message box. Modifying the COLORRES case to return screen_bpp allows the
application to get past this point, though I am not sure if this is the right
thing to do.
--
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=19064
Summary: Microsoft Security Essentials Setup crashes missing
QueryAllTracesW
Product: Wine
Version: 1.1.24
Platform: PC-x86-64
URL: http://www.microsoft.com/security_essentials/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: advapi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nerv(a)dawncrow.de
The Setup of Microsoft Security Essentials(Virus-Scanner) is trying to call
Unimplemented function ADVAPI32.dll.QueryAllTracesW
Then it crashes.
--
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=19105
Summary: From VB / VBScript / maybe others, the TimeSerial
function dont answer like is awaited
Product: Wine
Version: 1.1.24
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: slezica(a)yahoo.com
I determine this problem after a hard hunt.
This issue affects software from several sources, probably silently.
In Visual Basic 6 and VBScript, you have a function "TimeSerial" for convert
three integers (hour, minute and second) to a "date/time" format ("HH:MM:SS",
for example 03:45:12).
On Windows, you can use the arguments without ranges, for example 300 minutes
- "TimeSerial(0,300,0)" -, and it automatically converts and displays the
result correctly (in this case "05:00:00", 5 hours).
In Wine, if you pass the same previous example it returns "Error 5 - Invalid
procedure call or argument.". The function work if you pass for example minutes
in the 0-59 range. But the conversion functionality is missing (and give a
error).
I can't determine what DLL is used, but shure is shared with others Microsoft
Visual Studio tools.
The debug don't show any relevant information, because is not a Wine error
really (ony the answer is different).
Thanks, and if I can help more only say.
Excuse my english.
Sebastián Lezica
--
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=19430
Summary: winedump: null pointer dereference in spec mode
Product: Wine
Version: 1.1.26
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P5
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tillmann.werner(a)gmx.de
Created an attachment (id=22556)
--> (http://bugs.winehq.org/attachment.cgi?id=22556)
diff against git that solved the problem
I think a null pointer dereference may occur when running winedump in spec
mode. I encountered a segmentation fault when invoking ./winedump spec -c
/tmp/poly/poly.dll -I /tmp/poly/. The reason seems to be line 1598 in
tools/winedump/pe.c where dll_current_symbol may be NULL. This affects version
1.1.26 as well as a fresh git checkout. The attached URL contains a quick hack
that worked for me but certainly requires review from somebody more familiar
with the code.
--
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=19778
Summary: cmd set "FOO=bar" does the wrong thing; breaks firefox
build script
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
The firefox build scripts do
SET "PATH=%PATH%;%MOZ_TOOLS%\bin"
On Wine, this sets the bizarre environment variable "PATH.
--
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=19851
Summary: interlocked* functions unimplemented for ARM
Product: Wine
Version: 1.1.28
Platform: Other
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Long story short, someone on #winehq asked how wine was on ARM (in case
Microsoft started supporting Windows on ARM). Out of curiosity, I got Debian on
ARM for QEMU, got wine source, installed deps, and went along.
First show stopper:
interlocked.c:389:3 error: #error You must implement the interlocked* functions
for your CPU
--
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=18073
Summary: VB6 Format decimal error
Product: Wine
Version: 1.1.18
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: oleaut32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gabmoa(a)yahoo.it
CC: damjan.jov(a)gmail.com
Created an attachment (id=20475)
--> (http://bugs.winehq.org/attachment.cgi?id=20475)
test program
I had posted bug 15387 (fixed) for a problem in VB6 Format but I find there is
another problem in the Wine VarFormat function.
MASK=#.###
INPUT RESULTS
LINUX WIN
0.099 0.099 0.099 -> ok
0.0999 0.099 0.1 -> wrong
0.09999 1.000 0.1 -> wrong!!
0.099999 1.000 0.1 -> wrong!!
MASK=#.####
INPUT RESULTS
LINUX WIN
0.099 0.099 0.099 -> ok
0.0999 0.0999 0.0999 -> ok
0.09999 0.09999 0.1 -> wrong
0.099999 1.000 0.1 -> wrong!!
0.099999 1.000 0.1 -> wrong!!
In attachment there is a VB6 test program used to get these results.
All the cases must have the same behaviour
Thank you
--
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.