Happens to me as well after upgrade from 19.04 to 19.10
--
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/1850887
Title:
Audio / Sound reverts to HDMI when power event occ
#34 said:
This bug affects a cryptographic (read: highly sensitive) feature, is 15 months
old, a patch was proposed 12 months ago, but it is still of "Undecided"
importance and still "Unassigned"? Come on! Are the ecryptfs-utils and systemd
packages unmaintained at Ubuntu?
Well, this bug is now
Hi csozo,
It looks like your system was under some form of memory pressure prior
to the openssh installation. So I don't think this is a fault
necessarily in openssh itself but rather due to your computer having run
out of memory and gotten into some sort of inconsistent state.
I would recommend
** Description changed:
I don't know.
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: openssh-server 1:8.0p1-6build1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
Date
This bug was fixed in the package klibc - 2.0.7-1ubuntu4
---
klibc (2.0.7-1ubuntu4) focal; urgency=medium
* Fix losetup, by switching to kernel uapi header, instead of buggy
klibc one. LP: #1850184
-- Dimitri John Ledkov Thu, 07 Nov 2019 01:08:13
+
** Changed in: klibc
This is due to the new googletest 1.9 git snapshot in focal-proposed,
which is (at least part way) through a big set of deprecations.
If this needs to be pushed through urgently, we could evict googletest
from focal-proposed, do the nettle transition, and then let googletest
back in.
I'll also ke
flock will not block inotify or udev events being emitted.
See
https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L322
https://github.com/systemd/systemd/blob/master/src/udev/udevd.c#L409
it will prevent udevd from running the rules against it. Thus
effectively the event will be fire
** Changed in: apport (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1851542
Title:
autopkgtest fails due to aspell SRU
S
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.12
---
unattended-upgrades (1.1ubuntu1.18.04.12) bionic; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
(LP: #18230
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.4
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.4) xenial; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.2
---
unattended-upgrades (1.10ubuntu5.2) disco; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
(LP: #1823070)
* Defau
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.4
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.4) xenial; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.12
---
unattended-upgrades (1.1ubuntu1.18.04.12) bionic; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
(LP: #18230
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.12
---
unattended-upgrades (1.1ubuntu1.18.04.12) bionic; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
(LP: #18230
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.2
---
unattended-upgrades (1.10ubuntu5.2) disco; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
(LP: #1823070)
* Defau
The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.4
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.4) xenial; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
This bug was fixed in the package unattended-upgrades - 1.10ubuntu5.2
---
unattended-upgrades (1.10ubuntu5.2) disco; urgency=medium
* Report packages kept back by origin (LP: #1821376)
* Store list of kept packages and report the number of them in motd
(LP: #1823070)
* Defau
The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Tags removed: block-proposed-bionic block-proposed-disco block-
proposed-eoan block-proposed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1848354
Tit
This bug was fixed in the package unattended-upgrades - 1.14ubuntu1.1
---
unattended-upgrades (1.14ubuntu1.1) eoan; urgency=medium
* debian/tests/control: Mark upgrade-between-snapshots as flaky
(Closes: #941752) (LP: #1848354)
-- Balint Reczey Wed, 16 Oct 2019 17:47:42 +020
"1 updates"? Having an "s" for 1 update is incorrect.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1823070
Title:
unattended-upgrades should tell the user (v
** Description changed:
Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier
subminor upstream releases (LP: #1822993).
SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the
3.6.9 release.
python3-stdlib-extensions also updates the modules to the 3.6.
So this is actually happening now every time I lock my computer, no
power change whatsoever (no standby, no suspend to RAM, no power
off/reboot). So this is now becoming very frustrating to work with as I
have to change my default audio device every time I use my computer now
so that my volume cont
Re-opening the ibus task for now.
@Johny: This is a very old bug report, and a lot has been changed since
it was originally filed. Any chance you can provide some details about
how to reproduce the bug on 19.10?
** Changed in: ibus (Ubuntu)
Status: Invalid => New
** Tags removed: lucid
-
** Branch linked: lp:~ubuntu-core-dev/ubuntu/eoan/apport/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1851542
Title:
autopkgtest fails due to aspell SRU
Status in
** Description changed:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an
aspell SRU.
+
+ ==
+ FAIL: test_install_packages_versioned (__main__.T)
+ install_packages() with versions and with cac
Stable Release Team,
I investigated the autopkgtest regression in Comment #12, and believe
it to not be a regression introduced by this gdb upload. apport has
been updated a couple of times via security since tests passed - and at
least one of those updates had known regressions. There is also a
f
Public bug reported:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an aspell
SRU.
[Test Case]
## From within autopkgtest source package, with autopkgtest deps installed
## This is a slightly modified version if debian/tests/upstream-system
# do not run in the sou
** Description changed:
Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier
subminor upstream releases (LP: #1822993).
SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the
3.6.9 release.
python3-stdlib-extensions also updates the modules to the 3.6.
This bug is now on Ubuntu 19.10 with openjdk-11...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/540751
Title:
Unable to use dead keys with java and ibus
Status in ibus pac
A couple of comments on the suggested path:
> Imho the sequency of commands should be:
> * take flock on the device, to neutralise udev
+1 on this approach. Do you know if the flock will block
systemd's inotify write watch on the block device which triggers
udevd? This is the typical race we se
@ Cloud init team, do we want to try changing cloud-utils to use a lock?
And like have a canary "only use locked codepath on this region" such
that we can assert through testing that this no longer happens with new
code, but does with old code.
--
You received this bug notification because you a
The same bug!
** Also affects: pulseaudio
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => datch (s-ogorodnick)
** No longer affects: pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
As noted in the last comment I posted on this, I have managed to get the
printer to work OK.
Would it be possible to simplify/clarify somewhere what the different
connections made by printers such as this are and mean? That is, when
you plug this printer in, you get several 'printers' showing up i
I have found a working combination of printer driver (from Epson) and
printer definition (one plugged in it shows up about three times as
different versions of the same XP-960), so this is not a 'bug'. Though I
have to say that it's not immediately obviouw what is going on!
--
You received this b
Public bug reported:
I've been googling this issue for 10's of hours and tried many things.
Relase of Ubuntu: 19.10
Expected outcome: Music plays on the internal speakers and headphones.
Actual outcome: I can barely hear audio using headphones with volume
turned up to 150%. Absolutely nothing
Only fails on arm64 now (all others good):
15-basic-resolver.c:58:46: error: ‘__NR_open’ undeclared (first use in this
function)
58 | if (seccomp_syscall_resolve_name("open") != __NR_open)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
** Description changed:
Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier
subminor upstream releases (LP: #1822993).
SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the
3.6.9 release.
python3-stdlib-extensions also updates the modules to the 3.6.
Offline build worked much better with these, but I still see some arches
fail (see PPA)
PPA: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1849785
-libseccomp-ftbfs/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
# ls -l /usr/share/apport/symptoms/ubuntu-release-upgrader.py
-rw-r--r-- 1 root root 214 May 17 16:32
/usr/share/apport/symptoms/ubuntu-release-upgrader.py
# dpkg -S /usr/share/apport/symptoms/ubuntu-release-upgrader.py
apport-symptoms: /usr/share/apport/symptoms/ubuntu-release-upgrader.py
# deb
Well the answer to the new fails is that we are now "too new" in my
tests I used kernel 5.3 and this is what Focal has. But the final fix
used 5.4-rc levels which brought in all the time64 things.
linux-libc-dev:amd64 5.3.0-21.22
5.3 already has the NR definitions like
/usr/include/x86_64-li
+source:
https://git.launchpad.net/ubuntu/+source/cryptsetup/tree/debian/initramfs/hooks/cryptroot?id=applied/2%252.1.0-6#n414
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.n
Please, any new findings/new info? It is very annoying! :/ and got
worse. I must go to TTY1 and `killall light-locker` in order to be able
to use computer again...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubu
PS: turning the computer off performs normally, there is no delay any
more
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1830408
Title:
[nouveau][XFCE] Do not see login s
** Also affects: cryptsetup
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1851504
Title:
encrypted root fails to crypt
WORKAROUND: Change line 429 to read:
# libargon2 uses pthread_cancel
LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')"
find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so;
do
copy_exec "$so"
do
Public bug reported:
There is a subtle error message during update-initramfs:
find: '': No such file or directory
I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line
430:
# libargon2 uses pthread_cancel
LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/lib.*)/
I have tried quickly to just backport [1] but it still fails in a full cross
arch PPA build
OTOH adding those worked in the sbuild env when modifying things manually.
There must be more to it.
[1]:
https://github.com/seccomp/libseccomp/commit/be65b26b67099be2b2b4890d736dbd1ad15adf36
--
You rece
Oh it now became a real build issue (not on unit tests) by breaking very early
with things like:
arch-x86_64-syscalls.c:63:27: error: ‘__PNR_clock_getres_time64’ undeclared
here (not in a function)
63 | { "clock_getres_time64", __PNR_clock_getres_time64 },
--
You received this bug notificat
Joe, thanks for reporting the bug.
I am unable to reproduce the issue in my test env.
Can you please provide a step-by-step procedure to reproduce it on a
clean 18.04 installation?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libseccomp/+git/libseccomp/+merge/375205
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/18
Unsure the system has enough information from the hardware to tell
appart a disconnect from a power off, there is no mechanical check that
something is plugged in the port, it's just depending on whether a
signal is received. That said it looks like a duplicate of #1847570
--
You received this bu
What about
-ls -l /usr/share/apport/symptoms/ubuntu-release-upgrader.py
-dpkg -S /usr/share/apport/symptoms/ubuntu-release-upgrader.py
-debsums apport-symptoms
The file should be there...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Summary changed:
- apt-add-repository always returns "user or team does not exist." for ppa repos
+ apt-add-repository returns "user or team does not exist." when erroring out
due to proxy auth needed
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Low
--
You receive
seems a disk issue rather than an xorg bug
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubunt
Dimitri, indeed, my bad.
In other news: it seems that this issue has been known for a while and somebody
has been (trying to) solv(e|ing) it - I guess the solution will come to Ubuntu
at some stage...
https://github.com/systemd/systemd/pull/12004
Thanks for the feedback, looking forward to a wo
Ignore the above about 3.10. I tried to compile without optimization.
That's why I didn't notice the problem. So 3.10 is also affected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad
I have the same protobuf problem with my personal code.
Generated by protobuf code is definitely not compatible with currently
installed system headers.
I also tested protobuf-3.10 and it works fine. So I think the protobuf package
has to be upgraded in the Ubuntu repo.
--
You received this bu
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Chris Halse Rogers (raof)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1851453
Title:
mir FTBFS in focal, blocks n
Code is on https://github.com/seccomp/libseccomp/tree/release-2.4 now.
But an official release would need 2.4.2 to be tagged by upstream.
But now fixes can be cherry-picked to fix the FTBFS in E+F
** Tags added: server-next
--
You received this bug notification because you are a member of Ubunt
62 matches
Mail list logo
