E: internal error no file name for upstart-app-launch:i386

Bug #1323333 reported by dino99
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart-app-launch (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

when i try to reinstall that package, i get that error. This is on a system booting with 'systemd'; it has happened after having upgraded the click-apparmor (0.2.4)
This is the output when upgrading:
E: click-apparmor: subprocess installed post-installation script returned error exit status 6
E: upstart-app-launch: dependency problems - leaving unconfigured

related click-apparmor reported bug lp:1322296

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: upstart-app-launch 0.3+14.10.20140521-0ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-2.6-generic 3.15.0-rc6
Uname: Linux 3.15.0-2-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.2-0ubuntu4
Architecture: i386
CurrentDesktop: GNOME
Date: Mon May 26 17:00:06 2014
SourcePackage: upstart-app-launch
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
dino99 (9d9) wrote :
tags: added: systemd-boot
dino99 (9d9)
description: updated
Revision history for this message
dino99 (9d9) wrote :

has been fixed by the latest systemd & debhelper packages.

Changed in upstart-app-launch (Ubuntu):
status: New → Incomplete
status: Incomplete → Fix Released
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.