http://bugs.winehq.com/show_bug.cgi?id=1208
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:26 -------
Bug comments restored from Gmane.org:
I get the following error when running Quicken 2000 Delux release 9.0
err:keyboard:X11DRV_ToUnicode (virtKey=9,scanCode=F,keycode=17,state=13)
err:keyboard:X11DRV_ToUnicode Please report: no char for keysym FE20
(ISO_Left_Tab) :
Doesn't seem to affect operation, but may be a symptom of some other
underlying problem
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1209
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:25 -------
Bug comments restored from Gmane.org:
When I attempt to display the portfolio view to view investments, Quicken and/or
wine crash, with the message "unhandled exception".
This bug is repeatable.
Wine exits with a failure status of 5
Error messages:
wine: Unhandled exception, starting debugger...
err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 134672120
400") (2)
Admittedly, I don't have the debugger set up, as I am mainly a user as opposed
to a developer.
Another message, which could be related (doesn't appear to be but thought I
would include for completeness):
**********************
fixme:file:SetFileAttributesW Couldn't set file attributes for existing file
"/mnt/win_c/quickenw/~qw~link.qdt".
Check permissions or set VFAT "quiet" mount flag
fixme:file:SetFileAttributesW Couldn't set file attributes for existing file
"/mnt/win_c/quickenw/~qw~link.qdt".
Check permissions or set VFAT "quiet" mount flag
**************************
I get this message everytime I run Quicken. I checked the permissions on this
file, and they are "777", so should be fine (?).
As long as I don't attempt to examine the portfolio, I never have a problem. I
have successfully entered data and reconciled accounts
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1218
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:22 -------
Bug comments restored from Gmane.org:
During install of Adaytum Analyst on Debian Unstable (Wine 20021219) all goes
well with the setup and it installs Adobe Acrobat fine and launches into the
setup for Analyst. However, midway through the install it throws a
InstallShield error:
995: Internal error in Windows Installer
followed by InstallShield error:
1611: Unable to extract the file (null).
Wine itself never crashes.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1217
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:20 -------
Bug comments restored from Gmane.org:
When I try to print something the job goes to spool but gets aborted. When I
print to file, the generated file is corrupted.
I tested it with several versions of wine from CVS and redhat 7.3 and 8.0 with cups.
All systems I tested prints ok from linux.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1216
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:18 -------
Bug comments restored from Gmane.org:
when trying to run WinBUGS
http://www.mrc-bsu.cam.ac.uk/bugs/winbugs/contents.shtml
using wine, i cannot get the buttons to work properly. Pressing 'Doodle' and
then 'New', and then 'Ok' nothing happens. this means i cannot run the program.
i got some infomation about this behaviour from one reliable source, for which i
quote:
The latest version of wine that works with WinBUGS is wine-20010731.
Everything after that fails because buttons do not respond to being
clicked.
I have no idea what the problem is. I am disappointed that the bug
hasn't been fixed. It must be a very rare bug, only revealed by the
Black Box component framework (which supplies the controls used by
WinBUGS).
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1215
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:15 -------
Bug comments restored from Gmane.org:
(Version in use is actually 20021031, but this error has existed for a long
time, on both -current and -stable, from ports or CVS).
After using any windows binary I've tried with FreeBSD's wine from ports, I
eventually get an error:
wine in malloc(): error: recursive call
It also shows up as "wine in free(): error: recursive call," and sometimes
several of them can show up in the output. The application hangs soon
afterwards (I am guessing it's right when the malloc recursion happens). In
particular I've been trying to use the Exile 3 binary, but with that it happens
after some minutes of play. When I was trying counterstrike it happened very
quickly.
Notable excerpt from the malloc manpage:
recursive call A process has attempted to call an allocation function
recursively. This is not permitted. In particular, signal handlers
should not attempt to allocate memory.
However, I think I've tracked down the mallocs/frees that can happen as a result
of signals. One set (server/registry.c) I patched to not malloc/free. I put in
a printf around the segv handler, and this recursive malloc doesn't appear to be
happening during segv. Would the rforking(RFPROC|RFMEM) cause this?
------- Additional Comments From eta <at> lclark.edu 2003-02-20 18:13 -------
*** This bug has been confirmed by popular vote. ***
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1213
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:11 -------
Bug comments restored from Gmane.org:
I use wine in Russian language environment, and I can see, that it uses
windows-1251 as a default Russian encoding. Of course, it is correct, since
Windows applications usually should work with the windows codepage. Even in
Linux windows-1251 becames more and more popular, since it is really better,
than traditionally used koi8.
But the Cyrillic X11 keysyms, which I input from my keyboard, are recognized by
wine as koi8, and it is strange, since, I think, the keyboard encoding should
match the encoding used for screen. So I recommend to change 20866 to 1251 at
least for one Russian keyboard described in the file keyboard.c (there are 3
Russian keyboards in this file).
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de 2003-01-14
09:43 -------
Just submitted a patch to change the main Russian keyboard's codepage to 1251.
------- Additional Comments From dpaun <at> rogers.com 2003-04-01 00:15 -------
Why was this bug marked FIXED? Reopening.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1211
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:07 -------
Bug comments restored from Gmane.org:
Error Message Pops Up saying:
Warcraft III was unable to initialize DirectX. Please ensure you have DirectX
8.1 or newer installed and that your display drivers are current. DirectX may be
found on your Warcraft III install CD under Options.
Running Wine 20021219 with a WinXP partition
------- Additional Comments From us <at> the-edmeades.demon.co.uk 2003-01-09
17:27 -------
Keep updating wine as dx8 support is improving in wine over time. Make sure you
have wine compiled with --enable-opengl if required, and ensure your display is
not in a 24 bit display mode (There's an issue there as Warcraft doesnt like 24
bit displays - it must be 16 or 32 bit). If you still get the message, send me
a --debugmsg +d3d trace zipped up and I'll take a look.
(Note: I dont get _that_ error, it just doesnt work...)
Jason
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1210
------- Additional Comments From winebug(a)flonet.net 2003-23-06 13:05 -------
Bug comments restored from Gmane.org:
Hi,
I try to install wine-20021219 but I got this :
[...]
Preparing to install default Wine registry entries...
Installing default Wine registry entries...
FIXME:pthread_cond_init
Could not stat /mnt/fd0 (No such file or directory), ignoring drive A:
Could not stat /cdrom (No such file or directory), ignoring drive D:
./tools/wineinstall: line 634: 22743 Segmentation fault $REGEDIT $DEFREG
>/dev/null
Registry install failed.
It would be great if you could help me with this !
Best regards,
Pierre.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1238
------- Additional Comments From winebug(a)flonet.net 2003-23-06 12:57 -------
Bug comments restored from Gmane.org:
I'm using wine cvs sources as of 20030115 and am running on a
linux-2.4/glibc-2.3 based system.
When I tried to configure wine recently, I was interested in having IPX
support. However, configure was returning a negative result when it checked for
the necessary headers. After confirming that both netipx/ipx.h and linux/ipx.h
were present, I examined the autoconf macro more closely. It was then I
discovered that it was omitting a necessary header for IPX support on linux
systems: sys/socket.h. This is because the header is guarded by a test against
the existance of sys/socket.h.
The problem with the current wine configure.ac is that
AC_CHECK_HEADERS([sys/socket.h]) is placed *after* the check for IPX support.
This is most unfortunate and will result in false negatives previously
described.
The solution is to place AC_CHECK_HEADERS([sys/socket.h]) right after
AC_CHECK_LIB(mmap,mmap). This ensures that it will be properly defined in the
later test macros.
------- Additional Comments From marcus <at> jet.franken.de 2003-01-27 01:14
-------
fixed in CVS.
------- Additional Comments From tony_lambregts <at> telusplanet.net 2003-02-19
22:13 -------
Closing
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.