Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1392 Segfault on opening a rosegarden file

None
closed
nobody
1
2013-08-13
2013-06-14
Karl Lindén
No

When I try to open a rosegarden file I get a segfault. The error is reproducible with the following steps:

  1. Start rosegarden.
  2. Open a file using the menu (File->Open), the button in the bar or Ctrl+O.
  3. Double click on the file.
  4. Rosegarden dies with a segfault.

Note that if I in step 3 select the file and then press open everything works fine.

I'm running Rosegarden version 13.04 on Gentoo GNU/Linux.

1 Attachments

Discussion

  • Karl Lindén
    Karl Lindén
    2013-06-14

    And here is the file I used.

     
    Attachments
  • I pointed the file dialog at that file and double clicked. No crash. Nothing seems out of the ordinary.

    I went back and tried it all again with the official 13.04 release, and again, nothing seemed out of the ordinary.

    I can barely imagine remote far out scenarios where double clicking would make a difference compared to other methods of loading the file. If any of that stuff is actually true, we'll never solve it anyway. More likely, double clicking isn't the real problem, and the explanation why it behaves one way one time and differently another time is more likely some kind of pure randomness.

     
  • Karl Lindén
    Karl Lindén
    2013-06-14

    Strange that you can't reproduce it, but I definitely agree with you that it is very hard to imagine that it would do any difference but it does!

    Please see this video showing the issue:
    https://www.youtube.com/watch?v=Fc-vv8XqKuo

     
  • The video allows me to repeat various subtle things about your pattern of behavior that I wasn't doing before, but I still can't produce a crash.

    Let's compare notes. Run "./rosegarden --version" and see what it reports. I am using:

    Rosegarden version: 13.04 ("Allysand")
    Build key: 77253ca0f3
    Built against Qt version: 4.8.1

    If your build key is different, your source has been modified from the original. If you're using a different version of Qt, that could potentially explain the difference. We have definitely had bugs that occurred with one version of Qt but not another.

     
  • Karl Lindén
    Karl Lindén
    2013-06-14

    Here it is:

    $ rosegarden --version
    Rosegarden version: 13.04 ("Allysand")
    Build key: de7d5f3125
    Built against Qt version: 4.8.4
    

    The source has been modified by the patch supplied by Gentoo. I am attaching the patch, but it should not matter because it is only correcting the check for debug build.

    I tried compiling the latest SVN but I ran into exactly the same issue, so it has not already been fixed by any later commit.

    I will try to grab a previous version of Qt and see if it is related to it.

     
  • Karl Lindén
    Karl Lindén
    2013-06-14

    Installing a previous version of Qt was not a very good idea. The old ebuilds are removed so I have to mess with Qt manually if I want to test things out. I'd rather not do that just yet.

    I'm trying the bug out on different setups now to see some kind of pattern, I will post the information gradually as I discover things.

    On Debian Wheezy (stable):
    Not reproducible with the package from the package manager.

    $ rosegarden --version
    Rosegarden version: 12.04 ("Freedom")
    Build key: 6af3694df8
    Built against Qt version: 4.8.1
    

    I can try with SVN version on the Debian computer if you think that will give some necessary information.

     
  • Karl Lindén
    Karl Lindén
    2013-06-14

    Not reproducible with almost identical software (also Gentoo GNU/Linux). The latest SVN version compiled on my laptop:

    Rosegarden version: 13.06 ("Imagination")
    Build key: 0b73c83660
    Built against Qt version: 4.8.4
    

    The bug looks more and more strange...

     
  • Cannot reproduce, cannot fix.

     
    • status: open --> closed