At this point better to start a thread on Ubuntu forums.
https://ubuntuforums.org/forumdisplay.php?f=339
Already many similar questions and answers.
Also from live installer: Please copy & paste link to the Boot-info summary
report ( do not post report), the auto fix sometimes can create more
** Changed in: accountsservice (Ubuntu Eoan)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1841079
Title:
Speech Dispatcher an
Forgive me if this has been asked and answered, but I was pointed here
by bug #1675079 which has affected my Ubuntu 16.04 LTS server for a very
long time. I have tried time and again to understand how to fix the
problem, and I can't figure it out. I see the bug is marked as fixed,
and there are sev
Thank you for opening this bug and helping make Ubuntu better.
Can you explain what is wrong? "idk how to show you" means we also do
not know what to look for...
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubunt
** Attachment added: "log messages"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1842161/+attachment/5285897/+files/log%20messages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchp
Public bug reported:
idk how to show you
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13
Hello Jamie, or anyone else affected,
Accepted shadow into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/shadow/1:4.2-3.1ubuntu5.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Jamie, or anyone else affected,
Accepted shadow into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/shadow/1:4.5-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Jamie, or anyone else affected,
Accepted shadow into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/shadow/1:4.5-1.1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Public bug reported:
This problem occurs on Ubuntu 18.04.3 LTS (bionic).
It does not occur on Ubuntu 19.04 (disco)
The "find" and "xargs" command are provided by a patched version of the
GNU findutils package. The current version is based on release 4.6.0, but
the "--version" option shows a versi
** Package changed: xorg (Ubuntu) => duplicity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1842124
Title:
Making Backup HD NTFS
Status in duplicity package in Ub
Public bug reported:
Falhou devido a um erro desconhecido.
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File
I found the addition of the 18.04 libnss-resolve package fixed my
(intermittent) problems with name-resolution failures. Earlier comments
indicate this package was not installed. The installation alters the
nsswitch.conf file's hosts line to add "resolve [!UNAVAIL=return]"
before "dns".
--
You
The fix that worked for me is to add the libnss-resolve package. This changes
the /etc/nsswitch.conf file to actually attempt the dns lookup after the other
conditions have started the UDB fallback mode.
Bug 1727237 had a comment requesting if libnss-resolve were installed, answered
"no", but n
Public bug reported:
Ubuntu is stuck with tracker 2.1.8 and tracker miners 2.1.6, while GNOME
3.34 will ship versions 2.3.0 of both.
Main changes since archive version, in tracker:
- Support for storing Musicbrainz metadata in the multimedia ontology.
- Fix detection of files that need writeb
Reproducer is as follows:
lxc launch ubuntu:bionic zfs-bug-test
Creating zfs-bug-test
Starting zfs-bug-test
lxc delete zfs-bug-test --force
Error: Failed to destroy ZFS filesystem:
Can reproduce this on Eoan with latest 5.2, 5.3 kernel.
** Also affects: linux (Ubuntu Eoan)
Importance: Medium
Yeah, this GetDynamicUsers denial is probably unrelated and should/will
be addressed in another bug. Thanks for double checking the alias trick!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.
I can confirm that the following commands fixes the problem so Ubound
can start again:
echo 'alias / -> /upper/,' >> /etc/apparmor.d/tunables/alias
apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.unbound
I noticed that when it starts, another AppArmor-related error message is
logged:
[ 257.
To be clear: point(3) above is what I see happening most of the time at
the moment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1779156
Title:
lxc 'delete' fails to destroy
*** This bug is a duplicate of bug 1841318 ***
https://bugs.launchpad.net/bugs/1841318
I fumbled around and got it fixed.
On Tue, Aug 27, 2019 at 8:45 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> *** This bug is a duplicate of bug 1841318 ***
> https://bugs.launchpad.net/
Hi,
I hit this issue on Bionic, Disco and Eoan. Our (server-team) Jenkins
nodes are often filled by stale LXD containers which are left there
because of "fails to destroy ZFS filesystem" errors.
Some thoughts and qualitative observations:
0. This is not a corner case, I see the problem all the t
** Tags added: id-5d67fe691c14484db556d212
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6 MTU
Status in cloud-init p
** Changed in: systemd (Ubuntu Eoan)
Assignee: Dan Streetman (ddstreet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1814373
Title:
storage / luks /
** Tags removed: i386
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/938751
Title:
Images are washed out or colors are skewed in some apps
Status in Eye of GNOME:
New
St
When I say bind, I actually meant to bind the outgoing connection from
Pidgin (not related to Avahi). So when creating the socket, specify the
source IP address.
The problem is that when you connect (without specifying a source) then
at least for IPv6 due to the routing table specification of the
Do we have any hunches on how to reproduce this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1779156
Title:
lxc 'delete' fails to destroy ZFS filesystem 'dataset is b
Cosmic is now end-of-life. Does this still occur on Disco?
** Changed in: linux (Ubuntu)
Importance: High => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
27 matches
Mail list logo
