[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

2018-01-05 Thread Christian Uceda
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

[Touch-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed

2016-07-08 Thread Christian Uceda
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

[Touch-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed

2016-01-11 Thread Christian Uceda
, 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=""

[Touch-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed

2015-05-22 Thread Christian Uceda
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

[Touch-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed

2015-05-22 Thread Christian Uceda
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

[Touch-packages] [Bug 1394193] Re: 114 instances of indicator-sound-service running

2015-02-09 Thread Christian Uceda
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.