[Bug 42980] New: Black Desert Online - Failed to init security.
https://bugs.winehq.org/show_bug.cgi?id=42980 Bug ID: 42980 Summary: Black Desert Online - Failed to init security. Product: Wine-staging Version: 2.6 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shitman71(a)hotmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Created attachment 58112 --> https://bugs.winehq.org/attachment.cgi?id=58112 BDO_09.05.2017_Debug_Log After starting the launcher of the game and pushing the play-button the client(32 bit?) begins to load and quits with the error-message: Failed to init security. This is also a very common problem to windows users. Fixes to windows users are to run this game within administrator-mode or to put some kind of community-made patch into the folder "/Black Desert Online/bin32/xc/na/". I did also completely disable the firewall to test it, i cannot progress to the point of initialising its graphics. It always exits with this error-message. This should be the anti-cheat(unsure) of the game or some kind of other check before fully loading the game. Added attachments: BDO_09.05.2017_Wine_Output BDO_09.05.2017_Debug_Log -- 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=42980 --- Comment #1 from SF <shitman71(a)hotmail.com> --- Created attachment 58113 --> https://bugs.winehq.org/attachment.cgi?id=58113 BDO_09.05.2017_Wine_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=42980 --- Comment #2 from SF <shitman71(a)hotmail.com> --- This bug doesnt seem to appear anymore and previously caused the error-message "failed to init security": Wine Bug 23999 fixme:virtual:get_section_name (0x1c0,0x81c00000,0x33d538,528,0x33d534): semi-stub -- 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=42980 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #3 from winetest(a)luukku.com --- (In reply to SF from comment #2)
This bug doesnt seem to appear anymore and previously caused the error-message "failed to init security":
Wine Bug 23999
fixme:virtual:get_section_name (0x1c0,0x81c00000,0x33d538,528,0x33d534): semi-stub
So is this bug fixed? Not able to reproduce anymore? Fixed on game's side? What happens now when you try to run it up to date 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=42980 SF <shitman71(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal -- 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=42980 --- Comment #4 from SF <shitman71(a)hotmail.com> --- (In reply to winetest from comment #3)
So is this bug fixed? Not able to reproduce anymore? Fixed on game's side?
What happens now when you try to run it up to date wine?
It got fixed on game-side, it got an update since last week and today the error didnt occur anymore. I didn't do any changes to my system since this. The bug 23999 cannot be reproduced anymore but is staged and definitely not fixed on wine-side. Some duplicates of this bug exist with other users complaining of Black Desert Online not running because of this Bug. The only explanation is it has been fixed on game-side, there was an update last week and nothing else changed. -- 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=42980 --- Comment #5 from SF <shitman71(a)hotmail.com> --- No, Bug 23999 didn't get fixed in any way. Not from game-side and not from wine-side. After repairing the game with the launcher i get the behaviour of last week back, i was about to add attachments to Bug 23999 but couldn't reproduce it anymore. The reason of this was that i did add one of the community-patches and forgot it. I deleted this patch and got the game back to its stage it should be originally. I think this is a critical Bug now, preventing several applications from running. The Bug 42980 was caused by the community patch. Deleting "/Black Desert Online/bin32/xc/na/" fixes it. I dont know how this community patch did affect this game, maybe it solved Bug 23999 and did lead to this bug or it prevented the client from progressing to bug 23999. This can only be told after Bug 23999 is fixed. I added the community patch to the attachments for others to reproduce it, this might help to get the game(and high chances of others also affected by it) running. As far as i know this should be the anti-cheating of this game which is leading to this, usually anti-cheat-software is used to more then only one game. Bug 23999 affects also non-games. -- 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=42980 --- Comment #6 from SF <shitman71(a)hotmail.com> --- The community-patch can be downloaded here: http://forum.blackdesertonline.com/index.php?/topic/94675-issue-failed-to-in... Forum-Discussion to it was this one: http://forum.blackdesertonline.com/index.php?/topic/94675-issue-failed-to-in... The file itself is too large to be added to attachments. -- 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=42980 SF <shitman71(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |23999 -- 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=42980 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |focht(a)gmx.net Status|UNCONFIRMED |NEEDINFO --- Comment #7 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, after reading the comments I'm confused about the purpose/status of this ticket. You reported it against Wine-Staging 2.6 which means that Wine-Staging implements some functionality (on top of plain Wine) that is broken for you. Do you have a problem with the Wine-Staging patchset that implements 'MemorySectionName' class in 'NtQueryVirtualMemory'? https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-NtQue... Since you linked to a private forum without registration what is the purpose of the "community patches"? Are they further improvements of Wine-Staging? If, yes why aren't you communicating with Wine-Staging maintainers then? Again: What's the difference of this ticket to bug 23999 ? 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=42980 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- 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=42980 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #8 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with vanilla wine-4.4? -- 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=42980 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |ABANDONED Status|NEEDINFO |RESOLVED CC| |z.figura12(a)gmail.com --- Comment #9 from Zebediah Figura <z.figura12(a)gmail.com> --- No reply in over 2 years; marking 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.
https://bugs.winehq.org/show_bug.cgi?id=42980 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #10 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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=42980 Bug 42980 depends on bug 23999, which changed state. Bug 23999 Summary: Multiple applications with DRM schemes need NtQueryVirtualMemory 'MemorySectionName' info class (Crossfire HGWC, EMS SQL Manager 2010 Lite for PostgreSQL v.4.7.08, Cygwin/MSYS2, Knight Online client) https://bugs.winehq.org/show_bug.cgi?id=23999 What |Removed |Added ---------------------------------------------------------------------------- Status|STAGED |RESOLVED Resolution|--- |FIXED -- 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