https://bugs.winehq.org/show_bug.cgi?id=43285
Bug ID: 43285 Summary: thief 3 - lock picking not working Product: Wine-staging Version: 2.10 Hardware: x86 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: shitman71@hotmail.com CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de
Created attachment 58623 --> https://bugs.winehq.org/attachment.cgi?id=58623 terminal log
At the tutorial mission you cannot open the door that needs to be lockpicked, the lockpicking is not working.
I remember this did work in wine 1.8.
https://bugs.winehq.org/show_bug.cgi?id=43285
SF shitman71@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86 |x86-64
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #1 from Michael Müller michael@fds-team.de --- Excerpt from the product selection page when creating a new bug report:
Wine‑staging: For bugs that occur in wine-staging, but not in wine-development
Have you tested that it works in Wine 2.10, but not in Wine Staging 2.10? If not, you should move this and all your other bugs into the Wine product.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #2 from SF shitman71@hotmail.com --- Usually all the bugs which occur in staging do also occur in normal wine.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #3 from SF shitman71@hotmail.com --- It is a bit hard to test this with freebsd, i always need to install and reinstall wine to switch between versions. I thought i only go for reporting it to staging. Shouldn't it be easy to you on your side to know if this error also occurs in normal wine?
I am developer myself, no x86/x64 development but i know what im talking about. I mean you see the logs i post and can tell if this also occurs within other wine-versions.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #5 from SF shitman71@hotmail.com --- can you delete this? this wasn't meaned to be posted, sorry.
https://bugs.winehq.org/show_bug.cgi?id=43285
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Product|Wine-staging |Wine
--- Comment #6 from Sebastian Lackner sebastian@fds-team.de --- (In reply to SF from comment #3)
It is a bit hard to test this with freebsd, i always need to install and reinstall wine to switch between versions. I thought i only go for reporting it to staging. Shouldn't it be easy to you on your side to know if this error also occurs in normal wine?
I am developer myself, no x86/x64 development but i know what im talking about. I mean you see the logs i post and can tell if this also occurs within other wine-versions.
Most of the time, the terminal output does not contain enough information to tell if a problem is Wine Staging specific, or is also present in the development branch. Please note that we also do not have all games/applications available for testing, so it is very helpful when users provide as much information as possible (which versions are affected, is it really a Wine regression or has something else be changed in the meantime, ...).
When it is unknown if a problem is a Wine Staging regression, it is recommended to open the bug in the Wine product, so that all developers can take a look at it.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #7 from SF shitman71@hotmail.com --- k, you did change it to wine? i know it next time, thx. this is all new to me.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #8 from SF shitman71@hotmail.com --- its still bugged within wine 2.15, it did work at 1.8.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #9 from Nikolay Sivov bunglehead@gmail.com --- If you're able to bisect that would be helpful. Or at least narrow down release range.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #10 from SF shitman71@hotmail.com --- Bisect? Sorry iam new to this.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #11 from Nikolay Sivov bunglehead@gmail.com --- It's described in details here https://wiki.winehq.org/Regression_Testing. Basically git vcs helps with that task, moving through commit history automatically, you only need to rebuild and test. If you can't build locally, you can use pre-built packages of specific version to find out what was the first version after 1.8 that stopped working. Regression test results are more valuable because you'll get exact commit that broke your application. Unless of course it was some change in your system and not Wine change.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #12 from SF shitman71@hotmail.com --- Uhm, thats not so easy on FreeBSD because you can only use one version and have to reinstall everything each time.
https://bugs.winehq.org/show_bug.cgi?id=43285
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com Keywords| |regression
--- Comment #13 from Austin English austinenglish@gmail.com --- (In reply to SF from comment #12)
Uhm, thats not so easy on FreeBSD because you can only use one version and have to reinstall everything each time.
FreeBSD ships a compiler. Otherwise they'd be unable to ship binary packages..
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #14 from SF shitman71@hotmail.com --- Thats another problem, even if i would have ports and pkg aviable to install it must be always manually done. I cannot have more then one version installed at time. The next problem is compiling to me, it outputs files and folders in a different order then they are on FreeBSD. I have to change manually names of dozens of files and they need to be put into the right folder each single file.
https://bugs.winehq.org/show_bug.cgi?id=43285
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #15 from Fabian Maurer dark.shadow4@web.de --- I don't see the problem, you just compile it somewhere and run it from there? You don't need to have it installed at all for that.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #16 from SF shitman71@hotmail.com --- How do you mean? The only way i know to use whine is via installing from pkg command or using ports and all of this must be installed into correct folders.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #17 from Fabian Maurer dark.shadow4@web.de --- No, you can just compile it and run it from there. You should have a "wine" script symlink in the top level folder after compiling.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #18 from SF shitman71@hotmail.com --- Yes, there is a link called wine. I can use this to run wine with it?
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #19 from Fabian Maurer dark.shadow4@web.de --- Yes, this is how it should work.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #20 from SF shitman71@hotmail.com --- How shall anyone know this link can be used? It works, i tryed wine 2.18 and accidently also found a workaround to this bug. You need to stay very close to the door and do some movements, lockpicking starts then. But its still bugged compared to how it worked in wine 1.8. It will take some time to find out.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #21 from Austin English austinenglish@gmail.com --- (In reply to SF from comment #20)
How shall anyone know this link can be used?
I thought it was documented in the README, but it's not. I sent a patch for that: https://source.winehq.org/patches/data/137506
https://bugs.winehq.org/show_bug.cgi?id=43285
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #22 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with current wine(3.21)?
https://bugs.winehq.org/show_bug.cgi?id=43285
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |ABANDONED Status|UNCONFIRMED |RESOLVED
--- Comment #23 from Gijs Vermeulen gijsvrm@gmail.com --- No response in over 3 years, no download.
-> ABANDONED.
https://bugs.winehq.org/show_bug.cgi?id=43285
--- Comment #24 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=43285
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #25 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla