Ok I connected this to the internet and manually copied the oauth token over
and had the info sent.
I hope all of this is useful to fix the issue with the continue button's text.
These are files from the page before the page with the problem.
--
You received this bug notification because you
apport information
** Attachment added: "UbiquityPartman.txt"
https://bugs.launchpad.net/bugs/1965680/+attachment/5571293/+files/UbiquityPartman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/1965680/+attachment/5571294/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UbiquityDm.txt"
https://bugs.launchpad.net/bugs/1965680/+attachment/5571292/+files/UbiquityDm.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965680
apport information
** Attachment added: "UbiquityDebug.txt"
https://bugs.launchpad.net/bugs/1965680/+attachment/5571291/+files/UbiquityDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1965680/+attachment/5571290/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1965680/+attachment/5571289/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected impish ubiquity-21.10.10 ubuntu
** Description changed:
- After you select that you want to erase everything and install over it
- the button in the lower right corner says "Install Now". This should say
- "Continue" because you still need to
Am I reporting this to the right repository? ubiquity is the program
that runs when you try to install ubuntu from a live cd right?
What information do you want? I have my cell phone camera ready to go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It says
ERROR: connecting to Launchpad failed: Unable to find the server at
launchpad.net
What now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965680
Title:
it says install now when it should
Public bug reported:
When I select that it should erase a disk and install there it queries
my disks to see if my other disks with ntfs on them can be resized. This
is unnecessary since I'm not using those disks. It also takes forever.
It basically makes installing ubuntu impossible unless I
Public bug reported:
After you select that you want to erase everything and install over it
the button in the lower right corner says "Install Now". This should say
"Continue" because you still need to pick which disk to erase. It saying
"Install Now" makes it seem like that is the last step
What does rls-ff-incoming mean? Is this something that can be fixed everywhere?
I'm pretty sure it's something that happens to mysql also:
https://askubuntu.com/q/1037285
A workaround for this seems to be to use the docker snap package. snapd seems
to keep stuff running.. at least when there
*** This bug is a duplicate of bug 1880025 ***
https://bugs.launchpad.net/bugs/1880025
** This bug has been marked a duplicate of bug 1880025
apparmor="DENIED" on docker container files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
docker seems to not be able to start because of a pid file that was left behind.
This only happened on one of my hosts and hasn't happened again after fixing it.
I get these logs over and over again:
2020-04-30T06:47:38Z systemd[1]: Started Service for snap application
Public bug reported:
[ 905.842011] audit: type=1400 audit(1590090428.258:167): apparmor="DENIED"
operation="open" profile="snap.docker.dockerd" name="/usr/local/bin/start_ipfs"
pid=8466 comm="start_ipfs" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
My containers are failing to start
Maybe a workaround fix could be to restart ubuntu if dependent services
had to be stopped to update something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870876
Title:
docker stopped when
Here are people who are hit by this except for mysql:
https://askubuntu.com/questions/1037285/starting-daily-apt-upgrade-and-clean-activities-stopping-mysql-service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
attaching unattended-upgrades-dpkg.log
** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades-dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346860/+files/unattended-upgrades-dpkg.log
--
You received this bug notification
attaching unattended-upgrades.log
** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades.log"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346859/+files/unattended-upgrades.log
--
You received this bug notification because you are a
Public bug reported:
When containerd was updated in my bionic instance it stopped docker then
stopped containerd. When it was done updating containerd it brought it
back online. docker stayed stopped.
2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport
containerd python3-apport
It's working now. I'm not sure why.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821540
Title:
docker can't stop containers because of apparmor
To manage notifications about this bug go to:
I think the change in this commit isn't in my app armor profile.
https://github.com/moby/moby/commit/4822fb1e2423d88cdf0ad5d039b8fd3274b05401
What does yours look like?
$ cat /etc/apparmor.d/docker
#include
profile docker-default flags=(attach_disconnected,mediate_deleted) {
#include
Public bug reported:
Docker can't stop containers because it can't send a signal to it
because of apparmor. There is also a spelling mistake in the error
message.
$ docker stop 35
Error response from daemon: cannot stop container: 35: Cannot kill container
Public bug reported:
I can't get logs out of containers that use journald using the `docker
logs` command.
```
$ docker logs fa95590f3c6b
Error response from daemon: configured logging driver does not support reading
```
The journald logging driver usually supports reading logs. According to
What actually has to be done for something like this to be fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258597
Title:
Warning: Setting GRUB_TIMEOUT to a non-zero value when
Public bug reported:
Description:Ubuntu 12.10
Release:12.10
empathy:
Installed: 3.6.0.3-0ubuntu1
Candidate: 3.6.0.3-0ubuntu1
Version table:
*** 3.6.0.3-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
100 /var/lib/dpkg/status
The
27 matches
Mail list logo
