https://bugs.winehq.org/show_bug.cgi?id=37382
Bug ID: 37382 Summary: Kyonyuu fantajii:A adult adventure games can install games but cannot start Product: Wine Version: 1.7.28 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: kddc3s@gmail.com
Created attachment 49716 --> https://bugs.winehq.org/attachment.cgi?id=49716 Console messages when starting the game
The day before yesterday I updated wine 1.7.28 can't run ,but original wine 1.7.27 was still work. I re-install the game and recover to wine 1.7.27 was still can't work.
https://bugs.winehq.org/show_bug.cgi?id=37382
kddc3s@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kddc3s@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=37382
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
--- Comment #1 from Austin English austinenglish@gmail.com --- If you reinstall with 1.7.27 and run it, does it work? If so, run a regression test (you could backup the prefix before running, so you don't have to reinstall each time).
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #2 from kddc3s@gmail.com --- (In reply to Austin English from comment #1)
If you reinstall with 1.7.27 and run it, does it work? If so, run a regression test (you could backup the prefix before running, so you don't have to reinstall each time).
I reinstall with 1.7.27 and run it, but isn't work.
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #3 from Austin English austinenglish@gmail.com --- Please attach the full backtrace.
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #4 from kddc3s@gmail.com --- Created attachment 49729 --> https://bugs.winehq.org/attachment.cgi?id=49729 Backtrace
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #5 from kddc3s@gmail.com --- (In reply to Austin English from comment #3)
Please attach the full backtrace.
uploaded.
https://bugs.winehq.org/show_bug.cgi?id=37382
Sagawa sagawa.aki+winebugs@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sagawa.aki+winebugs@gmail.c | |om
--- Comment #6 from Sagawa sagawa.aki+winebugs@gmail.com --- Your backtrace shows the fault occurs inside MessageBox. Could you provide us debug trace with WINEDEBUG=msgbox?
Please refer to http://wiki.winehq.org/FAQ#head-16da35b6327024d6ea576e3678488b16862d0f5e (How do I get a debug trace?) for details.
I got demo version of the software from publisher's web page, but I can't reproduce this issue. Kyonyuu fantajii uses 800x600 resolution by specs. So, you might run another version, e.g. download version.
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #7 from kddc3s@gmail.com --- Created attachment 49752 --> https://bugs.winehq.org/attachment.cgi?id=49752 debug trace with WINEDEBUG=msgbox
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #8 from kddc3s@gmail.com --- (In reply to Sagawa from comment #6)
Your backtrace shows the fault occurs inside MessageBox. Could you provide us debug trace with WINEDEBUG=msgbox?
Please refer to http://wiki.winehq.org/FAQ#head-16da35b6327024d6ea576e3678488b16862d0f5e (How do I get a debug trace?) for details.
I got demo version of the software from publisher's web page, but I can't reproduce this issue. Kyonyuu fantajii uses 800x600 resolution by specs. So, you might run another version, e.g. download version.
I have played other games that using the same game engine, they all encounter the same issue, including the demo version u said.
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #9 from Sagawa sagawa.aki+winebugs@gmail.com --- Thanks for providing logs. But, I'm afraid your trace log doesn't contain msgbox channel messages at all. I wonder why msgbox isn't shown.
From another point of view, your terminal log shows xrandr issue. So, you may
want to fix your screen resolution to 800x600 or 1280x960 somehow. xrandr command might help you.
I tried following archive file which avaiable from [1] or [2] as last comment. SHA1(titi_taiken.zip) = d95aec030a384be95fd99707c49fa16392d1b450 (202MB) If possible, could you try this and attach full backtrace without winedbg?
[1] ... http://mirror.tsundere.ne.jp/download/waffle/584738240609a82e7428b0b8a052750... [2] ... http://kokoron.madoka.org/mirror/k/kyonyufantasy/titi_taiken.zip
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #10 from kddc3s@gmail.com --- Created attachment 49756 --> https://bugs.winehq.org/attachment.cgi?id=49756 titi_taiken full backtrace without winedbg
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #11 from kddc3s@gmail.com --- (In reply to Sagawa from comment #9)
Thanks for providing logs. But, I'm afraid your trace log doesn't contain msgbox channel messages at all. I wonder why msgbox isn't shown.
From another point of view, your terminal log shows xrandr issue. So, you may want to fix your screen resolution to 800x600 or 1280x960 somehow. xrandr command might help you.
I tried following archive file which avaiable from [1] or [2] as last comment. SHA1(titi_taiken.zip) = d95aec030a384be95fd99707c49fa16392d1b450 (202MB) If possible, could you try this and attach full backtrace without winedbg?
[1] ... http://mirror.tsundere.ne.jp/download/waffle/ 584738240609a82e7428b0b8a0527503/titi_taiken.zip [2] ... http://kokoron.madoka.org/mirror/k/kyonyufantasy/titi_taiken.zip
uploaded.
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #12 from Sagawa sagawa.aki+winebugs@gmail.com --- Please run the executable like: $ wine KyonyuuFantajii.exe &> log.txt Of course, KyonyuuFantajii is a placeholder and `$' is a prompt. You don't forget to choose [Close] when program error dialog appears. Then attach log.txt file here.
In your trace log, the first line shows, ``wine winedbg t@^W[(+).exe''. That doesn't mean run without winedbg. Your process starts as pid 002c, but your backtrace is for pid 0008.
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #13 from kddc3s@gmail.com --- (In reply to Sagawa from comment #12)
Please run the executable like: $ wine KyonyuuFantajii.exe &> log.txt Of course, KyonyuuFantajii is a placeholder and `$' is a prompt. You don't forget to choose [Close] when program error dialog appears. Then attach log.txt file here.
In your trace log, the first line shows, ``wine winedbg t@^W[(+).exe''. That doesn't mean run without winedbg. Your process starts as pid 002c, but your backtrace is for pid 0008.
But I don't know why run the executable $ wine KyonyuuFantajii.exe &> log.txt I didn't get any backtrace but a page fault
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #14 from Sagawa sagawa.aki+winebugs@gmail.com --- (In reply to kddc3s from comment #13)
But I don't know why run the executable $ wine KyonyuuFantajii.exe &> log.txt I didn't get any backtrace but a page fault
Did you meet ``Program Error'' dialog? Basically, when a page fault occurs, wine executes winedbg in background. The winedbg shows ``Program Error'' dialog. If you choose [Close] button on it, winedbg dumps backtrace information to your terminal.
I looked back your attachments, and noticed attachment 49752 shows ``couldn't load main module''. This is winedbg's error message. That's so strange. Just to be sure, did you setup and run this application in Japanese locale?
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #15 from kddc3s@gmail.com --- Created attachment 49765 --> https://bugs.winehq.org/attachment.cgi?id=49765 titi_taiken winedbg
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #16 from kddc3s@gmail.com --- (In reply to Sagawa from comment #14)
(In reply to kddc3s from comment #13)
But I don't know why run the executable $ wine KyonyuuFantajii.exe &> log.txt I didn't get any backtrace but a page fault
Did you meet ``Program Error'' dialog? Basically, when a page fault occurs, wine executes winedbg in background. The winedbg shows ``Program Error'' dialog. If you choose [Close] button on it, winedbg dumps backtrace information to your terminal.
I looked back your attachments, and noticed attachment 49752 [details] shows ``couldn't load main module''. This is winedbg's error message. That's so strange. Just to be sure, did you setup and run this application in Japanese locale?
Sorry,I try again it's show
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #17 from Sagawa sagawa.aki+winebugs@gmail.com --- Umm, I can't figure out what's behind it. Did you try to create new wine prefix? If not, could you create new prefix and install the software? See http://wiki.winehq.org/FAQ#wineprefix for details.
https://bugs.winehq.org/show_bug.cgi?id=37382
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | CC| |wylda@volny.cz
--- Comment #18 from Wylda wylda@volny.cz --- Removing regression keyword, as OP says it worked in 1.7.27, broken with update to wine 1.7.28 (maybe with system update), but going back to 1.7.27 did not solve the problem.
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #19 from kddc3s@gmail.com --- (In reply to Sagawa from comment #17)
Umm, I can't figure out what's behind it. Did you try to create new wine prefix? If not, could you create new prefix and install the software? See http://wiki.winehq.org/FAQ#wineprefix for details.
I re-install my Linux(Arch Linux),I get the same bugs. But I run this game on other computer(Ubuntu),It's work. I don't know this bugs is driver issue or other isuue. I will try to re-install my Linux(Arch LInux) to Ubuntu on this weekend.
https://bugs.winehq.org/show_bug.cgi?id=37382
--- Comment #20 from kddc3s@gmail.com --- I found it to be not working with Intel graphics but Nvidia or Ati during cross test.
https://bugs.winehq.org/show_bug.cgi?id=37382
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #21 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-4.5?