[Bug 26744] New: Matlab 2009a: "Manage Licenses" doesn't work
http://bugs.winehq.org/show_bug.cgi?id=26744 Summary: Matlab 2009a: "Manage Licenses" doesn't work Product: Wine Version: 1.3.17 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Steps to reproduce: 1) remove ~/.wine 2) winetricks gecko 3) wine MATLAB R2009a.exe 4) Help->Licensing->Manage Licenses Behaviour: Wine error window "The program cmd.exe has encountered[...]". Expected Behaviour: No Wine error window and an website should open. Terminal Output: ERROR: Unable to reserve shield memory - disabling shield (line:760) System Error:487, Invalid address fixme:heap:HeapSetInformation 0x4c27000 0 0xc2e390 4 MATLAB:I18n:InconsistentLocale - The system locale setting, Russian_Russia.1251, is different from the user locale setting, Polish_Poland.1250. fixme:win:EnumDisplayDevicesW ((null),0,0xc194fc,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),1,0xc194fc,0x00000000), stub! fixme:font:WineEngCreateFontInstance Untranslated charset 255 fixme:imm:ImmGetOpenStatus (0x1c1728): semi-stub fixme:ntdll:NtCreateJobObject stub: 0xc16bb8 1f001f <null> fixme:ntdll:NtSetInformationJobObject stub: 0xdead 9 0xc18364 112 wine: Unhandled page fault on execute access to 0x000034c0 at address 0x34c0 (thread 0029), starting debugger... Additional info: wine-1.3.17-244-g83e692fb -- 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=26744 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv(a)dawncrow.de --- Comment #1 from André H. <nerv(a)dawncrow.de> 2011-04-12 13:20:37 CDT --- could you please attach a WINEDEBUG=cmd output -- 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=26744 --- Comment #2 from NSLW <lukasz.wojnilowicz(a)gmail.com> 2011-04-12 13:32:18 CDT --- (In reply to comment #1)
could you please attach a WINEDEBUG=cmd output
There is nothing new with WINEDEBUG=cmd. -- 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=26744 --- Comment #3 from butraxz(a)gmail.com 2013-10-18 13:37:32 CDT --- This ticket has not been updated for over 900 days. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it. Is this still an issue with 1.7.4 or higher ? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=26744 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |focht(a)gmx.net Resolution|--- |ABANDONED --- Comment #4 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, no further response from OP, resolving 'abandoned'. Regards -- 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.
https://bugs.winehq.org/show_bug.cgi?id=26744 NSLW <lukasz.wojnilowicz(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|ABANDONED |--- --- Comment #5 from NSLW <lukasz.wojnilowicz(a)gmail.com> --- Still issue in Wine 1.7.18 -- 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=26744 --- Comment #6 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, still cannot confirm, works fine here. Prerequisite: 'winetricks -q mfc42 vb6run' You also need 'winetricks -q vcrun2005' to work around msvcr80 insufficiency (bug 37026). The installer complains about missing .NET Framework during installation of some component (if one doesn't have Mono by default), but that's rather harmless. The error window is by design (Windows vs. Linux/Wine address space layout) and doesn't affect the actual activation process/license management. The app does something stupid: it reserves a hard-coded contiguous range of virtual memory. Upon failure it falls back to 'noshield'. Also documented here: http://www.mathworks.de/de/help/matlab/ref/matlabwindows.html --- quote --- matlab shieldOption provides the specified level of protection of the address space used by MATLAB during startup on Windows 32–bit platforms. It attempts to help ensure the largest contiguous block of memory available after startup, which is useful for processing large data sets. The shieldOption does this by ensuring resources such as DLLs, are loaded into locations that will not fragment the address space. With shieldOption set to a value other than none, address space is protected up to or after the processing of matlabrc. Use higher levels of protection to secure larger initial blocks of contiguous memory, however a higher level might not always provide a larger size block and might cause startup problems. Therefore, start with a lower level of protection, and if successful, try the next higher level. You can use the memory function after startup to see the size of the largest contiguous block of memory; this helps you determine the actual effect of the shieldOption setting you used. If your matlabrc (or startup.m) requires significant memory, a higher level of protection for shieldOption might cause startup to fail; in that event try a lower level. Values for shieldOption can be any one of the keywords shown in the table below. Option Description -shield minimum This is the default setting. It protects the range 0x50000000 to 0x70000000 during MATLAB startup until just before startup processes matlabrc. It ensures there is at least approximately 500 MB of contiguous memory up to this point. Start with this, the default value. To use the default, do not specify a shield option upon startup. If MATLAB fails to start successfully using the default option, -shield minimum, instead use -shield none. If MATLAB starts successfully with the default value for shieldOption and you want to try to ensure an even larger contiguous block after startup, try using the -shield medium option. -shield medium This protects the same range as for minimum, 0x50000000 to 0x70000000, but protects the range until just after startup processes matlabrc. It ensures there is at least approximately 500 MB of contiguous memory up to this point. If MATLAB fails to start successfully with the -shield medium option, instead use the default option (-shield minimum). If MATLAB starts successfully with the -shield medium option and you want to try to ensure an even larger contiguous block after startup, try using the -shield maximum option. -shield maximum This protects the maximum possible range, which can be up to approximately 1.5 GB, until just after startup processes matlabrc. If MATLAB fails to start successfully with the -shield maximum option, instead use the -shield medium option. -shield none This completely disables address shielding. Use this if MATLAB fails to start successfully with the default (-shield minimum) option. --- quote --- Again: the activation/managing of licenses works fine here. If it still crashes after applying the winetricks recipes attach a new backtrace with Wine 1.7.23 otherwise resolve the bug. Just stating "still an issue" isn't very useful if the symptoms changed, that's basically recycling the bug for different issues. Regards -- 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.
https://bugs.winehq.org/show_bug.cgi?id=26744 --- Comment #7 from Austin English <austinenglish(a)gmail.com> --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=26744 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #8 from super_man(a)post.com --- NEEDINFO -- 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.
https://bugs.winehq.org/show_bug.cgi?id=26744 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lukasz.wojnilowicz(a)gmail.co | |m, winetest(a)luukku.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=26744 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED --- Comment #9 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, resolving 'abandoned' here. Asked for feedback/testing multiple times. Regards -- 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.
https://bugs.winehq.org/show_bug.cgi?id=26744 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #10 from André H. <nerv(a)dawncrow.de> --- closing abandoned -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla