[Bug 43975] New: Warning: failed to reserve range ... i386_set_ldt: Invalid argument | 10.13.2 beta High Sierra
https://bugs.winehq.org/show_bug.cgi?id=43975 Bug ID: 43975 Summary: Warning: failed to reserve range ... i386_set_ldt: Invalid argument | 10.13.2 beta High Sierra Product: Wine Version: 2.19 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tspamm3r(a)gmail.com It was working few days ago and it just stopped working. Tried to reinstall wine-staging but even normal wine is not working. When I try to run wine with something other than options showed after typing wine its just crashing always with same error: "preloader: Warning: failed to reserve range 00001000-00010000 i386_set_ldt: Invalid argument" I reinstalled wine and winestaging and still nothing. I am using few programs from windows (very light ones) but they are important for me. After running commands like: "WINEPREFIX=~/.snowman/ WINEARCH=win32 winecfg its crashing with same error. MacOS 10.13.2 High Sierra. Was working 2 days ago, nothing was modified in meanwhile. -- 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=43975 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- It never just "stops working", there must have been a change. If you didn't change wine, did you do OS updates or configuration changes in the meantime? -- 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=43975 --- Comment #2 from Tomas <tspamm3r(a)gmail.com> --- (In reply to Fabian Maurer from comment #1)
It never just "stops working", there must have been a change. If you didn't change wine, did you do OS updates or configuration changes in the meantime?
First of all I do not recall any update to be installed etc. It was working on friday... It was not in use from friday until today. Is there a way to get more detailed debug output? -- 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=43975 Ken Thomases <ken(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Ken Thomases <ken(a)codeweavers.com> --- This is the same as bug 43966. It's a bug in High Sierra 10.13.2 which is a *beta* release. It's been reported to Apple. *** This bug has been marked as a duplicate of bug 43966 *** -- 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=43975 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv(a)dawncrow.de Status|RESOLVED |CLOSED --- Comment #4 from André H. <nerv(a)dawncrow.de> --- closing dup -- 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 (1)
-
wine-bugs＠winehq.org