package bluetooth-touch 0.3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[mathieg2]

Trying out ubuntu-next from a ubuntu-desktop installation - didnt work - so I have reverted back.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: bluetooth-touch 0.3.1
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
Date: Sat Mar 28 14:43:25 2015
DuplicateSignature: package:bluetooth-touch:0.3.1:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2013-07-09 (627 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
RelatedPackageVersions:
 dpkg 1.17.24ubuntu1
 apt 1.0.9.7ubuntu3
SourcePackage: bluetooth-touch
SystemImageInfo:
 current build number: 0
 device name:
 channel: daily
 last update: Unknown
Title: package bluetooth-touch 0.3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to vivid on 2015-03-28 (0 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Neo Nengrong Qu (qunengrong)]

I am facing the same problem while installing the ubuntu-desktop-next :
dpkg: error processing package ubuntu-desktop-next (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 bluetooth-touch
 ubuntu-desktop-next
E: Sub-process /usr/bin/dpkg returned an error code (1)

error log :
neo@superstar:~$ systemctl status bluetooth-touch.service
● bluetooth-touch.service - Bluetooth init for Touch devices
   Loaded: loaded (/lib/systemd/system/bluetooth-touch.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since 三 2015-05-06 23:00:18 CST; 54s ago
  Process: 11727 ExecStart=/bin/sh -ec SCRIPT=/usr/share/bluetooth-touch/`getprop ro.product.device`; [ ! -x $SCRIPT ] || exec $SCRIPT (code=exited, status=126)
 5月 06 23:00:18 superstar systemd[1]: Starting Bluetooth init for Touch devices...
 5月 06 23:00:18 superstar sh[11727]: /bin/sh: 1: exec: /usr/share/bluetooth-touch/: Permission denied
 5月 06 23:00:18 superstar systemd[1]: bluetooth-touch.service: control process exited, code=exited status=126
 5月 06 23:00:18 superstar systemd[1]: Failed to start Bluetooth init for Touch devices.
 5月 06 23:00:18 superstar systemd[1]: Unit bluetooth-touch.service entered failed state.
 5月 06 23:00:18 superstar systemd[1]: bluetooth-touch.service failed.
neo@superstar:~$ ls /usr/share/bluetooth-touch/
flo grouper maguro mako

I have checked this command : getprop ro.product.device, but it's result is empty. log as follow:
neo@superstar:~$ getprop ro.product.device

neo@superstar:~$

please help to solve the problem. thx

[zyklo (zyklosmile)]

sudo gedit bluetooth-touch.service

comment out ExecStart with # in front and write some dummy stuff like "ExecStart=/bin/sh -ec 'echo bluetooth-touch'".

The issue is, that `getprop ro.product.device` is empty and so this script tries to call another script, but it's not a script but a directory and so the operation fails -.-

After change call
sudo dpkg --configure bluetooth-touch

The thing is, my pc has no bluetooth, so I dont care, if this works, but it seems to be a dependency of ubuntu-desktop-next.

[groby (groby)]

Still waiting for a fix! Hope on 15.10!

After the installation failed, I noticed that WiFi doesn't work anymore after reboot/suspend. Some of the files were already installed on the system, untill the fail-message was displayed. So I had to make a complete uninstall of bluetooth-touch, in order to make WiFi work again.

Maybe an additional Bug on bluetooth-touch?!

[Launchpad Janitor (janitor)]

This bug was fixed in the package bluetooth-touch - 0.3.2

---------------
bluetooth-touch (0.3.2) wily; urgency=medium

  * Update the systemd job to check that $SCRIPT is a regular file before
    attempting to run it. (LP: #1437671)

 -- Christopher James Halse Rogers <email address hidden> Mon, 19 Oct 2015 10:17:56 +1100