[Bug 49597] New: Guitar Pro 7.5 can't open valid .gp files once they have been changed in any way (like composing), also cannot open newly created .gp files

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49597

Bug ID: 49597
           Summary: Guitar Pro 7.5 can't open valid .gp files once they
                    have been changed in any way (like composing), also
                    cannot open newly created .gp files
           Product: Wine
           Version: unspecified
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Guitar Pro 7.5.4 Build 1799 can't open valid .gp files once they have been
changed in any way (like composing), also cannot open newly created .gp files.

The program fails to load legitimate gp files unless they have not been altered
since before the last wine update. Changing anything in a gp file, like
correcting notations or rewriting a song/sound as well as creating a new file
leads to those files not being able to load once the program tries to load them
in again in another instance (for example after closing Guitar Pro 7.5 or after
closing the file itself). Guitar Pro 7.5.4 freezes (becomes unresponsive) and
has to be shut down via commands or similar means to be fully closed and
reopened. Reopening however does not fix the issue.

Due to this bug it has become fully impossible to compose music or alter
existing songs as those files won't open the next time a user would like to use
them. In that way it is a critical bug for composers and problematic for
teachers.

[Bug 49597] Guitar Pro 7.5 can't open valid .gp files once they have been changed in any way (like composing), also cannot open newly created .gp files

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49597

--- Comment #1 from Austin English  ---
Please attach the terminal output.

Did this work in previous application/wine versions?

Is there a free demo/download available that shows this issue?

[Bug 49597] Guitar Pro 7.5 can't open valid .gp files once they have been changed in any way (like composing), also cannot open newly created .gp files

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49597

--- Comment #2 from Davin Dittrich  ---
(In reply to Austin English from comment #1)
> Please attach the terminal output.
>
> Did this work in previous application/wine versions?
>
> Is there a free demo/download available that shows this issue?

I unfortunately don't know how to attach or even read the terminal output, so I
cannot help you there.

This link provides you with a trial version for 30 days, but I cannot say for
sure that it has the same issue. It should, but I cannot guarantee it.

https://www.guitar-pro.com/en/index.php?pg=download&software=gp7demo

To create a file that does not work just open a new file and change anything in
it, like adding a new note, working on the notations etc. you don't need any
real knowledge on the program to do so. Just click into the notation, enter any
number, safe the file, close the program and you got yourself a test subject.

By now I could verify that the same bug appears on the system of a friend which
has the same software config (Wine 5.12-1, Guitar Pro 7.5.4 Build 1799).

Also, sorry for the very late reply

[Bug 49597] Guitar Pro 7.5 can't open valid .gp files once they have been changed in any way (like composing), also cannot open newly created .gp files

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49597

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from joaopa  ---
Explain how to add a new note or a notation. I did not find how to do.

to collect a console output: in a terminal
cd ~/.wine/drive_c/Program Files/Arobas Music/Guitar Pro 7
wine GuitarPro7.exe&>~/log.txt

and attach to this bug the file log.txt