I see it is queued here:
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=
--
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/1556439
Title:
pulseaudio
Please don't upload anything for bionic till this is done:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/comments/32
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
OK, let us skip the cosmic, I will upload a debdiff for bionic.
Thanks.
--
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/1834138
Title:
PA: Don't restore the streams to
>> FWIW, I think not booting a 19.04 ISO is probably fine,
Unless like me, you have just upgraded your hardware to a Ryzen 3600x
and find you have to downgrade from the version you are using on your
old machine to use the new machine you just purchased.
--
You received this bug notification
I can't see the SRU anywhere yet...?
--
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/1556439
Title:
pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
Upgraded from Ubuntu server 16 to 18 and I too am having this issue.
--
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/1718658
Title:
ecryptfs-mount-private fails to
I've confirmed, that #9 is is not reproducible with systemd from Debian.
The runs from there with our without DNSSEC=yes are the same. They
differ on Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Same thing on bionic now.
a) SSL with incorrect name fails as expected:
ubuntu@bionic-ldap-start-tls-1835181:~$ sudo truncate -s 0 /var/log/syslog
ubuntu@bionic-ldap-start-tls-1835181:~$ ldapwhoami -x -H
ldaps://bionic-ldap-start-tls-1835181.lxd
ldap_sasl_bind(SIMPLE): Can't contact LDAP
I didn't have TLS_REQCERT set in /etc/ldap/ldap.conf during these tests,
but the manpage says the value "demand" (equal to "hard") is the default
in eoan at least.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in
It seems to be working fine in eoan. I setup a CA and issued a server
certificate, and setup openldap with ssl/start_tls.
The hostname of the container:
ubuntu@eoan-ldap-start-tls-1835181:~$ hostname -f
eoan-ldap-start-tls-1835181.lxd
ubuntu@eoan-ldap-start-tls-1835181:~$ ping -c 1 $(hostname
Thank you for your bug report, could you add your 'journalctl -b 0' log
after a boot having the issue?
Could you also try if downgrading to the debs from
https://bugs.launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.8/+build/16742546
makes the issue got away?
--
You received this bug
Public bug reported:
My computer has got very slow since 4 or 5 weeks. Finally, I checked
resource usage with and the culprit seems to be cupsd. Here is an
output line from a few minutes after boot:
30900 root 20 0 305452 287396 5768 S 5,3 9,3 0:41.34
cupsd
Then after an hour
In my case, Ubuntu 18.04 running on AWS, the problem was as follows:
1. /etc/fstab had 0 in the 6th (passno) field. I presume this is the default
that AWS places there, or maybe this is determined by the Ubuntu template on
AWS.
2. According to a comment that I found on Stack Overflow, this is
** Branch linked: lp:~ubuntu-core-dev/ubuntu/eoan/apport/ubuntu
** Branch linked: lp:apport
--
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/1830858
Title:
TOCTOU
I think a change in Ubuntu broke ClutterGstCamera.
I don't use io.elementary.camera but have my own program that also uses
ClutterGstCamera. Up until about a month ago it was working fine on
18.04. Now it gives the same error:
Clutter-Gst-CRITICAL **: Unable to setup device without element
** Changed in: systemd (Ubuntu)
Status: Expired => Confirmed
--
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/1797282
Title:
fsck not running at all on reboot
Public bug reported:
Running the following perf collect inside a running docker could
potentially crash:
$ perf record -F 100 -ag -o /tmp/perf-100Hz-10s -- sleep 10
The dump is caused by SIGSEGV for de-referencing nullptr in
nsinfo__copy() in at namespaces.c:144
$ lldb -c
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834494
Title:
latest bzip2 reports crc errors incorrectly
Status in bzip2:
New
Status in
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834494
Title:
latest bzip2 reports crc errors incorrectly
Status in bzip2:
New
Status in
Public bug reported:
Linking with libosmesa6-dev version 19.0.2 will fail because all the gl*
symbols are missing:
```
[100%] Linking CXX executable bin/minko-converter
../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o):
In function `jas_stream_tmpfile':
I've uploaded a backport for the NTLMv2 support to Bionic now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1817537
Title:
libsoup should support ntlmv2
Status in
** Description changed:
+ * Impact
+ Without NTLMv2 support evolution-ews can't connect to some exchange servers
+
+ * Test case
+ Try connecting from evolution-ews to an exchange server which enforces NTLMV2
+
+ * Regression potential
+ The change adds extra cases in the ntlm handling support,
I tested 240-6ubuntu5.2, it fixes the issue on Ubuntu 19.04
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
All autopkgtests for the newly accepted systemd (240-6ubuntu5.2) for disco have
finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco
--
Thanks, I've sponsored the Bionic SRU now
--
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/1556439
Title:
pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref()
Thanks for the new debdiff but I don't think it makes sense to do a
Cosmic SRU at this point since it's a deprecated serie
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
@Anton
Thanks. However, is that safe to do, i.e. it won't compromise security,
will it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1782263
Title:
Can you find out how it was inverted for x, y and z?
--
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/1821641
Title:
[HP Elitebook 840 G1] Screen is upside down on 19.04
Thanks, I will get it tested soon
--
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/1835809
Title:
AMD Ryzen 3000 series fails to boot
Status in systemd package in Ubuntu:
Is there any way to do it by CLI?
--
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/1835711
Title:
Ubuntu-bug collects bug data but does not upload it
Status in apport
I don't even have any option of this kind in my settings :/
** Attachment added: "Screenshot from 2019-07-09 16-11-29.png"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1835711/+attachment/5275879/+files/Screenshot%20from%202019-07-09%2016-11-29.png
--
You received this bug
The issue was fixed in Eoan with https://launchpad.net/ubuntu/+source
/software-properties/0.98.1
It doesn't make sense to SRU to Disco since livepatch is nor available
there
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Low
** Changed in: software-properties (Ubuntu)
This is still a UX bug, as thomas303 said, ubuntu-bug should still
inform the user of what happened and why.
--
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/1814611
Title:
The issue was fixed in Eoan with https://launchpad.net/ubuntu/+source
/software-properties/0.98.1
It doesn't make sense to SRU to Disco since livepatch is nor available
there
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: software-properties
Public bug reported:
* Impact
Sometime the livepatch status goes through an 'applying' intermediate value
which can confuse the UI which then reports an non existing error
* Test case
Enable livepatch, go to software-properties->livepatch, check that the status
matches the one reported by
Public bug reported:
* Impact
The livepatch UI design includes a control in software-properties which let you
enable the indicator or not, that UI element is currently missing from bionic
* Test case
- start software-properties
- go the livepatch tab and enable livepatch by adding an account
->
Note that the fix is committed to git for eoan, but not uploaded as
systemd currently fails its testsuite on eoan. This needs
investigation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Jeremy, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+
+ * Systems with AMD Ryzen 3000 series CPUs don't boot.
+
+ [Test Case]
+
+ * Boot with fixed systemd on an AMD Ryzen 3000 series system.
+
+ [Regression Potential]
+
+ * The fix itself is very small, it ignores known to be faulty random
+ values
To disable warning (and authentication) you can add:
[main]
auth-polkit=false
To the /etc/NetworkManager/NetworkManager.conf (if you already have
[main] section, just add value to it)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Disco)
Status:
Hi! This bug is still happening with the latest DisplayLInk Driver for Ubuntu
(5.2). The mouse flickers and moves around alone. It also dissapears on click.
I am using a DELL 7300 laptop and a Asus MB16AC display. As soon as I connect
the mponitor with the display link adapter uysing an USB a
Next time the problem happens, please check if you have a 'pulseaudio'
process running. If not then please follow these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
If you do however have a 'pulseaudio' process running (as yourself)
also before restart i need to run
pulseaudio -k
pulseaudio -D
and then restart computer
--
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/1833527
Title:
in gnome
Unfortunately it is a recurring bug, and yet again I have no sound
detected in gnome settings
@Daniel van Vugt
--
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/1833527
** Also affects: pulseaudio (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: pulseaudio (Ubuntu Eoan)
Importance: High
Status: Fix Released
** Also affects: pulseaudio (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: pulseaudio
** Also affects: pulseaudio (Ubuntu Eoan)
Importance: High
Status: Fix Released
** Also affects: pulseaudio (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: pulseaudio (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: pulseaudio
--- icl_commit_20190702.list_kernv_drm-tip 2019-07-02 13:55:00.666216695
+0800
+++ icl_commit_20190709.list_kernv_drm-tip 2019-07-09 13:40:15.070144631
+0800
@@ -1,13 +1,52 @@
+patches series of drm/i915: Random plane stuff,,,
+1/6 26443a4bc44 ADDED!,drm/i915: Add windowing for primary
48 matches
Mail list logo
