package spamassassin 3.4.1-7ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Rene Horn]

This happened with a regular upgrade from the previous version.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: spamassassin 3.4.1-7ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sat Feb 3 08:26:09 2018
DuplicateSignature:
 package:spamassassin:3.4.1-7ubuntu1
 Setting up spamassassin (3.4.1-7ubuntu1) ...
 -su: 28: /etc/profile.d/10-budgie-desktop.sh: Syntax error: word unexpected (expecting ")")
 dpkg: error processing package spamassassin (--configure):
  subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationDate: Installed on 2014-03-15 (1421 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5.1
SourcePackage: spamassassin
Title: package spamassassin 3.4.1-7ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
UpgradeStatus: Upgraded to artful on 2017-10-23 (103 days ago)

[Christian Ehrhardt  (paelzer)]

Hi Rene,
I think while the spamassasin upgrade fails the reason is in budgie desktop.

From your log:
 -su: 28: /etc/profile.d/10-budgie-desktop.sh: Syntax error: word unexpected (expecting ")")

The spamassassin upgrade tries to execute something with a login.
That will source anything in /etc/profile.d/.

Now in your case there seems to be an issue in that file.
You might check if you happen to spot the issue in there.

I have checked which bugdie package this file belongs to and found none.
Is that a custom file - if so what is the source?
In any case this is the reason for your upgrade issue.

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[fossfreedom (fossfreedom)]

please can you attach the file /etc/profile.d/10-budgie-desktop.sh to this issue. cheers

[Christian Ehrhardt  (paelzer)]

Found it
budgie-desktop-common: /etc/profile.d/10-budgie-desktop.sh

But I had no issue in it.
You might check if it is still in original state with
$ dpkg --verify budgie-desktop-common

Maybe the budgie developers can help you better, but I'd still expect a local change that needs to be fixed.

[fossfreedom (fossfreedom)]

hmm - I'm wondering what shell spamassassin is sourcing that file.

Looking at the file at the very least I think it needs a shebang statement at the top of the script file just in-case spamassasin is using something like csh/ksh etc

maybe

#!/bin/bash

or possibly

#!/bin/sh

[Launchpad Janitor (janitor)]

[Expired for budgie-desktop-environment (Ubuntu) because there has been no activity for 60 days.]