[Touch-packages] [Bug 1741416] [NEW] package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
Public bug reported: I noticed after a reboot that this was an issue for some reason after the system tried to upgrade apport: Start-Date: 2018-01-05 07:44:52 Commandline: /usr/bin/unattended-upgrade Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), apport-gtk:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-problem-report:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2018-01-05 07:45:10 I fixed it with: apt-get dist-upgrade -f ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 Uname: Linux 4.14.8-041408-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashReports: 600:0:116:145106:2018-01-05 07:45:09.131217479 +:2018-01-05 07:45:10.131217479 +:/var/crash/apport.0.crash Date: Fri Jan 5 07:45:10 2018 DuplicateSignature: package:apport:2.20.1-0ubuntu2.15 Setting up apport (2.20.1-0ubuntu2.15) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-05-29 (220 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1741416 Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 Status in apport package in Ubuntu: New Bug description: I noticed after a reboot that this was an issue for some reason after the system tried to upgrade apport: Start-Date: 2018-01-05 07:44:52 Commandline: /usr/bin/unattended-upgrade Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), apport-gtk:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-problem-report:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2018-01-05 07:45:10 I fixed it with: apt-get dist-upgrade -f ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 Uname: Linux 4.14.8-041408-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashReports: 600:0:116:145106:2018-01-05 07:45:09.131217479 +:2018-01-05 07:45:10.131217479 +:/var/crash/apport.0.crash Date: Fri Jan 5 07:45:10 2018 DuplicateSignature: package:apport:2.20.1-0ubuntu2.15 Setting up apport (2.20.1-0ubuntu2.15) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-05-29 (220 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741416/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
This is incredibly annoying, if you leave your computer permanently on sessions mount up each time you lock your screen, eventually sessions pile up to the point where you notice your computer running very slowly. This bug has been there since Xubuntu 14.04 was released. Most people do not notice this issue because they switch their computers off or do not lock their screens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed Status in Light Display Manager: New Status in lightdm package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: dm-tool lock starts a new lightdm greeter (for unlocking) and a new logind session. After unlocking the greeter disappears, but the logind session never closes. loginctl session status c24 reports something like: c24 - lightdm (103) Since: Thu 2014-05-22 18:38:27 CEST; 30min ago Leader: 7872 Seat: seat0; vc8 Display: :1 Service: lightdm-greeter; type x11; class greeter State: closing CGroup: systemd:/user/103.user/c24.session └─7907 init --user --startup-event indicator-services-start This results in an accumulation of stale lightdm sessions after using e.g. a session locker for a while. I get this issue on a freshly installed and fully updated Xubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
To get rid of the proliferation of sessions I run this on a script:
loginctl | awk '$3~/lightdm/ {print $1}' | xargs -I{} loginctl
terminate-session {}
ps aux | awk '$0~/^[l]ightdm.*indicator-services-start/ {print $2}' | xargs
-I{} kill -9 {}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1322275
Title:
lightdm sessions started by dm-tool lock (or a session locker) never
get closed
Status in Light Display Manager:
New
Status in lightdm package in Ubuntu:
Confirmed
Status in upstart package in Ubuntu:
Confirmed
Bug description:
dm-tool lock starts a new lightdm greeter (for unlocking) and a new
logind session. After unlocking the greeter disappears, but the logind
session never closes. loginctl session status c24 reports something
like:
c24 - lightdm (103)
Since: Thu 2014-05-22 18:38:27 CEST; 30min ago
Leader: 7872
Seat: seat0; vc8
Display: :1
Service: lightdm-greeter; type x11; class greeter
State: closing
CGroup: systemd:/user/103.user/c24.session
└─7907 init --user --startup-event indicator-services-start
This results in an accumulation of stale lightdm sessions after using
e.g. a session locker for a while.
I get this issue on a freshly installed and fully updated Xubuntu
14.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394193] Re: 114 instances of indicator-sound-service running
I have the same proble, I have found 29 instances of indicator-sound-
service running on my box.
I run Xubuntu 14.04.1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1394193
Title:
114 instances of indicator-sound-service running
Status in indicator-sound package in Ubuntu:
Confirmed
Bug description:
I have at the moment 114 instances of indicator-sound-service running.
I can get rid of them by running "sudo killall indicator-sound-service".
After which, in about two seconds, 114 new indicator-sound-service processes
are started.
$ ps aux | grep indicator-sound-service | grep lightdm | wc -l
114
$ ps aux | grep indicator-sound-service | grep lightdm | wc -l
lightdm 32320 0.0 0.0 54320 612 ?Ds 15:17 0:00
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32321 0.0 0.0 54320 612 ?Ds 15:17 0:00
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32322 0.0 0.0 54320 616 ?Ds 15:17 0:00
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32323 0.0 0.0 54320 616 ?Ds 15:17 0:00
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32324 0.0 0.0 54320 612 ?Ds 15:17 0:00
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32325 0.0 0.0 54320 612 ?Ds 15:17 0:00
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
lightdm 32326 0.0 0.0 54320 616 ?Ds 15:17 0:00
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
etc...
I'm not an expert, but I don't think I need 114 instances of
indicator-sound-service.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ActionStates: ({'mute': (true, signature '', []), 'phone-settings':
(true, '', []), 'next.gmusicbrowser.desktop': (true, '', []), 'mic-volume':
(true, '', [<0.14678955078125>]), 'scroll': (true, 'i', []),
'play-playlist.gmusicbrowser.desktop': (true, 's', []),
'gmusicbrowser.desktop': (true, '', [<{'running': , 'state':
<'Paused'>}>]), 'desktop-settings': (true, '', []), 'volume': (true, 'i',
[<0.8486785888671875>]), 'root': (true, '', [<{'title': <'Sound'>,
'accessible-desc': <'Volume (84%)'>, 'icon': <('themed',
<['audio-volume-high-panel', 'audio-volume-high', 'audio-volume', 'audio']>)>,
'visible': }>]), 'previous.gmusicbrowser.desktop': (true, '', []),
'play.gmusicbrowser.desktop': (true, '', [<'Paused'>])},)
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 19 15:20:57 2014
InstallationDate: Installed on 2013-05-20 (548 days ago)
InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120817.3)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to trusty on 2014-04-29 (204 days ago)
upstart.indicator-sound.log:
(process:2208): GLib-GObject-CRITICAL **: g_object_unref: assertion
'G_IS_OBJECT (object)' failed
** (process:32533): CRITICAL **: volume_control_set_volume_internal:
assertion '_tmp1_ == PA_CONTEXT_READY' failed
** (process:32533): CRITICAL **: file /build/buildd/indicator-
sound-12.10.2+14.04.20140401/obj-x86_64-linux-gnu/src/volume-
control.c: line 1775: uncaught error:
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface
(g-dbus-error-quark, 16)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1394193/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
Unbelievable Since this bug was originally released: 14.04 has had 4 mayor updates, 14.04.1, 14.04.2, 14.04.3, 14.04.4, soon to be .5, 16.04 has been released (soon to be 16.04.1) and this bug is still there. It is BASIC issues like these that give Linux distros a bad name/reputation, locking the screen is such a basic piece of functionality that it is mind boggling that for a start this is even an issue, without getting into the fact that years have gone by and officially nothing have been done about it other than 2 years later recognize it as a bug. :-( Let's hope this bug gets fixed solely by the inertia of upstream, because if we have to wait for Canonical we'll die of old age. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed Status in Light Display Manager: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: dm-tool lock starts a new lightdm greeter (for unlocking) and a new logind session. After unlocking the greeter disappears, but the logind session never closes. loginctl session status c24 reports something like: c24 - lightdm (103) Since: Thu 2014-05-22 18:38:27 CEST; 30min ago Leader: 7872 Seat: seat0; vc8 Display: :1 Service: lightdm-greeter; type x11; class greeter State: closing CGroup: systemd:/user/103.user/c24.session └─7907 init --user --startup-event indicator-services-start This results in an accumulation of stale lightdm sessions after using e.g. a session locker for a while. I get this issue on a freshly installed and fully updated Xubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
For those desperate because they work for companies who take locking
screen as a serious thing, this is the workaround I came with, have been
running for a few weeks and it does the job well so far.
The script if run via cron every 10 mins will keep your system clean of
lightdm dead sessions, your system will not get sluggish over time, this
is not an ideal solution but it is a good compromise until the issue is
fixed for good.
[begin file: lightdm_clean.sh]
#!/bin/bash
# Cleans lightdm session leftovers in Ubuntu 14.04.x
# Christian Uceda 2015 v0.0.2
set -u
declare PID=""
declare -i SESSION_COUNTER=0
declare -i INDICATOR_COUNTER=0
declare STATUS=""
declare SESSION=""
declare CRONMODE=""
# Send output to the console if not running on cron mode
function echo_print(){
if [ ! "${CRONMODE}" == "yes" ]
then
echo -e "${1:-}"
fi
}
# -8<- Script body
# Root required
if [ $(id -u) -ne 0 ]
then
echo -e "\nI can only run as root.\n"
exit 1
fi
if [ "${1:-}" == "-cron" ]
then
CRONMODE="yes"
fi
# Get rid of lightdm "closing" sessions
while read SESSION
do
STATUS=$(loginctl session-status "${SESSION}" | awk '$1~/State/ {print $2}')
if [ "${STATUS}" == "closing" ]
then
((SESSION_COUNTER++))
echo_print "Teminating session: ${SESSION}"
loginctl kill-session "${SESSION}" &>/dev/null
fi
done < <(loginctl | awk '$3~/lightdm/ {print $1}')
echo_print "\nTerminated: ${SESSION_COUNTER} sessions.\n"
# Notify if there are still some stray indicators (if not running in cron mode)
can be removed if desired.
# I used it to verify the operation did not left any stray indicators.
if [ ! "${CRONMODE}" = "yes" ]
then
while read PID
do
((INDICATOR_COUNTER++))
if [ ! "${PID}" == "" ]
then
echo_print "Found indicator pid: ${PID}"
fi
done < <(ps aux | awk '$0~/^[l]ightdm.*indicator-services-start/ {print
$2}')
echo_print "Found: ${INDICATOR_COUNTER} stray indicators.\n"
fi
exit 0
[end of file]
To test it lock and unlock the screen a couple of times and then run it
manually, run it from root's cron like:
*/10 * ** */usr/local/sbin/lightdm_clean.sh -cron
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1322275
Title:
lightdm sessions started by dm-tool lock (or a session locker) never
get closed
Status in Light Display Manager:
New
Status in lightdm package in Ubuntu:
Confirmed
Status in upstart package in Ubuntu:
Confirmed
Bug description:
dm-tool lock starts a new lightdm greeter (for unlocking) and a new
logind session. After unlocking the greeter disappears, but the logind
session never closes. loginctl session status c24 reports something
like:
c24 - lightdm (103)
Since: Thu 2014-05-22 18:38:27 CEST; 30min ago
Leader: 7872
Seat: seat0; vc8
Display: :1
Service: lightdm-greeter; type x11; class greeter
State: closing
CGroup: systemd:/user/103.user/c24.session
└─7907 init --user --startup-event indicator-services-start
This results in an accumulation of stale lightdm sessions after using
e.g. a session locker for a while.
I get this issue on a freshly installed and fully updated Xubuntu
14.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
