Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-2320

macOS: Picard 2.6.4 segfault upon authorization/login prompt

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Normal Normal
    • 2.7.0b3
    • 2.6.4
    • None
    • None
    • Mac OS X 10.12.6
      Model: MacPro5,1, BootROM MP51.007F.B03, 8 processors, Quad-Core Intel Xeon, 2.4 GHz, 64 GB, SMC 1.39f11

      Hello.  I was requested to submit a ticket/bug-report for Picard (which overall is awesome by the way) for it segfaulting repeatedly when prompting for login.  I am unfortunately hard-tied to the 10.12 version of OSX as I often have to use this system with a pricy piece of audio hardware that does not support newer versions of OSX.

       

      This is discussed here:https://community.metabrainz.org/t/authorization-request-is-on-a-loop/431540/18

       

      When I receive the pop-up prompting login (even though the preferences says I am logged in), I click yes, copy the code returned from the website, and then paste the code in, only to have the application segfault.  If I click "yes" and then click 'cancel', the application will crash every single time. Oftentimes, even if I click ‘no’ the application segfaults as well. 

       

      This repeated prompting to login (when the preferences dialogue indicates that I am already currently logged in) is particularly painful in that I will keep making attempts to get the auth code accepted, and even if it is accepted and the application does not crash, I again get prompted some time later.  So it's not like a successful auth even persists within an actively running instantiation of the application.

       

      I was trying to post the segfault details reported by OSX for both when the fault occurs during trying to apply the valid OAuth code as well as for a fault when I select "No" to login....however I am unable to submit a full segfault output due to this site's error "The entered text is too long. It exceeds the allowed limit of 32,767 characters."...so I am adding the segfault outputs as text attachments.

       

       

        1. Screen Shot 2021-11-12 at 4.12.45 PM.png
          128 kB
          humbuckerlove
        2. Screen Shot 2021-11-12 at 4.14.53 PM.png
          12 kB
          humbuckerlove
        3. segfault-click-no.txt
          190 kB
          humbuckerlove
        4. segfault-click-yes-and-submit-auth-code.txt
          150 kB
          humbuckerlove

            outsidecontext Philipp Wolfer
            humbuckerlove humbuckerlove
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                2.7.0b3