[Touch-packages] [Bug 1598505] Re: adb usage has typo disbled => disabled

2018-07-14 Thread Kevin Dalley
** Summary changed: - adb usage has typo disabled => disabled + adb usage has typo disbled => disabled -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1598505 Title:

[Touch-packages] [Bug 1588395] Re: 70gconfd_path-on-session doesn't quote DESKTOP_SESSION and fails if it contains a space

2018-06-26 Thread Kevin Dalley
Add double quotes around the right hand side of the assignment definitely solved the problem for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1588395 Title:

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-06-18 Thread Kevin Dalley
I did not install the image, just ran it from the USB stick. By default, it does not not have a login screen, since there is a single user, I believe. I added a second user, and logged in to that user, which was successful. But this may be different from what I see on my long-installed system.

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-06-18 Thread Kevin Dalley
Finally getting back to this. My notes on setting enable_rc6 aren't very good. I may have started using it as a possible way to extend battery life, as mentioned here. I don't notice a difference now that I have removed it. https://askubuntu.com/questions/93654/why-does-my-computer-get-less-

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Kevin Dalley
Thanks for your suggestions. I just installed: gnome-session-flashback Working: Gnome Flashback (Metacity) not working: Gnome Flashback (Compiz) And a new item in /var/crash: ** Attachment added: "/var/crash/_usr_lib_gnome-initial-setup_gnome-initial-setup.1000.crash"

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Kevin Dalley
Since filing this bug, I have been successfully using lxdm as a worked around, with lxde Recently, after I open this bug, I built my own version of xserver-xorg-input-synaptics following the instructions here:

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Kevin Dalley
Since filing this bug, I have been successfully using lxdm as a worked around, with lxde Recently, after I open this bug, I built my own version of xserver-xorg-input-synaptics following the instructions here:

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Kevin Dalley
** Attachment added: "/var/crash/_usr_bin_xfce4-power-manager.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144822/+files/_usr_bin_xfce4-power-manager.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Kevin Dalley
** Attachment added: "/var/crash/_usr_bin_plasmashell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144821/+files/_usr_bin_plasmashell.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Kevin Dalley
** Attachment added: "/var/crash/_usr_sbin_unity-greeter.119.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144823/+files/_usr_sbin_unity-greeter.119.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Kevin Dalley
** Attachment added: "/var/crash/_usr_bin_kwin_wayland.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144820/+files/_usr_bin_kwin_wayland.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10

2018-05-26 Thread Kevin Dalley
After removing: i915.i915_enable_rc6=1 I still have problems. I'll attach a few files from /var/crash ** Attachment added: "From /var/crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+attachment/5144819/+files/_usr_bin_ksplashqml.1000.crash -- You received this bug

[Touch-packages] [Bug 1771232] Re: Lightdm no longer works after 18.04 upgrade

2018-05-14 Thread Kevin Dalley
** Attachment added: "Results of systemctl status lightdm" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1771232/+attachment/5139562/+files/lightdm-status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm

[Touch-packages] [Bug 1771232] Re: Lightdm no longer works after 18.04 upgrade

2018-05-14 Thread Kevin Dalley
I commented out pam_kwallet.so in /etc/pam.d/ lightdm and lightdm-greeter since this shared library does not exist, and I received warning messages about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu.

[Touch-packages] [Bug 1771232] [NEW] Lightdm no longer works after 18.04 upgrade

2018-05-14 Thread Kevin Dalley
Public bug reported: Both lightdm and gdm3 no longer work after the 18.04 upgrade, though I have been able to use lxdm, somewhat, if I use LXDE. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux

[Touch-packages] [Bug 1770306] [NEW] X display is black after 18.04 upgrade from 17.10

2018-05-09 Thread Kevin Dalley
Public bug reported: I can manually start lightdm, and that will give me a login screen, Unfortunately, most of the desktop environments crash after login. Only plasma gives me a little bit of clients, though even plasma complains All shell packages missing And Vboxclient warning Under 17.10,

[Touch-packages] [Bug 1620774] [NEW] lxc container does not start: cgroupfs failed to detect cgroup metadata

2016-09-06 Thread Kevin Dalley
Public bug reported: lxc container failed to start until after I installed cgroupfs-mount After a recent upgrade, I received the following error messages when start an lxc container: kevin@awabi:~$ sudo lxc-start -F -n escale_build lxc-start: cgroups/cgfs.c: cgfs_init: 2288 cgroupfs failed to

[Touch-packages] [Bug 1598505] [NEW] adb usage has typo disabled => disabled

2016-07-02 Thread Kevin Dalley
Public bug reported: type "adb shell help" get the following output, include "disbled" below Please correct disbled to disabled pm list packages: prints all packages, optionally only those whose package name contains the text in FILTER. Options: -f: see their associated file. -d:

[Touch-packages] [Bug 1598459] [NEW] adb man page has incorrect link

2016-07-02 Thread Kevin Dalley
Public bug reported: The man page for adb has the following link: http://developer.android.com/guide/developing/tools/adb.html This link no longer exists The following link is a better link: https://developer.android.com/studio/command-line/adb.html ProblemType: Bug DistroRelease: Ubuntu

[Touch-packages] [Bug 1596248] Re: Touchpad stops working occasionally

2016-06-25 Thread Kevin Dalley
** Attachment added: "dmesg_boot" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+attachment/4690364/+files/dmesg_boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1596248] Re: Touchpad stops working occasionally

2016-06-25 Thread Kevin Dalley
** Attachment added: "List of devices" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+attachment/4690363/+files/devices -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1596248] Re: Touchpad stops working occasionally

2016-06-25 Thread Kevin Dalley
** Attachment added: "New dmesg entries" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+attachment/4690365/+files/dmesg_diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1596248] Re: Touchpad stops working occasionally

2016-06-25 Thread Kevin Dalley
** Attachment added: "Full Xorg.0" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+attachment/4690362/+files/Xorg.0.log_tmp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1596248] [NEW] Touchpad stops working occasionally

2016-06-25 Thread Kevin Dalley
Public bug reported: Occasionally, my cursor stops following my mouse movements. I followed instructions described here: https://wiki.ubuntu.com/DebuggingTouchpadDetection If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in the kernel itself and you should follow these

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-13 Thread Kevin Dalley
I suggest that README.Debian (or Ubuntu) mention the workarounds regarding bind9 and ipv6. It might save some time in debugging lxc problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-13 Thread Kevin Dalley
What I should do is try to back out some of my changes and determine whether I can duplicate the problem. Then I can determine which changes matter and which ones don't. I won't have time for a few days, but I will do my best. -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-12 Thread Kevin Dalley
And suddenly, it has started working. I don't know why. I did a reboot sudo systemctl status lxc-net The above command suddenly had results which looked familiar, in a good way. Before this, I had unsuccessfully tried a few of the sample lxc. Perhaps I updated something which fixed the

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-10 Thread Kevin Dalley
*** This bug is a duplicate of bug 1240757 *** https://bugs.launchpad.net/bugs/1240757 I had missed restart lxc-net. Unfortunately, that didn't make any difference. kevin@awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log --logpriority 3 -F lxc-start: conf.c: instantiate_veth:

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-09 Thread Kevin Dalley
*** This bug is a duplicate of bug 1240757 *** https://bugs.launchpad.net/bugs/1240757 Thanks for your help. Unfortunately, I didn't have any luck with this either. I added listen-on { ! 10.0.3.1; }; just before the final "}" line. restarted bind9, and I have the same error

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-09 Thread Kevin Dalley
*** This bug is a duplicate of bug 1240757 *** https://bugs.launchpad.net/bugs/1240757 I have now added listen-on-v6 { none; }; restarted bind9, and again nothing: kevin@awabi:~/src$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log --logpriority 3 -Flxc-start: conf.c:

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-06 Thread Kevin Dalley
kevin@awabi:~/notes/security$ sudo netstat -lap| grep LISTEN [sudo] password for kevin: tcp0 0 usscc-mvetter.co:domain *:* LISTEN 1192/named tcp0 0 192.168.43.174:domain *:* LISTEN 1192/named tcp0

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-05 Thread Kevin Dalley
Thanks again. kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. kevin@awabi:~/tmp$ sudo brctl

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-04 Thread Kevin Dalley
Thanks. kevin@awabi:~$ sudo brctl show bridge name bridge id STP enabled interfaces virbr0 8000.52540063031d yes virbr0-nic kevin@awabi:~$ sudo ifconfig -a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-04 Thread Kevin Dalley
Thanks. kevin@awabi:~$ sudo lxc-start -n escale_build -F -l trace -o /dev/stdout lxc-start 1446650865.960 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /var/lib/lxc/escale_build/config lxc-start 1446650865.961 WARN lxc_confile - confile.c:config_pivotdir:1801 -

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-03 Thread Kevin Dalley
Host is: Linux awabi 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux container is: Linux escalebuild 3.16.0-51-generic #69~14.04.1-Ubuntu SMP Wed Oct 7 15:32:41 UTC 2015 x86_64 GNU/Linux here is output from my attempt to start: kevin@awabi:~$ sudo

[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

2015-11-02 Thread Kevin Dalley
I upgraded to Wiley, and the problem has shown up again. I haven't managed to fix it yet under Wiley, though I could fix it under Vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1451232] Re: container does not receive IP address after 15.04 upgrade

2015-05-06 Thread Kevin Dalley
And, so far, these steps are needed each time I reboot. 2 reboots after initial success. As you suggested, stopping and restarting the lxc-net systemd job is necessary. Just starting it does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1451232] Re: container does not receive IP address after 15.04 upgrade

2015-05-05 Thread Kevin Dalley
Thanks. That works. Stopping and starting systemtl once fixed the problem. I did have some issues with the upgrade in general, and discovered a memory problem. Bad memory is now gone. Perhaps that was responsible for some of the problem. Perhaps not. I expected that reinstalling lxc with good

[Touch-packages] [Bug 1451232] Re: container does not receive IP address after 15.04 upgrade

2015-05-04 Thread Kevin Dalley
Thanks. No sign of lxcbr0. kevin@nereocystis:/home/kevin$ ps -ef | grep lxcbr0 kevin17684 17583 0 13:06 pts/000:00:00 grep lxcbr0 I attached the original config file which does not work under 15.04, but did work under 14.10 and 14.04. ** Attachment added: Original config which does

[Touch-packages] [Bug 1451232] [NEW] container does not receive IP address after 15.04 upgrade

2015-05-03 Thread Kevin Dalley
Public bug reported: Perhaps this is an upgrade issue, perhaps it is a installation issue. In either case, there should be more information about upgrading lxc. After upgrading to Ubuntu 15.04, my container no longer started. After upgrading, I had to remove the following line from the config