now migrated
** Changed in: python-defaults (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1860647
Title:
block migra
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libx11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net
Came across this issue on a system I'm rebuilding and spun up a VM
running 18.04.3 to test. It seems like I got it working consistently on
every reboot. I'll try and breakdown what I've tried and what worked.
Everyone & Dev's can let me know if they see any issues of setting it up
the way it's work
** Tags added: eoan
--
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/1765477
Title:
5s delay in dns resolving; artful and earlier is quick
Status in systemd package in
All autopkgtests for the newly accepted pam (1.3.1-5ubuntu1.19.10.1) for eoan
have finished running.
The following regressions have been reported in tests triggered by the package:
openssh/1:8.0p1-6build1 (ppc64el, amd64, s390x, armhf, i386, arm64)
kscreenlocker/unknown (armhf)
Please visit the
I'm seeing this in eoan, too.
Whenever I try to access a host in my lan, host resolution takes 15s
(tried timing "ping -c 1" and "nslookup"
a "dig " query is immediate, but a "dig " also takes
15s.
It seems it's trying 3 times, each with a 5s timeout before failing.
--
You received this b
All autopkgtests for the newly accepted bluez (5.50-0ubuntu5) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
network-manager/1.20.4-2ubuntu2 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceed
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020, (i.e.
yesterday).
You will need to install or upgrade to a supported release of Ubuntu. If
you then find that the problem is still present kindly upload the
debugging logs by running only onc
YEAH!!!
Finally Fixed!!! I just tested the bluez proposed update and my
headphones connected in A2DP mode the first time (without having to go
through all the tricks of connecting/disconnecting bluetooth, etc, etc).
I did try powering off and on my headphones several times and it
continues to wor
It affects disco. Was a fix released?
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1583801
Title:
No sound via headphones (headset) when Ubuntu
All autopkgtests for the newly accepted openssh (1:8.0p1-6ubuntu0.1) for eoan
have finished running.
The following regressions have been reported in tests triggered by the package:
libnet-scp-perl/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceedi
My machine did not reboot successfully; because I followed The Guide, my
system has a root password, and I was prompted for it at the systemd
emergency shell. (Which is super-confusing, because I forgot I had set a
password.)
The error message appeared to be along the lines of "bpool failed to
imp
Public bug reported:
Hello, after upgrading to focal I found the following in my journalctl
output:
Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open
/etc/securetty: No such file or directory
Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open
/etc/
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1860826
Title:
pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
directory
Status i
All autopkgtests for the newly accepted poppler (0.80.0-0ubuntu1.1) for eoan
have finished running.
The following regressions have been reported in tests triggered by the package:
kopanocore/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding aft
OK I see now. I mistook Ubuntu 19.04 as the next LTS after 18.04. So my choices
will be:
1. Clean install of 18.04LTS
2. Upgrade to 19.10
3. Upgrade to 20.04 daily (after upgrade to 19.10)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
** Changed in: mawk (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1159933
Title:
mawk %d maxes out at 0x7FFF instead of 0xFF
Hmm... I can't duplicate this on Debian testing, which is using a newer
version of e2fsprogs (1.45.5-2). The e2scrub_reap.service file is
identical with Ubuntu's 1.45.3-4ubuntu2.1, though. And looking at the
service file, I have no idea why systemctl would be trying to paskk for
a password, given
I can no longer reproduce it either. *shrug*
P.S. Hi Ted long time no see.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1860676
Title:
apt-get dist-upgrade -y hangs d
[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unatt
** Changed in: mawk (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1074404
Title:
Segfault with mawk
Status in mawk package in Ubunt
** Changed in: mawk (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1332114
Title:
Please update mawk to latest upstream release
Stat
** Changed in: mawk (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/490736
Title:
mawk 1.3.3-17ubuntu2 incorrectly handles "/" in "[ ]
Found a fix
https://www.andreagrandi.it/2013/06/22/how-to-make-subwoofer-work-in-
ubuntu/
thank me later :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1553685
Tit
Another result. When I tried the v18.04.3 system preview from the USB
FD, the background was "normal". I just finished installing the system,
and the background now has the transparent red raster overlay. I could
get to "Settings" though without locking up the system, so there was at
least a ma
101 - 125 of 125 matches
Mail list logo
