package prey (not installed) failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

Bug #1449725 reported by Jordilz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
prey (Ubuntu)
New
Undecided
Unassigned

Bug Description

Error upstart when isntall

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: prey (not installed)
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
Date: Tue Apr 28 20:54:51 2015
DuplicateSignature: package:prey:(not installed):el subproceso instalado el script post-installation devolvió el código de salida de error 1
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2015-04-26 (2 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt 1.0.9.7ubuntu4
SourcePackage: prey
Title: package prey (not installed) failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jordilz (jordilz) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Jordilz (jordilz) wrote :

Hi!

Version 1.3.9 of prey crash when install.

Actually Ubuntu 15.04 d'ont work with upstart, now work with systemd

Control center d'ont install in ubuntu but device is controlled ok way web

Thanks

Hola!

Versión 1.3.9 falla al finalizar la instalación

Actualmente ubuntu 15.04 no utiliza upstart sino systemd.

Por ello no se llega a instalar la aplicación en ubunru (Centro de control) pero si que se puede controlar el dispositivo desde la página web, indicando incluso la versión correcta de prey instalada em ubuntu

Gracias

Revision history for this message
Luke Williams (wililupy) wrote :

The way I got this to work on my laptop was after I installed 1.3.9, I went into /sbin and renamed initctl temporarily to initctl.orig
 <sudo mv /sbin/initctl /sbin/initctl.orig>

I then ran sudo /usr/lib/prey/current/bin/prey config hooks post_install
and everything completed successfully. I then ran sudo /usr/lib/prey/current/bin/prey config gui
and configured it to Prey and everything checked out. I then put initctl back to normal: sudo mv /sbin/initctl.orig /sbin/initctl
and everything is working as designed.

The reason you get this error is because the script that it runs to install the service looks for initctl and if it finds it, it tries to use upstart. Since 15.04 uses systemd, it fails and crashes out before it can build the systemctl module, even thought prey can do this, it sees initctl and uses that instead. Telling it that it isn't there would be better, or having Prey update the script to look for systemctl first instead of initctl would be preferred.

Revision history for this message
Luke Williams (wililupy) wrote :

I did run into one issue with my fix, and that is that the package never seems to get to an installed state, even though it is installed. Looking at the postinst script in the deb package, it tries to run /usr/lib/prey/current/bin/prey config gui and for some unknown reason it fails to load it properly, which causes the package to go into a pending config state. So every time I tried ran aptitude for updates or install new packages, it deleted the prey-agent.service. To fix this, I modified the /var/lib/dpkg/status so that under Package: prey, under Status: it says install ok installed and everything is good to go now.

I then had to redo my previous procedure to get the prey-agent.service back and up and running, but now I don't have any other issues. I may try to modify the .deb and the postinst script so that it works properly with Ubuntu 15.04. I'll let you know.

Revision history for this message
Jordilz (jordilz) wrote :

Thanks Wililupy!

I've gotten it to work as you say.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.