wine-bugs June 2008

wine-bugs@winehq.org

1 participants
5528 discussions

[Bug 10599] New: dlls/oleaut32/tests/vartest.c fails
by wine-bugs＠winehq.org 06 Jan '16

06 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=10599 Summary: dlls/oleaut32/tests/vartest.c fails Product: Wine Version: CVS/GIT Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: test AssignedTo: wine-bugs(a)winehq.org ReportedBy: alexandru.balut(a)gmail.com I'm running "make test" from dlls/oleaut32/tests and I get this error: ../../../tools/runtest -q -P wine -M oleaut32.dll -T ../../.. -p oleaut32_test.exe.so vartest.c && touch vartest.ok fixme:variant:VarMod Could not convert left type 4096 to 20? rc == 0x80020008 fixme:variant:VarMod Could not convert left type 8192 to 20? rc == 0x80020008 fixme:variant:VarMod Could not convert left type 16384 to 20? rc == 0x80020008 vartest.c:3143: Test failed: got VT_DATE(-1.5) expected VT_DATE(-1.4) vartest.c:3150: Test failed: got VT_R8(-1.5) expected VT_R8(-1.4) make: *** [vartest.ok] Error 2 I use wine-0.9.49-376-gc2f0697 on Ubuntu Gutsy (2.6.22-14-generic #1 SMP x86_64 GNU/Linux), the compiler is gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) There is a similar report here: http://www.winehq.org/pipermail/wine-devel/2007-August/058585.html -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 9

[Bug 9575] New: IBExpert need windows native ole32.dll to run
by wine-bugs＠winehq.org 06 Jan '16

06 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=9575 Summary: IBExpert need windows native ole32.dll to run Product: Wine Version: 0.9.44. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: c_pradelli(a)yahoo.com To run ibexpert ole32.dll needs to be overriden (or dcom98 installed). I can't detect why, there are no fixme printed on screen. The application raise an access violation when starts and then you can't close it. The application is in AppDB http://appdb.winehq.org/appview.php?iVersionId=9049 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 33

[Bug 9401] New: Dragon Naturally Speaking 7 crashes after training complete
by wine-bugs＠winehq.org 06 Jan '16

06 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=9401 Summary: Dragon Naturally Speaking 7 crashes after training complete Product: Wine Version: CVS Platform: Other URL: http://scansoft.com OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: wine-ole AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Created an attachment (id=7715) --> (http://bugs.winehq.org/attachment.cgi?id=7715) +ole log of running training, and error that happened shortly thereafter After user training is complete, DNS puts up a dialog saying something like "Congratulations! Training is complete." The next thing you do crashes with a dialog box saying something like "Unexpected error. COM out of memory." and log messages like Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0 0000000). Fortunately, the error repeats the next time you start and try to do something, you don't have to repeat training. Better make a copy of ~/.wine once you finish training, though, so you can get back to that state quickly in case something goes wrong. (e.g. running a +relay log at that point filled up my disk, and after that, dragon wouldn't start properly.) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 11

[Bug 9388] New: installer stuck for TRS 2006 Demo
by wine-bugs＠winehq.org 06 Jan '16

06 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=9388 Summary: installer stuck for TRS 2006 Demo Product: Wine Version: CVS Platform: PC-x86-64 URL: http://www.auran.com/TRS2006/index.php OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: dan(a)danny.cz When trying to install the demo for TRS 2006, the installer gets stuck on the first installation wizard page. output from the terminal: fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" err:ole:TLB_ReadTypeLib Loading of typelib L"c:\\Program Files\\Common Files\\InstallShield\\Professional\\RunTime\\IsProBE.tlb" failed with error 2 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5

[Bug 13027] New: Add a description field to winetest
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=13027 Summary: Add a description field to winetest Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Depends on: 13026 It should be possible to specify a description for a winetest run. That description field would be sent with the report and would describe the system the tests are run on, providing details that cannot be retrieve programmatically. For instance: "US Windows XP system provided by Compaq and then cleaned up. Last updated on 2007/10/16 but no IE7." or "Clean install of a stock French Windows 95, running in a VMware 5.5 guest." The user should be able to either enter this description in the main dialog (see also bug 13026), or on the command line. -- 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.

1 8

[Bug 13028] New: winetest's Stop button does not work
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=13028 Summary: winetest's Stop button does not work Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com It says it's not implemented but closing the winetest window works just fine. So it seems like implementing the Stop button should not be too hard. -- 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.

1 11

[Bug 11016] New: odbc32.dll should look for libodbc.so.1 instead of libodbc .so
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=11016 Summary: odbc32.dll should look for libodbc.so.1 instead of libodbc.so Product: Wine Version: 20040615 Platform: PC URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=259710 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: ovek(a)arcticnet.no An easy one for a newbie wine hacker, maybe... Currently, in dlls/odbc32/proxyodbc.c, there's a hardcoded libodbc.so (unless an environment variable overrides it). Perhaps it would be preferable if the WINE_GET_SONAME configure macro was used to grab a name like libodbc.so.1 instead, so that if some user have installed unixodbc, things would Just Work without forcing him/her to also either install unixodbc-dev, or manually make a symlink, or figure out weird environment variables. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 3

[Bug 13030] New: winetest and result logging / submission
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=13030 Summary: winetest and result logging / submission Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com The winetest GUI does not make it possible to choose between saving the results to a local file and submitting the results. -- 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.

1 9

[Bug 11177] New: winealsa doesn't assign unique MIDI port names
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=11177 Summary: winealsa doesn't assign unique MIDI port names Product: Wine Version: 20050628 Platform: PC URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333361 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: _obsolete_multimedia AssignedTo: wine-bugs(a)winehq.org ReportedBy: ovek(a)arcticnet.no Currently, when mapping ALSA MIDI ports to Windows MIDI port names, winealsa uses the port's client name, which is not unique and may cause some programs to get confused. A user is suggesting using the ALSA port name, which I suspect can be acquired by e.g. replacing snd_seq_client_info_get_name(cinfo) in midi.c with snd_seq_port_info_get_name(pinfo). You could also append a number to the client name, or whatever else it takes to make the name unique. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 7

[Bug 13029] New: winetest should make it possible to just extract the individual tests
by wine-bugs＠winehq.org 05 Jan '16

05 Jan '16

http://bugs.winehq.org/show_bug.cgi?id=13029 Summary: winetest should make it possible to just extract the individual tests Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com The first task that winetest does is extract the individual test binaries. However it does not say where and if one wants to get at them (to then run them by hand for testing/debugging purposes), then one has to kill winetest, and track down its temporary directory (which is something like in c:\Documents and Settings\account\Local Settings\Temp\wctXXX btw). It would be nice to have an 'Extract tests' button in the main dialog that would open a dialog letting the user choose where to save the individual tests (or some other reasonably simple way of achieving the same purpose). -- 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.

1 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs June 2008