On 24.09.2015 20:34, Robert Park wrote:
On Wed, Sep 23, 2015 at 11:56 PM, Simon Fels wrote:
The reason for this isn't clear yet however I modified the citrain utility
to do an device upgrade without service restart and then directly reboot the
device recently. See
https://code.launchpad.net/~mo
On Wed, Sep 23, 2015 at 11:56 PM, Simon Fels wrote:
> The reason for this isn't clear yet however I modified the citrain utility
> to do an device upgrade without service restart and then directly reboot the
> device recently. See
> https://code.launchpad.net/~morphis/phablet-tools/citrain-changes
On 24.09.2015 07:46, Steve Langasek wrote:
On Thu, Sep 24, 2015 at 08:12:22AM +1000, Michi Henning wrote:
I'm seeing this on Vivid plus overlay on my desktop as well as on my Nexus
4 when using citrain device-upgrade.
Are you sure you're seeing the same issue on a Nexus 4? The ps output shows
On Thu, Sep 24, 2015 at 08:12:22AM +1000, Michi Henning wrote:
> I'm seeing this on Vivid plus overlay on my desktop as well as on my Nexus
> 4 when using citrain device-upgrade.
Are you sure you're seeing the same issue on a Nexus 4? The ps output shows
systemd-specific tools being invoked. Thi
On 24-09-15 00:12, Michi Henning wrote:
I'm seeing this on Vivid plus overlay on my desktop as well as on my Nexus 4
when using citrain device-upgrade.
During package installation, the bluez install hangs. Looking at the processes,
I see
28628 pts/1S+ 0:00 sudo apt-get upgrade
286
I'm seeing this on Vivid plus overlay on my desktop as well as on my Nexus 4
when using citrain device-upgrade.
During package installation, the bluez install hangs. Looking at the processes,
I see
28628 pts/1S+ 0:00 sudo apt-get upgrade
28629 pts/1S+29:25 apt-get upgrade
363
6 matches
Mail list logo