Skip to main content
andreaf87356109
Participating Frequently
January 7, 2016
Question

fpsaud Segmentation Fault 11

  • January 7, 2016
  • 2 replies
  • 5475 views

Hi guys,

some times ago I configured a webserver and necessary scripts for a background update configuration: Windows clients works fine so I decided to join a MacOSX client too (El Capitan 10.11.1)

So I installed an old version of Flash Player (e.g. 18x or 19x) and performed a reboot, then I configured the mms.cfg with required parameters.

The first time I launched fpsaud manually from root shell: I saw the client making HTTP requests to the webserver, also Library/Logs/FlashPlayerInstallManager.log log reports a successful operation:

2016-01-07 23:34:57 +0100   IM: ---------- log start ----------

2016-01-07 23:34:57 +0100   IM: All install checks pass

2016-01-07 23:34:57 +0100   IM: [install started]

2016-01-07 23:34:58 +0100 FIN: [finalizer started]

2016-01-07 23:34:58 +0100 FIN: Compression Output Path: '/Library/Internet Plug-Ins/Flash Player.plugin'.

2016-01-07 23:34:58 +0100 FIN: Compression Input Path: '/Library/Internet Plug-Ins/Flash Player.plugin.lzma'.

2016-01-07 23:35:00 +0100 FIN: Reading previous version file

2016-01-07 23:35:01 +0100 FIN: Creating previous version file

2016-01-07 23:35:01 +0100 FIN: [finalizer succeeded]

installer: Package name is Adobe Flash Player

installer: Upgrading at base path /

installer: The upgrade was successful.

2016-01-07 23:35:02 +0100   IM: [install succeeded]

2016-01-07 23:35:02 +0100   IM: Install succeeded with exit code: 0.

2016-01-07 23:35:02 +0100   IM: ----------  log end  ----------

but fpsaud exit with Segmentation Fault: 11 error.

From then, when I try to launch the binary again, Segmentation Fault: 11 is immediatly reported, everytime.

Any idea about this behaviour?

Now Flash is the lastest version (v20,0,0,267).

BR,

-f

This topic has been closed for replies.

2 replies

_maria_
Community Manager
Community Manager
January 7, 2016

Hi,

I don't recall seeing the Segmentation Fault error you're seeing.  I'll forward your post to the developer and get back to you.

--

Maria

andreaf87356109
Participating Frequently
January 8, 2016

Thanks Maria. Let me know if further information are required (for example more info about fpsaud binary)

jeromiec83223024
Inspiring
January 7, 2016

If you're using an installer that pre-dates the version of the operating system that you're using, it's certainly possible that you might run into a compatibility issue.

The intent is for you to always run the latest Flash Player.  We're not going to go back and amend old versions, but if you have problems with the current builds, we'd be happy to investigate further.

andreaf87356109
Participating Frequently
January 8, 2016

I used an older version only to test the update mechanism... how can I test the repository if I install the latest version of Flash?

jeromiec83223024
Inspiring
January 8, 2016

You could do it on the latest version of the operating system that existed at the time the version you're testing with shipped.  You can multi-boot a mac to different OS versions. 

The reality is that we're not going to re-release a Flash Player 18 to fix this.  The exception would be the extended support release, but that doesn't help you test the release-channel upgrade path.  You'll need to find a working config to test with.