http://bugs.winehq.org/show_bug.cgi?id=25448
Summary: Filemaker Pro 11 can't be started from Linux main menu
icon - Invalid or incorrect link
Product: Wine
Version: 1.3.8
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: emerson.prado.eng(a)gmail.com
Created an attachment (id=32388)
--> (http://bugs.winehq.org/attachment.cgi?id=32388)
Filemaker Pro 11 starter link inside "Windows" Start menu
Clicking in the Filemaker icon in the main menu just brings in an error message
window saying "File not found". Starting from Terminal works OK.
The link in the main menu points to:
env WINEPREFIX="/home/<user>/.wine" wine C:\\windows\\command\\start.exe /Unix
/home/<user>/.wine/dosdevices/c:/users/<user>/Menu\
Iniciar/Programas/FileMaker\ Pro.lnk
I'm sending attached the Filemaker Pro.lnk file.
--
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=22469
Summary: FileMaker Pro 11: Text is upside down when builtin
gdiplus is used
Product: Wine
Version: 1.1.43
Platform: x86
URL: http://www.filemaker.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wylda(a)volny.cz
Created an attachment (id=27526)
--> (http://bugs.winehq.org/attachment.cgi?id=27526)
Filemaker pro 11
Text in boxes is upside down, when the box is selected. This doesn't happen
when native gdiplus is used. Attachment shows that better.
To reproduce:
1. Download the trial version
2. Download demo data http://bugs.winehq.org/attachment.cgi?id=26679
3. Run "wine FileMaker\ Pro.exe" and load data from step 2.
4. Click on any textbox, to make it upside down
--
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=33287
Bug #: 33287
Summary: Filemaker Pro12 crashes when opening database file
Product: Wine
Version: 1.4.1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jmeador(a)momentapharma.com
Classification: Unclassified
I can install Filemaker Pro 12 with a valid serial number into BioLinux 7,
which is Ubuntu 12.04. Wine was installed as 4.1 via the Ubuntu Software Center
and I cannot get the dev version of 1.5 to install via this or the commandline.
It says that the binaries are not available.
When running from the commandline, I get this output:
:~$ wine "c:\program files (x86)\FileMaker\FileMaker Pro 12\FileMaker Pro.exe"
p11-kit: couldn't load module:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared
object file: No such file or directory
When I look for this directory in /usr/lib/i386-linux-gnu/ there are no files
or folders called pkcs11 so perhaps this is missing from the wine1.4 installer?
When installing, the installer gets to the end and then crashes and says the
registration program cannot run, however, the program will start and appears to
run ok until you open a database file, and I have tried several. Once I try to
open a file, it crashes. The FileMaker Pro binary and other files are installed
into /Program File (x86)/FileMaker/...
I am attaching the backtrace file as well which was obtained from running the
program from the graphical method.
The computer is an HP Xeon processor with 64-bit Ubuntu 12.04 and 128 GB ram
Thanks for any help you can provide.
--
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=22077
Summary: cspro 4.0 error in wine (1.1.40)
Product: Wine
Version: 1.1.40
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: iip.umar.rifai(a)gmail.com
CC: iip.umar.rifai(a)gmail.com
Created an attachment (id=26903)
--> (http://bugs.winehq.org/attachment.cgi?id=26903)
screen show when hang
Cspro get hang when pressing key or mouse during popup selection (selcase
function in cspro), and also the icon on the tree look weird.
How to test:
1. download cspro here http://www.census.gov/ipc/www/cspro/
2. Run Cspro 4.0 program
3. Open file/application, goto examples/capi
4. BUG 1. you will see that the icon in the left are black. Different when you
see it in native windows.
5. BUG-2. now, run the program, from the menu file->run. Just clik ok on every
prompt or enter everything. On roster screen, enter only one line, and leave
blank in the second row, to directly end the data entry, you will see yes/no
popup, just klik or press up/down arrow, then cspro will hang.
Screenshot can be see here
http://sites.google.com/site/iipumarrifai2/wine-cspro-error1.jpg
I think this the only one problem I found in cspro, if this can be fix than it
will be gold in wine. And the problem is the same problem since wine Beta and
cspro 3.x, but I never send it to wine.
I'm running this on Linux Mint 8 (Ubuntu karmic)
Best Regards,
-iip-
--
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=15022
Summary: msi.dll.MsiDatabaseMergeW not implemented
Product: Wine
Version: 1.1.3
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aruiz(a)gnome.org
Created an attachment (id=15664)
--> (http://bugs.winehq.org/attachment.cgi?id=15664)
Wix test case
While trying to run wix[0]'s candle tool with mono[1] I get this error:
wine: Call from 0x7ee510e0 to unimplemented function msi.dll.MsiDatabaseMergeW,
aborting
Are there any plans to support this function anytime soon?
[0] http://wix.sourceforge.net/
[1] http://www.go-mono.com/mono-downloads/download.html
--
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=17983
Summary: WiX fails with builtin msi.dll
Product: Wine
Version: 1.1.18
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hib(a)hiberis.nl
Created an attachment (id=20350)
--> (http://bugs.winehq.org/attachment.cgi?id=20350)
reproduce-wix-msi-bug.sh
With Windows Installer XML (WiX) toolset, you can create .msi packages.
The program light.exe creates these packages.
Light.exe succeeds both when run with wine's builtin msi.dll and with a native
msi.dll. However, the msi package produced with the builtin msi.dll does not
install on MS Windows (XP), while the one built with the native msi.dll does.
Apparently, light.exe fails without complaining, which makes it difficult to
pinpoint the problem. Nonetheless, looking at the produced .msi packages it
seems that there is something wrong with the Summary information.
I have attached a script to reproduce the problem.
Note, the storage warnings that light.exe produces can be get rid off by using
a native ole32.dll, but that does not appear to affect this bug.
--
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=27132
Summary: Crash in MSI_RecordSetStringW when embedding RTF with
NUL character into an MSI with Wix
Product: Wine
Version: 1.3.19
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sam(a)robots.org.uk
Created an attachment (id=34640)
--> (http://bugs.winehq.org/attachment.cgi?id=34640)
test case
When using WiX to build an MSI installer package, Wine will crash when an RTF
file that will be contained in the installer contains a NUL character.
To reproduce:
1. Run build.msi in the attached test case.
2. light should crash while reading from 0x30
To run the test case, you will need Mono
<http://ftp.novell.com/pub/mono/archive/2.10.2/windows-installer/5/mono-2.10…>
and WiX <http://wix.codeplex.com/releases/view/44406#DownloadId=119160>. You
will need to put WiX's tools in Wine's PATH, or modify build.sh to give the
full path to the WiX tools when it invokes light and candle.
--
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=28350
Summary: failure to create MSI packages include merge modules
(MSM files)
Product: Wine
Version: 1.3.28
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sam(a)robots.org.uk
The attached test case fails to compile an MSI using WiX 3.0 under Wine 1.3.28.
The error given is:
wine light -sval pr.wixobj
Microsoft (R) Windows Installer Xml Linker version
Copyright (C) Microsoft Corporation. All rights reserved.
light.exe : error LGHT0001 : Object reference not set to an instance of an
object
Exception Type: System.NullReferenceException
Stack Trace:
at Microsoft.Tools.WindowsInstallerXml.MergeMod.NativeMethods.GetMsmMerge ()
[0x00000] in <filename unknown>:0
at Microsoft.Tools.WindowsInstallerXml.Binder.ProcessMergeModules
(Microsoft.Tools.WindowsInstallerXml.Output output,
Microsoft.Tools.WindowsInstallerXml.FileRowCollection fileRows) [0x00000] in
<filename unknown>:0
at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase
(Microsoft.Tools.WindowsInstallerXml.Output output, System.String databaseFile)
[0x00000] in <filename unknown>:0
at Microsoft.Tools.WindowsInstallerXml.Binder.Bind
(Microsoft.Tools.WindowsInstallerXml.Output output, System.String file)
[0x00000] in <filename unknown>:0
at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run (System.String[] args)
[0x00000] in <filename unknown>:0
Unhandled Exception: System.NullReferenceException: Object reference not set to
an instance of an object
at Microsoft.Tools.WindowsInstallerXml.MergeMod.NativeMethods.GetMsmMerge ()
[0x00000] in <filename unknown>:0
at Microsoft.Tools.WindowsInstallerXml.Binder.ProcessMergeModules
(Microsoft.Tools.WindowsInstallerXml.Output output,
Microsoft.Tools.WindowsInstallerXml.FileRowCollection fileRows) [0x00000] in
<filename unknown>:0
at Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase
(Microsoft.Tools.WindowsInstallerXml.Output output, System.String databaseFile)
[0x00000] in <filename unknown>:0
at Microsoft.Tools.WindowsInstallerXml.Binder.Bind
(Microsoft.Tools.WindowsInstallerXml.Output output, System.String file)
[0x00000] in <filename unknown>:0
at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run (System.String[] args)
[0x00000] in <filename unknown>:0
Binder temporary directory located at '/tmp/user/1000\11699d64\2ddee0c7'.
Validator temporary directory located at '/tmp/user/1000\28b7882d\728284bb'.
--
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=11414
Summary: msidb:STREAMS_modify 0x1c2178 3 0x12d2aa0 - mode not
implemented
Product: Wine
Version: unspecified
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jdahlin(a)async.com.br
To be able to test this you need to install mono on win32. I used the 1.2.6
version.
I installed the latest beta of WiX, 3.0.2925 available from
wix.sourceforge.net.
First light.exe needs to be run on product.wxs on the
examples/public/first/product.wxs, this generated product.wixobj.
After that I run, with only builtin dlls:
wine ../light.exe "-cultures:en-us" product.wixobj
fixme:msidb:STREAMS_modify 0x1c2178 3 0x12d2aa0 - mode not implemented
light.exe : error LGHT0001 : Some sort of w32 error occurred: 120
Exception Type: System.ComponentModel.Win32Exception
Stack Trace:
[mono backtrace cut]
--
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=11411
Summary: GetFileVersionInfoSizeW returns wrong error code if file
has no version (affects WiX)
Product: Wine
Version: 0.9.54.
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Keywords: patch
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
http://blog.rvburke.com/2008/01/30/gtk-and-pygtk-on-win32/
complained about WiX not running.
http://www.winehq.org/pipermail/wine-patches/2007-November/046456.html
talks about two changes needed to get it closer to running.
It seems to have been dropped, so here's one of the two bugs
it reports:
Running light.exe from wix on a wixobj file with a non-versioned
file as a component prints a diagnostic error indicating
ERROR_FILE_NOT_FOUND using wine's builtin of version.dll and msi.dll,
but ERROR_RESOURCE_DATA_NOT_FOUND using wine's builtin of msi.dll and
native version.dll.
... version.dll's GetFileVersionInfoSizeW does return
ERROR_FILE_NOT_FOUND when trying to get the version of a file that
does not contain a version (for example, a text file). This is
because it relies on VERSION_GetFileVersionInfo_16 to do the file
existance check, which returns 0 (meaning file does not exist) if
LoadLibrary16 fails.
The patch addresses this by making VERSION_GetFileVersionInfo_16
return 0xFFFFFFFF (meaning file exists but does not have version) if
LoadLibrary16 returns an error beside ERROR_FILE_NOT_FOUND.
--
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.