[Expired for openssl (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssl (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
** Tags added: eoan
--
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/1839589
Title:
pulseaudio FTBFS on eoan 12.2-2ubuntu4
Status in pulseaudio package in Ubuntu:
New
Was fixed by release 243~rc1-0ubuntu2 of systemd.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
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/1839292
** Description changed:
[Impact]
APT releases the locks in the same order it acquires them, rather than
reverse order. Given that we have no waiting for locks, this is not _super_
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock,
rather than lock-frontend.
** Description changed:
[Impact]
APT releases the locks in the same order it acquires them, rather than
reverse order. Given that we have no waiting for locks, this is not _super_
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock,
rather than lock-frontend.
** Description changed:
[Impact]
TLS sessions can renegotiate keys, but APT does not support it; meaning their
HTTPS connections stop working.
[Test case]
- ...
+ We don't really have a reproducer. You'd need a server that re-negotiates by
path; e.g. because it requires a a certain
Public bug reported:
pulseaudio fails to build from source on Eoan
I was attempting to put together a patchset for LP#1839580, but it
appears as if the packages are currently failing to build from source.
Not sure how they built the first time around.
Here's my ppa's buildlog, for a source
Confirmed, it's a test failure:
FAIL: cpu-volume-test
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
** Summary changed:
- pulseaudio FTBFS on eoan 12.2-2ubuntu4
+ pulseaudio FTBFS on eoan 12.2-2ubuntu4: FAIL: cpu-volume-test
** Summary changed:
- pulseaudio FTBFS on
Maybe this is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916504 ?
** Bug watch added: Debian Bug tracker #916504
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916504
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Uploaded apt 1.8.3 to disco (this is a sync (*) from Debian unstable,
and also includes some other bug fixes from 1.8.2 which I forgot to sync
earlier)
(*) uploaded with --no-lp so we get a diff for sru-review
** Description changed:
[Impact]
Currently CONNECT requests use the name of
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1839586
Title:
package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency
Public bug reported:
error at the start of the pc
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
AptOrdering:
cups-filters:amd64:
/var/log/syslog seems to contain debug information of network-manager, although
I was not successful:
With this command:
sudo /usr/lib/NetworkManager/debug-helper.py --nm debug
I followed these instructions:
https://wiki.ubuntu.com/DebuggingNetworkManager#Getting_NetworkManager_debug_logs
@Hui Wang
Thanks, here is my new alsa-info.txt. Unfortunately, my internal mic
still doesn't work.
** Attachment added: "alsa-info.txt.69pNmVM83Q"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5281774/+files/alsa-info.txt.69pNmVM83Q
--
You received this bug
You say "But I'm getting tired of this after years of doing it.". Does
this mean that you are suffering this bug already with older versions of
Ubuntu?
Yes, that is correct. It is happening for 2 years now, if I'm not
mistaken.
--
You received this bug notification because you are a member of
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1834192
Title:
apparmor mult_mount
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Tags removed: wily
** Tags added: xenial
--
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/1577654
Title:
PCI/internal sound card not detected E7470
Status in
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Tags added: sru-20190722 ubuntu-qrt-apparmor
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1834192
Title:
apparmor mult_mount regression test
Public bug reported:
This is constant struggle for me, it seems that in the initial days
after installation of Ubuntu 19.10 this problem of Wifi stopping to work
after wake up does not happen. I'm sure, I reinstalled Ubuntu many
times, the issue still persist.
Breaking of Wifi after computer
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Description changed:
This is constant struggle for me, it seems that in the initial days
after installation of Ubuntu 19.10 this problem of Wifi stopping to work
after wake up does not happen. I'm sure, I reinstalled Ubuntu many
times, the issue still persist.
-
- Breaking of Wifi
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Tags removed: wily
--
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/1533343
Title:
No sound from internal speakers after boot with connected headphones
Status in
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Please have a look at
https://wiki.ubuntu.com/DebuggingNetworkManager
and supply us with debug logs of NetworkManager and wpasupplicant,
You say "But I'm getting tired of this after years of doing it.". Does
this mean that you are suffering this bug already with older versions of
Ubuntu?
**
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
** Tags removed: wily
--
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/1523100
Title:
Alsa not detecting internal microphone [ALC255] (Realtek)
Status in alsa-driver
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
*** This bug is a duplicate of bug 1794053 ***
https://bugs.launchpad.net/bugs/1794053
I fixed this in 1.7.0, but forgot about this bug and tracked it in bug
1794053, so marking this as a duplicate.
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Released
** This bug has been
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
This bug was fixed in the package procps - 2:3.3.15-2ubuntu3
---
procps (2:3.3.15-2ubuntu3) eoan; urgency=medium
* d/p/pgrep-increase-CMDSTRSIZE.patch:
- Allows long command lines to be searched.
eg: Java process with a long classpath. (LP: #1839329)
-- Eric Desrochers
Ok, change seems to be trivial enough to accept even without getting
this merged upstream (most important is that there was no disagreement
so far from the maintainers). I also don't expect anything to go bad
since the constant bump is not too big anyway.
** Changed in: procps (Ubuntu Disco)
Hello Pedro, or anyone else affected,
Accepted procps into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:3.3.12-3ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
After system update and reboot, system stay on the purple screen for
long time.Then after going to advanced mode and from recovery option, I
run check for broken packages. After completion system was restarted on
normal mode and found the display driver missing.
ProblemType:
Hello Pedro, or anyone else affected,
Accepted procps into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:3.3.15-2ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: openssh (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/201786
Title:
ssh Agent admitted failure to sign
[VERIFICATION DISCO]
I have installed the disco-proposed 'procps' package and was able to
conclude that it fixes the situation based on the reproducer suggested
upstream:
$ vi $(seq 1 1250| paste -s -d'_')_foo.txt # Creating a process containing >
4096 chars, to be precise 5158 chars)
$ pgrep
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openldap/+git/openldap/+merge/371148
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openldap/+git/openldap/+merge/371149
--
You received this bug notification because
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tcp-wrappers in Ubuntu.
https://bugs.launchpad.net/bugs/1839598
Title:
tcp_wrappers does not whitelisting of
Hello Federico,
Wietse is correct. You will not get security benefits from your proposed
changes.
Public key authentication, combined with a 2FA mechanism such as TOTP
for interactive users, is the current best practice.
IP filtering is a useful tool; you can already have good benefits from
** Description changed:
Impact
--
- Users willing to use the slapd rwm overlay will face a slapd segmentation
fault
- when trying to rewrite some rules. Backporting this fix will allow users using
- stable releases to take advantage of this feature without crashing slapd. This
- issue
[VERIFICATION BIONIC]
I have installed the bionic-proposed 'procps' package and was able to
conclude that it fixes the situation based on the reproducer suggested
upstream:
$ vi $(seq 1 1250| paste -s -d'_')_foo.txt # Creating a process containing >
4096 chars, to be precise 5158 chars)
$ pgrep
** Description changed:
+ Impact
+ --
+
+ Users willing to use the slapd rwm overlay will face a slapd segmentation
fault
+ when trying to rewrite some rules. Backporting this fix will allow users using
+ stable releases to take advantage of this feature without crashing slapd. This
+ issue
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openldap/+git/openldap/+merge/371147
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
67 matches
Mail list logo
