wine-bugs October 2015

wine-bugs@winehq.org

1 participants
7946 discussions

[Bug 39439] New: calling CreateProcess from windows code on a program binary mounted with noexec crashes wine
by wine-bugs＠winehq.org 13 Oct '15

13 Oct '15

https://bugs.winehq.org/show_bug.cgi?id=39439 Bug ID: 39439 Summary: calling CreateProcess from windows code on a program binary mounted with noexec crashes wine Product: Wine Version: 1.7.51 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: hramrach(a)gmail.com Distribution: --- I moved a windows application from a failed disk partition to a flash drive. I mounted the flash drive using pmount which adds the noexec flag. Executing the application as in wine ./Client.exe works. However, the application also spawns Client.bin (presumably using CreateProcess) and that binary crashes on start when spawned from noexec filesystem. It raises an exception very early in Wine code so I guess the application is in no position to catch it. And it raises it in the spawned application, not the spawning application. The Client.bin itself is not executable (as in +x mode). I can add traces if needed but this should be easy to reproduce. I see multiple related problems here 1) wine does not check the noexec flag when loading a binary initially from the commandline but does check it (or uses a library function that does) when a windows application calls spawn or clone or whatever - inconsistency 2) wine checks the noexec in the wrong place - it should check before performing CreateProcess and report error in the calling application but it fails executing the created process and crashes 3) when wine fails executing an application due to the noexec flag it should produce an intelligible error message rather than crash -- 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 5

[Bug 32785] New: Typing of the Dead freezes when being moved to another workspace in xmonad
by wine-bugs＠winehq.org 13 Oct '15

13 Oct '15

http://bugs.winehq.org/show_bug.cgi?id=32785 Bug #: 32785 Summary: Typing of the Dead freezes when being moved to another workspace in xmonad Product: Wine Version: 1.4.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: chinese_chater(a)yahoo.de Classification: Unclassified Created attachment 43289 --> http://bugs.winehq.org/attachment.cgi?id=43289 Wine command line log When starting Typing of the Dead (both the full or demo version) the game freezes as soon as I'm trying to move the according window to another workspace in the tiling window manager xmonad. I can move Typing of the Dead to other workspaces fine in Gnome 3.4 though. Tested on a recent Debian unstable with its wine 1.4.1 package. See the attachments for the full wine command line output and winedbg backtraces. -- 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 3

[Bug 30523] New: Jupiter crashes when trying to fill online tax declarations
by wine-bugs＠winehq.org 12 Oct '15

12 Oct '15

http://bugs.winehq.org/show_bug.cgi?id=30523 Bug #: 30523 Summary: Jupiter crashes when trying to fill online tax declarations Product: Wine Version: 1.5.2 Platform: x86 URL: http://pity.elfin.pl/pliki/Jupiter/Jupiter2011/std/1.0 .5.6/Jupiter2011_std_1.0.5.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: washuu(a)eastnews.com.pl Classification: Unclassified Created attachment 39930 --> http://bugs.winehq.org/attachment.cgi?id=39930 sample data file with bogus numbers Jupiter is free, downloadable program for calculating taxes in Poland, it's quite popular. I found using it under Wine quite uncomfortable, because of a few bugs. Here is one of them: - install the application. In my case it went without any glitches. - run the application. - open the attached sample data file, using menu "Plik" ("file") and "Otworz" ("open"). - wait a few seconds to open data file, when it is loaded you see some text in the middle, starting with "dziekujemy za skorzystanie z programu". - in the menu, choose "Rozliczenia" ("statements") and "e-deklaracje" ("e-declarations"). The program crashes with error: Unhandled exception: page fault on write access to 0x017c0bce in 32-bit code (0x02358bf5). Backtrace: =>0 0x02358bf5 (0x0033f804) 1 0x7c0af136 in mscoree (+0xf135) (0x0033f874) 2 0x7e71b84a CoCreateInstance+0x369() in ole32 (0x0033f8e4) 3 0x004167e4 in jupiter (+0x167e3) (0x7ea9c9d0) 4 0xb8ec81ec (0x8b55ff8b) 0x02358bf5: addb %al,0x0(%eax). -- 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 5

[Bug 19517] New: XenCenter is unable to contact anything on the network possibly due to "fixme:ras:RasEnumConnectionsW"
by wine-bugs＠winehq.org 12 Oct '15

12 Oct '15

http://bugs.winehq.org/show_bug.cgi?id=19517 Summary: XenCenter is unable to contact anything on the network possibly due to "fixme:ras:RasEnumConnectionsW" Product: Wine Version: 1.1.26 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: drwahls(a)gmail.com To recreate this bug, download XenCenter from Citrix (http://www.citrix.com/lang/English/lp/lp_1688615.asp), install it with msiexec, then try to connect to a XenServer on your network. Every time XenCenter tries to make a network call, it immediately fails and the following error is dumped on the command line: fixme:thread:NtQueryInformationThread info class 16 not supported yet fixme:shell:URL_ParseUrl failed to parse L"XenCenterMain.resources" fixme:shell:URL_ParseUrl failed to parse L"XenCenterMain.resources" fixme:ras:RasEnumConnectionsW (0x5d5ffd0,0x662dc0c,0x662dc08),stub! fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead! fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub fixme:ras:RasConnectionNotificationW (0xffffffff,0x34c,0x00000003),stub! fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub I have attached the full output from 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.

1 36

[Bug 39431] New: Make it possible to restart individual tasks
by wine-bugs＠winehq.org 11 Oct '15

11 Oct '15

https://bugs.winehq.org/show_bug.cgi?id=39431 Bug ID: 39431 Summary: Make it possible to restart individual tasks 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: --- If a task had a BotError or was Canceled, the WineTestBot lets either the administrator or the job's owner restart the whole job. But restarting all the tasks that actually completed normally seems wasteful. It would be more useful to make it possible to restart just the tasks that had a BotError or were Canceled. -- 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 0

[Bug 23697] New: Ethernet/IP application crashes on exit
by wine-bugs＠winehq.org 11 Oct '15

11 Oct '15

http://bugs.winehq.org/show_bug.cgi?id=23697 Summary: Ethernet/IP application crashes on exit Product: Wine Version: 1.2 Platform: x86 URL: http://www.odva.org/Default.aspx?tabid=202 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nsandschn(a)gmx.de Created an attachment (id=29684) --> (http://bugs.winehq.org/attachment.cgi?id=29684) Terminal output in wine-1.2 The zip file includes an EtherNet/IP example application in debug and release version. The debug version doesn't start (bug 15133). The release version works but crashes on exit. -- 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 7

[Bug 37002] New: Plogue chipsound registration fails
by wine-bugs＠winehq.org 10 Oct '15

10 Oct '15

http://bugs.winehq.org/show_bug.cgi?id=37002 Bug ID: 37002 Summary: Plogue chipsound registration fails Product: Wine Version: 1.7.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bique.alexandre(a)gmail.com Plogue Chipsound registration fails: fixme:process:GetProcessWorkingSetSize (0xffffffff,0x33e754,0x33e758): stub fixme:process:GetProcessWorkingSetSize (0xffffffff,0x33e754,0x33e758): stub fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} Here is a link to the software: http://www.plogue.com/products/chipsounds/ -- 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 3

[Bug 37311] New: Mentor PADS viewer cannot install
by wine-bugs＠winehq.org 10 Oct '15

10 Oct '15

https://bugs.winehq.org/show_bug.cgi?id=37311 Bug ID: 37311 Summary: Mentor PADS viewer cannot install Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nzsmith(a)gmail.com Created attachment 49620 --> https://bugs.winehq.org/attachment.cgi?id=49620 log showing error I am trying to install Mentor PADS viewer http://s3.mentor.com/pads-free-viewer/pads-pcb-viewer.zip I've followed the directions here: https://bugs.winehq.org/show_bug.cgi?id=35578 to get it to start the install, I get a EULA to agree to then all of a sudden I get a spew of messages on the screen, telling me it cannot access a log file: Title: Error Writing Log File [CP0069] Message: An error occurred while writing the history log file. Detail: It is possible that the nsmith-Latitude-E5430-non-vPro_8mip_history.txt history log file has read only permissions or is in use by another application. output attached, any help would be appreciated. -- 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 3

[Bug 38826] New: Dragon Age Origins: crash in msvcr80
by wine-bugs＠winehq.org 10 Oct '15

10 Oct '15

https://bugs.winehq.org/show_bug.cgi?id=38826 Bug ID: 38826 Summary: Dragon Age Origins: crash in msvcr80 Product: Wine Version: 1.7.46 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kurtjaeke(a)gmx.de Created attachment 51766 --> https://bugs.winehq.org/attachment.cgi?id=51766 Crash backtrace. Dragon Age Origins crashes after showing the intro sequence, with the backtrace attached. Just for curiosity, I bisected to wine-1.7.20. It crashes at the very same location. -- 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 39412] New: Add failover and load balancing support
by wine-bugs＠winehq.org 10 Oct '15

10 Oct '15

https://bugs.winehq.org/show_bug.cgi?id=39412 Bug ID: 39412 Summary: Add failover and load balancing support 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: --- Created attachment 52530 --> https://bugs.winehq.org/attachment.cgi?id=52530 Proposed schema update to allow for failover We currently have 4 VM hosts and it's easy to duplicate a given VM so it's present on multiple hosts. So we could put a VM such as win7u on both vm1 and vm2. But if vm1 goes offline for whatever reason, the administrator would still have to manually change the WineTestBot configuration so it knows to use the win7u copy on vm2. Furthermore if a task is scheduled to run on win7u but vm1 is busy running a task on another VM it would be nice to automatically run that task on vm2's win7u copy instead. This would lessen the need to carefully figure out which VMs can be put on the same host based on whether they are 64 bit or not, whether they are a base or winetest VM, etc. (later how many configurations they have, see bug 31784) But we cannot add entries for both copies of win7u because: 1. Both entries would show up in the user interface. 2. Wine patches would be scheduled to run on both copies which is not what we want. 3. Tasks scheduled to run on the first copy would still not be switched to the second copy. 4. The TestBot may start both copies at the same time which would be wrong from a licensing point of view and cause conflicts due to both having the same IP address (unless one of the copies is manually modified to have a different IP address). What is really needed is a change in the database schema so we can define multiple interchangeable 'VM instances' of a given VM. The attached schema adds a VMInstances table to deal with this: * A task would initially be connected to a VM (we can ignore the VMConfig vs. VM distinction here). * When scheduling the task the TestBot would iterate over the corresponding VM's VMInstances, identify the ones where the VMSnapshot field is set as the active instances and count them. (Note: the instance's ChildPid field is only set during reverts and the (JobID, StepNo, TaskNo) triplet is only set after revert when the task is actually running. So neither identify active VMs). * Then if the count of active instances is lower than the VM's MaxActive field it could revert that VM instance. * The VM's MaxActive is what allows us to not exceed our number of licenses. It also allow us to have multiple instances active in case we have multiple licenses: for the Linux build machine for instance (in that cae each copy would need a different IP address). * Optionally a user could request that a task be run on a specific VMInstance by setting the Task's VMNo field. -- 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 0

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 2015