wine-bugs October 2019

wine-bugs@winehq.org

1 participants
7768 discussions

[Bug 38271] New: The Docear4Word plugin for MS Word does not work at all
by wine-bugs＠winehq.org 25 Jan '20

25 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=38271 Bug ID: 38271 Summary: The Docear4Word plugin for MS Word does not work at all Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: whynot(a)nurfuerspam.de Distribution: --- Created attachment 51098 --> https://bugs.winehq.org/attachment.cgi?id=51098 Debug output trying to install/launch docear4word with Word Docear4Word is a FOSS plugin for MS Word, which allows creating citations and bibliography in MS Word based on a BibTeX database. Information about this plugin can be found here: http://www.docear.org/software/add-ons/docear4word/overview/ This is the download link: http://docear.org/download/docear4word_setup.exe The plugin's source code is also available: http://docear.org/download/docear4word_source.zip I tried installing this in both Word 2007 and Word 2010. In both cases, the install of the plugin appears to finish without any errors (in the GUI). In Word 2007, the progress is a little bit better, since the plugin at least shows up in the preferences (Word Options => Add-Ins => Inactive Application Add-ins lists "Docear4Word"). Obviously, since it is inactive, something went wrong. Also by following "Manage => Add-Ins => COM-Add-Ins" one gets to a modal pop-up window, which lists all COM Add-Ins. "Docear4Word" appears, but is unchecked. If one checks it and goes to the same window again (COM Add-Ins), it will say "Load Behavior: Not loaded. A runtime error occurred during the loading of the COM Add-in." If one turns wine debug output on, the are some specific errors in the command line (see attachment, 1st part), perhaps most importantly "fixme:ole:CoCreateInstance no instance created for interface {b65ad801-abaf-11d0-bb8b-00a0c90f2744} of class {34f82078-360b-4682-8275-0d9b0b641cbd}, hres is 0x800704e5" In Word 2010, the add-in does not even show up in Word whatsoever. Trying to manually launch the docear4word.exe installer from the Add-ins Window by using "Add", there is also some debug output in the console (see attachment, 2nd part). The Add-in uses .NET, so an obvious question is how to handle the .NET. I tried various approaches using several .NET versions and service packs via winetricks, and I believe also mono. Nothing worked. I do not remember the outcome of every single variant, but could try specific suggestions. This add-in is really important, since many in the science community are using Linux, but have to work with MS Word via wine for several reasons. Most in the science community use such plug-ins for reference management. Docear4Word is perhaps the most promising, powerful, and viable one, since the Docear4Word project strictly follows an FOSS approach. Getting this to work would thus be a huge progress. -- 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.

2 3

[Bug 33065] New: Make it possible to build a winetest executable with a single test
by wine-bugs＠winehq.org 24 Jan '20

24 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=33065 Bug #: 33065 Summary: Make it possible to build a winetest executable with a single test Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified Currently WineTestBot runs individual tests through TestLauncher (see testbot/src/TestLauncher). TestLauncher is responsible for checking for potential issues like missing dlls that could cause the test to hang on an error dialog. However that means duplicating a lot of WineTest's code and also that TestLauncher tends to be out of date (see bug 31609 for instance). Building the regular winetest.exe (with all the tests) and just running one test would result in a lot of wasted disk space and bandwidth. So the idea would be to make it possible to build winetest.exe and to only include the one test we want to run in the resources. -- 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.

2 11

[Bug 47997] New: Allow setting $WINEDEBUG
by WineHQ Bugzilla 24 Jan '20

24 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47997 Bug ID: 47997 Summary: Allow setting $WINEDEBUG Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- To figure out why a test is failing in a TestBot Wine VM it would sometimes be useful to be able to set $WINEDEBUG. The trouble with $WINEDEBUG is that it can result in very large logs (e.g. if set to +all or _relay). But then the tests can already generate large files by looping on a printf() so that's not really a new issue, it's just less likely to happen accidentally. The way to deal with that would be to limit the size of the log and reports that the TestBot retrieves from the VMs. Notes: * The TestBot already collects the whichever traces Wine puts out which would typically be the FIXME()s and ERR()s. They are at the end of the "full task log". * So a workaround is to patch Wine to convert the relevant traces to FIXME()s. That's not very practical if one does not initially know which ones are going to be needed which is why being able to set $WINEDEBUG would be better. -- 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 1

[Bug 47900] New: Enable caching of screenshots and log files
by WineHQ Bugzilla 24 Jan '20

24 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47900 Bug ID: 47900 Summary: Enable caching of screenshots and log files Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- web/Screenshot.pl and web/GetFile.pl systematically disable caching of the files they return by setting their Last-Modified field to the current time. For Screenshot.pl this may have been to deal with live screenshots that were updated regularly. But even so this should probably be done through the Expires field instead. Anyway we don't have live snapshots anymore and when they come back it will (most likely) be in the form of a timestamped filename so that once written a file would not change. The only case where a file may change is when a job is canceled and restarted. That does not seem to warrant disabling caching altogether. -- 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 4

[Bug 47901] New: Stream the files in Screenshot.pl and GetFile.pl
by WineHQ Bugzilla 24 Jan '20

24 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47901 Bug ID: 47901 Summary: Stream the files in Screenshot.pl and GetFile.pl Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Screenshot.pl and GetFile.pl load their files entirely in memory before returning them. That's wasteful. Also GetFiles.pl loads it in a $ImageBytes variable despite returning patches and executables. -- 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 1

[Bug 44684] New: Shaders fail to compile in Roblox Studio (white window)
by wine-bugs＠winehq.org 24 Jan '20

24 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=44684 Bug ID: 44684 Summary: Shaders fail to compile in Roblox Studio (white window) Product: Wine Version: 3.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: and3md(a)gmail.com Distribution: --- Created attachment 60693 --> https://bugs.winehq.org/attachment.cgi?id=60693 Roblox Studio run log The application displays splash screen correctly. Next, the main window is showed which is "empty" (the window is white). The cursor changes its shape in some places so probably it's just a display case. Wine returns a lot of errors: 007d: err: d3dcompiler: compile_shader HLSL shader parsing failed. 007d: fixme: hlsl_parser: declare_vars Complex initializers are not supported yet. Hardware: Geforce GTX 1060 (proprietary linux driver). -- 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.

2 12

[Bug 19329] New: Program installs but client fails to connect to server
by wine-bugs＠winehq.org 24 Jan '20

24 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=19329 Summary: Program installs but client fails to connect to server Product: Wine Version: 1.1.25 Platform: PC URL: http://www.livezilla.net/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: junk(a)mandd.com Using Wine 1.1.25 and a clean ~/.wine, I had to install dotnet20 and ie6 (I used winetricks) before the installer would complete. After that the Livezilla client will run. But when I try to connect to a Livezilla server, an error window pops up stating: -------------------------------------------------------------------- The underlying connection was closed: The connection was closed unexpectedly. Further information: The underlying connection was closed: The connection was closed unexpectedly. -------------------------------------------------------------------- -- 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.

2 41

[Bug 34865] New: Can't execute mingw toolchain provided by Rtools
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=34865 Bug #: 34865 Summary: Can't execute mingw toolchain provided by Rtools Product: Wine Version: 1.7.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mail(a)kirill-mueller.de Classification: Unclassified I can't execute "R CMD INSTALL" on an installation of R + Rtools in Wine (latest version from PPA "ppa:ubuntu-wine/ppa"). A reproducible script and console output can be found here: https://gist.github.com/krlmlr/7333242 . The script will set and write to $WINEPREFIX and download to $DOWNLOAD_DIR. Unfortunately, the logs do not show enough detail. After the line `about to run R CMD SHLIB -o kimisc.dll rcpp_hello_world.cpp RcppExports.cpp --debug`, a call to `gcc` is made. (I have added the output of the same call on my Linux system to the Gist.) To me, it seems that the calling process is not notified when the child process has completed, and it stops after a timeout. My hope is that this has been seen before and that there's an easy fix. I'm really new to Wine. -- 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.

2 11

[Bug 35344] New: Cygwin's post-install scripts fail on fork errors
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=35344 Bug ID: 35344 Summary: Cygwin's post-install scripts fail on fork errors Product: Wine Version: 1.7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)georg.so Classification: Unclassified Executing 'wine setup-x86.exe' seems to work quite well (you can step through the wizard, packages are downloaded and extracted) until the post-installation bash scripts are executed. Then I get for each script a message like: running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/glib2.0.sh" [..] fixme:ntdll:NtQueryInformationProcess (process=0xffffffff) Unimplemented information class: ProcessSessionInformation [..] fixme:ntdll:NtQueryVolumeInformationFile 0xf0: faking attribute info fixme:ntdll:NtQueryVolumeInformationFile 0xec: faking attribute info fixme:ntdll:NtQueryInformationFile Unsupported class (34) [..] fixme:ntdll:NtQueryVolumeInformationFile 0xf4: faking attribute info fixme:ntdll:NtQueryInformationFile Unsupported class (8) [..] fixme:ntdll:NtQueryVolumeInformationFile 0xfc: faking attribute info [..] fixme:ntdll:NtQueryVolumeInformationFile 0x100: faking attribute info fixme:ntdll:NtQueryVolumeInformationFile 0x124: faking attribute info [..] fixme:ntdll:NtQueryVolumeInformationFile 0x128: faking attribute info [..] /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: Resource temporarily unavailable abnormal exit: exit code=254 The fork error message are always displayed after some kind of timeout. Where to get the setup-x86.exe: http://cygwin.com/setup-x86.exe $ md5sum setup-x86.exe c9818d3500e42fd9eb755d424450871a setup-x86.exe Executing Cygwin's setup exe inside wine looks a little bit silly, but I want to create a reference cygwin installation for deployment purposes. see also: http://wiki.winehq.org/CygwinSupport -- 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.

2 13

[Bug 45978] New: Deadlight (2011) Steam - Graphical glitches
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=45978 Bug ID: 45978 Summary: Deadlight (2011) Steam - Graphical glitches Product: Wine-staging Version: 3.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: david.gamiz(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hello, This version of the game today run OK, gamepad work and have "good" performance, but with graphical glitch(black opaque triangles on screen) that broken the gameplay and experience. Only need find fix for this annoying bug. For perfect experience. Image courtesy from user: https://i.imgur.com/eyEEdxw.jpg More reports: https://spcr.netlify.com/app/211400 Actually, the normal terminal not show error or message from graphics stack. If necessary add specify log trace for fix this only ask me. Thanks in advance, David Gámiz Jiménez -- 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.

2 25

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 October 2019