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=25215
Summary: GetVolumePathNamesForVolumeNameA function not
implemented
Product: Wine
Version: 1.3.6
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kelytharun(a)gmail.com
wine: Call from 0x7bc4ba90 to unimplemented function
KERNEL32.dll.GetVolumePathNamesForVolumeNameA, aborting
I think the summary and this line says all.
Link to MSDN entry about the function:
http://msdn.microsoft.com/en-us/library/aa364998(VS.85).aspx
--
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=25111
Summary: Firefox 4 Beta 7: Starts but doesn't render the
program (menu/toolbars/browserarea)
Product: Wine
Version: 1.3.6
Platform: x86
URL: http://www.mozilla.com/products/download.html?product=
firefox-4.0b7&os=win&lang=en-US
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andreas.boggild(a)gmail.com
Firefox 4 Beta 7 seems to install correctly and also starts without errors, but
it fails to actually render the program inside the window decorations.
The title in the window decoration still shows that the program is functional
(though invisible), as I it updates with a new title if I go to a new page
(using Crtl+L shortcut and type the address blindly) or open a new tab
(Crtl+T).
Beta 6 works fine and I believe one of the changes to Beta 7 was the
introduction of GPU acceleration by default, which I suggest could be causing
the problem, though I'm not sure. I'm using Ubuntu 10.10 with a Radeon X1300
Mobility and the default open source driver from the distribution. In case it
is the GPU acceleration causing problems, I guess it could be a bug in the
driver instead?
--
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=24050
Summary: sparc/linux: port.c:189:2: error: #error You must
implement wine_switch_to_stack for your platform
Product: Wine
Version: 1.3.0
Platform: sparc
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: enhancement
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Hard to compile wine with it :-).
Apparently I'm not the only crazy one:
http://www.winehq.org/pipermail/wine-users/2008-November/044104.html
Though, I'm on Linux/Sparc, using qemu + debian etch:
http://www.aurel32.net/info/debian_sparc_qemu.php
Is Sparc considered a supported platform? If so, I suppose this would be a
blocker, but I have the feeling it's not (though there's quite a bit of code
for it already), so I'm marking it as an enhancement.
--
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=24649
Summary: crash with certification path
Product: Wine
Version: 1.3.4
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nerv(a)dawncrow.de
using inetcpl to browse certificates.
weird thing is i have a "Juan Lang" certificate...
try to see the certification path leads to crash
should i attach that certificate?
--
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=24722
Summary: LibreOffice 3.3.0 Beta misses msvcr90 func/var
Product: Wine
Version: 1.3.4
Platform: x86-64
URL: http://www.documentfoundation.org/download/
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: msvcrt
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nerv(a)dawncrow.de
When typing Text into LibreOffice Writer (Build 9526) it crashes with:
Unhandled exception: unimplemented function msvcr90.dll.__tzname called in
32-bit code (0x7ed9c497).
I guess __tzname (with two underlines) is not a function, but is like _tzname
(with one underline).
I already tried replacing the stub in the specfile of msvcr90 with:
@ extern __tzname msvcrt._tzname
But then it silently dies when typing...
--
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=24952
Summary: dlls/user32/button.c handles incorrectly unknown
button types
Product: Wine
Version: 1.3.6
Platform: x86
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mity(a)morous.org
Created an attachment (id=31597)
--> (http://bugs.winehq.org/attachment.cgi?id=31597)
code demonstrating the difference
When an unknown/unsupported button type is specified (e.g. BS_SPLITBUTTON or
BS_DEFSPLITBUTTON), creation of button control fails in Wine.
In contrary on Windows it suceeds (even though the created control then behaves
incorrectly) whenever BS_[DEF]SPLITBUTON is not supported. Tested on Windows
2000, Windows XP, Windows 7 (with program without manifest, so comctl32 6.0 was
NOT used).
The behavior difference in effect prevents mCtrl split button emulation from
working (see http://sourceforge.net/projects/mctrl/). The MCTRL.DLL provides a
split button as a subclass of standard BUTTON window class.
When needed (i.e. COMCTL32 < 6.0), the split buttons are handled by the code in
MCTRL.DLL implementation. This works perfectly on Windows, but not within Wine
for the reason described above.
The behavior difference can be tested with the attached code: On Windows the
two buttons are created successfully (even they misbehave), on Wine the two
CreateWindow calls fail.
Obviously the reason is the test:
if (btn_type >= MAX_BTN_TYPE)
return -1; /* abort */
in dlls/couser32/button.c:260.
There are probably also other related problems (e.g. in BM_SETSTYLE) etc.
--
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.