Public bug reported:
I was installing Ubuntu on a new computer and had entered all the data
and the installer was setting up when the installer crashed
unexpectedly.
See the apport files for more details.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2
Uname: Linux 4.12.
I did not have a special /boot directory in my partition table so boot
was part of the root (/) mount point. The root partition is on sdb1 if
that helps at all. When investigating this I did have the /boot/grub
directory, but was unabled to find the i386 directory in that tree.
To work around this
Public bug reported:
The grub-install apt upgrade does not complete successfully on my
system.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename: yakkety
Kernel: 4.8.0-32-generic
arch: X86_64
Here is the error from the apt-get upgrade
Installing for x86_6
Verified with juju version == 2.0-beta13-xenial-amd64:
$ ls -al /usr/share/bash-completion/completions/ju*
lrwxrwxrwx 1 root root 8 Jul 22 11:34
/usr/share/bash-completion/completions/juju -> juju-2.0
-rw-r--r-- 1 root root 12705 Jul 20 12:41
/usr/share/bash-completion/completions/juju-2.0
-
Since this seems to be a LXD problem please pastebin the following
commands:
sudo lxc list
sudo lxc remote add images images.linuxcontainers.org
sudo lxc launch images:ubuntu/trusty/ppc64el ubuntu-test
sudo lxc list
sudo lxc stop ubuntu-test
sudo lxc delete ubuntu-test
If those commands fail, pa
Before we can call this bug complete, the packaging should clean up the
potentially old files that would prevent the bash completion from
working correctly.
I understand we can include a post action that removes the bash
completion files from the old /etc/bash_completion.d/ directory.
Something l
After removing the old files from /etc/bash_completion.d/ I was not able
to get *any* completion to work (in new terminals).
I tried 'juju-2.0 ssh kuber' and that worked, it also started
working to run 'juju ssh kuber'
But it would not work with 'juju ssh kuber' alone until I
symbolically linked
** Summary changed:
- The tab completion on juju yeilds KeyError: 'services'
+ The tab completion on juju yields KeyError: 'services'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600257
Title:
Th
I too would like to see encryption on the tablet/phone. This is an
important feature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464697
Title:
Enable encryption as per design mock up
To manage
*** This bug is a duplicate of bug 1557346 ***
https://bugs.launchpad.net/bugs/1557346
Greetings retracing service! I tried to look at the other bug but can
not find the duplicate bug you reference. The link is dead, and when I
try to search that bug number in bugs.launchpad.net I do not find
It should be noted that I can run the hello-world docker container on my
host system, outside of lxd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560685
Title:
docker: Error response from daemon:
Serge,
$ ps -ef | grep docker
root 1387 1 0 07:44 ?00:00:10 /usr/bin/docker daemon -H fd://
mbruzek 6392 18048 0 21:27 pts/19 00:00:00 grep --color=auto docker
10 31515 28211 0 21:21 ?00:00:00 /usr/bin/docker daemon -H fd://
$ dpkg -l | grep docker
ii docker
The lxc/lxd team is wondering why the overlay driver is not included in
docker by default: https://github.com/lxc/lxd/issues/1791
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560685
Title:
docker:
Public bug reported:
I am running 16.04 Ubuntu and trying to run docker within lxd (I know
crazy right?!). While inside the LXC container we are unable to run
docker because there is an error trying to mount aufs.
We found a workaround to this problem was to add the overlay driver to
/etc/defaul
The official Docker docs refer to aufs in the Ubuntu extras:
https://docs.docker.com/engine/installation/linux/ubuntulinux/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560685
Title:
docker: Err
I got this crash on xenial 16.04 today when I tried to power off a USB
device that remained after I removed it from the system. I can reproduce
this on trusty as well on another Ubuntu system with trusty 14.04.4 LTS.
Let me know if you need anymore information.
--
You received this bug notificat
Was the fanctl suppose to return an error code in that case?
I realize the right way is to get the previous overlay and underlay values and
call:
fanatic disable-docker 250.0.0.0/8 10.0.0.0/16
And I will work on getting the charm to find the previous values and
call the correct command.
I stil
Public bug reported:
While writing a Juju layer that uses the fan technology I am running
into a problem.
The charm calls:
fanatic enable-docker 250.0.0.0/8 10.0.0.0/16
But when the overlay or underlay options are unset I want to unconfigure
the fan. I tried to use the command.
fanctl down -e
Public bug reported:
I am writing a charm layer for the fan networking component. We have
configuration for the fan overlay and underlay network. When those
values change it is not easy to get the previous values.
I would suggest/request an option on the fanatic script to deconfigure
everything.
I am trying to use gnome-lirc-properties in Utopic Unicorn 14.10 but
unable to start the program.
Here is the stack trace:
$ gnome-lirc-properties
Traceback (most recent call last):
File "/usr/bin/gnome-lirc-properties", line 31, in
gnome_lirc_properties.run(sys.argv[1:], datadir)
File
I believe the gccgo 4.9.1 compiler fix is a good thing. After
rebuilding Juju with gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb I was unable
to get the "juju ssh" problem I had seen previously. I also did some
load testing on juju with multiple bootstrap, deploy, and destroy cycles
without any juju relat
With sinzui's help I have compiled the latest version of Juju 1.20.2
with the gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb.
NOT able to reproduce the “juju ssh” panic/problem having several ssh
sessions open simultaneously and having output streaming for over 2
hours.
For clarity and review here are the
** Attachment added: "The juju logs from the 1.18.1 panic on stilson-01."
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1347322/+attachment/4161298/+files/machine_logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Public bug reported:
I am using Juju on Power 8 hardware and I get a panic when I use juju to
ssh to a system. The reproduction steps are
juju bootstrap -e local
juju deploy local:trusty/ubuntu
juju ssh ubuntu/0
(use the session to the local machine and after some time the panic
happens and the
** Attachment added: "the dmesg output from stilson-01 with version 1.18.1
installed."
https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1304754/+attachment/4160288/+files/dmesg_1.18_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I tried the package that Matthias left on the link in the last comment
(1.18.1). I received a similar but different error:
goroutine 3 [syscall]:
goroutine in C c
** Attachment added: "The dmesg output from stilson-06 (CI) machine."
https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1304754/+attachment/4160054/+files/stilson-06_dmesg_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Is there any way to verify if a Debian package has been built with this
gccgo fix?
Procedure:
I downloaded the 14.04 debian packages from:
http://juju-ci.vapour.ws:8080/job/publish-revision/690/
These packages were built on stilson-07 which has the PPA and the fixed version
of gccgo.
Then I ran
** Attachment added: "The output from dmesg on stilson-01 after installing the
deb packages."
https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1304754/+attachment/4149567/+files/dmesg_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I installed the debian packages from the CI server
http://juju-ci.vapour.ws:8080/job/publish-revision/588/
My understanding is these deb packages were built with the PPA toolchain that
has the fix installed.
I destroyed the environment, rebooted the machine (for good measure) and
find that I sti
** Attachment added: "The /var/log/syslog file from wolfe-01."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301496/+attachment/4064026/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
We just experienced the same problem on wolfe-01 today. We were
deploying charms with juju and noticed that juju status did not return
the right output.
The kernel that was running is:
Linux wolfe-01 3.13.0-21-generic #43-Ubuntu SMP Mon Mar 31 22:54:04 UTC
2014 ppc64le ppc64le ppc64le GNU/Linux
Public bug reported:
I got this error after logging in to my system today. No other system
problems that I can see. I was able to continue without rebooting or
restarting any services manually.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
I had some more time to work on this problem. After more research and
reading more information I discovered that IOMMU was not enabled on my
system. To enable IOMMU I performed the following steps on my Ubuntu
Linux server:
sudo vi /etc/default/grub
Add “intel_iommu=on” to the GRUB_CMDLINE_LINUX
Christopher,
I have not tried this scenario in any release earlier than Raring 13.04.
A google search tells me that people have been using PCI passthrough on
Ubuntu since 2009. This problem does not seem to be related to PCI
passthrough only the unbind step.
--
You received this bug notificati
Christopher,
I downloaded and installed the mainline kerel v3.12 and tried the
sequence of commands leading to the unbind command.
This time the system hung, no kernel oops but the system was
unresponsive/locked up. I was unable to use any keystroke to gain
control of my system Ctrl+c failed as
Christopher Penalver,
I finally got a chance to install 13.10 Saucy and retry this problem.
The new unbind problem happens exactly described above. Reminder I am
following these instructions: http://www.linux-kvm.org/page
/How_to_assign_devices_with_VT-d_in_KVM
I happened to be root while runni
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820994/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
Title:
Kern
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820995/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820997/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/119
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820999/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
Title:
Ke
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820996/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3821000/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3821001/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
Ti
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820992/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820998/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820993/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
Title:
Kern
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820991/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
Title:
Kernel
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820990/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
Titl
I obtained the Live CD for 13.10 amd64.
uname -a = Linux ubuntu 3.11.0-4-generic #9-Ubuntu SMP Mon Aug 26 15:21:06 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
I was following instructions described in this KVM document:
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
root@ubu
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820989/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1190120/+attachment/3820988/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190120
Title:
I applied the latest v3.10 kernel that you linked to in comment #4.
That appears to fix the kernel oops problem.
I was able to run the command:
echo :01:00.0 > /sys/bus/pci/devices/:01:00.0/driver/unbind
Without a kernel Oops problem.
So I believe the problem is fixed upstream. kernel
BUG: unable to handle kernel NULL pointer dereference at 38
IP: [] nouveau_fence_done+0xc4/0x100 [nouveau]
PGD 3c8eea067 PUD 3c8f2b067 PMD 0
Oops: [#1] SMP
...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Public bug reported:
I am trying to unbind a PCI device I received a kernel Oops.
I was following instructions described in this KVM document:
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
When I get to the unbind step:
echo :01:00.0 > /sys/bus/pci/devices/:01:00.
55 matches
Mail list logo
