Is this going to be fixed in disco?
--
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/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in NetworkManager:
Fix
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
"My biggest concern--ibus-libpinyin, also is working OK!"
"ibus-libpinyin" should be --ibus-pinyin--.
On Fri, May 31, 2019 at 2:10 PM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:
> Call for testing
>
>
> I hope for help by both Ping-Wu (the bug reporter) and other
At the first run, things are looking good. My biggest
concern--ibus-libpinyin, also is working OK!
On Fri, May 31, 2019 at 2:10 PM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:
> Call for testing
>
>
> I hope for help by both Ping-Wu (the bug reporter) and other
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
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/1831301
Title:
sound doesn't works in both kernel. no one
Public bug reported:
.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Sat Jun 1 04:26:10 2019
The error in your log is:
/build/cdebconf-Lc5sq3/cdebconf-0.198ubuntu1/src/debconf.c:241 (main):
Cannot initialize debconf frontend
cdebconf is not the default implementation of debconf in Ubuntu (debconf
is). Furthermore, your logs show that you have cdebconf-udeb installed,
which is not
** Summary changed:
- security.capability extended attributes not restored upon extraction
+ only user.* extended attributes restored upon extraction
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
Call for testing
I hope for help by both Ping-Wu (the bug reporter) and other Chinese
users to test the proposed upgrade of the ibus-libpinyin package in
Ubuntu 18.04. I have subscribed the Ubuntu CJK Testers team to this bug
report to reach out to more possible testers.
I have done these tests:
bionic
--
Installed from bionic-proposed these packages:
* ibus-libpinyin 1.11.0-1ubuntu0.18.04.1
* libpinyin-data 2.2.2-1~ubuntu18.04.1
* libpinyin13 2.2.2-1~ubuntu18.04.1
Used the Intelligent Pinyin method for inputting some Chinese
characters. Didn't observe any
Public bug reported:
idk more about this bug , but can you fix it
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture:
And another interesting information :
If I use a live-cd (USB disk) with 19.04 to open a session : the problem is the
same
If I use a live-cd (USB-disk) with 18.04 to open a session : the computer stop
normally at the end when I remove the USB-disk and press Return !
So, it looks really to be
** Changed in: systemd (Debian)
Status: Unknown => New
--
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 / dmsetup regressed (or got
Never !
I had the computer since 2011 I think, and I used all the releases since this
time, upgrade or fresh install.
I don't remember having this problem...
(Maybe a different problem : this last days, sometimes, Ubuntu suddenly close
and start again...)
--
You received this bug notification
Public bug reported:
Since https://github.com/systemd/systemd/pull/12430 was merged and
libsecomp was updated the test has been failing on Ubuntu CI:
https://github.com/systemd/systemd/issues/12709. By analogy with
Public bug reported:
The output of the apport reports the same error every time the system
starts, thus generating redundancy.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "61850716_881374908870302_7334842906412318720_o.jpg"
** Also affects: base-files (Ubuntu Eoan)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1829968
Title:
motd [on at least
** Changed in: systemd (Ubuntu Cosmic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Bionic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Cosmic)
Status: In Progress => Incomplete
** Changed in: systemd
** Tags added: sts
--
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/1796501
Title:
systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
Status in systemd
** Changed in: tar (Debian)
Status: Unknown => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1554715
Title:
rmt and rmt-tar should not be autoinstalled
> * add-apt-repository should support logging in to launchpad and adding
private ppas
added this functionality.
> * private PPAs should be added with auth.conf.d for the auth data
added this functionality.
still does not remove this auth data when the corresponding sources.list
entry is
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1825378
Title:
systemd-networkd doesn't set wireguard
** Tags added: sts
** Changed in: cups (Ubuntu Disco)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
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/1747765
** Tags removed: rls-dd-incoming
** Tags added: rls-ee-incoming
--
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/1756595
Title:
disk space info inadvertently provides all
** Changed in: systemd (Ubuntu Xenial)
Status: Triaged => In Progress
--
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/1828892
Title:
systemctl - alias service
** Also affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1831232
Title:
Ubuntu 18.04 won't boot - failed to
disco-proposed fixed it for me as well:
- Clean disco installation.
- Create .netdev file.
- reboot
--> Endpoint is not set.
- Update systemd from disco-proposed.
- reboot
--> Endpoint is set.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Tested with disco-proposed and confirmed this issue has been resolved.
# apt list systemd
Listing... Done
systemd/disco-proposed,now 240-6ubuntu5.1 amd64 [installed]
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification
Public bug reported:
On Kubuntu 18.04.2 LTS, with network-manager 1.10.14-0ubuntu2, DNS
servers in "Other DNS Servers" are ignored unless a Search Domain is
also specified. This difference can be seen in the output of `systemd-
resolve --status`.
For my use case, I need to specify an additional
Public bug reported:
$ lxc launch ubuntu-daily:eoan devel1
$ sleep 10 # wait for boot
$ lxc exec devel1 /bin/bash
root@devel1:~# cat /proc/uptime
183.00 173.00
root@devel1:~# cat /etc/cloud/build.info
build_name: server
serial: 20190531
root@devel1:~# lsb_release -sc
eoan
root@devel1
Quite a pleasent surprise I found today.
$ lxc launch ubuntu-daily:devel devel1
$ sleep 20
$ lxc exec devel1 systemctl status | grep State
State: running
$ lxc exec devel1 -- sh -c 'cat /etc/cloud/build.info; lsb_release -sc'
build_name: server
serial: 20190531
eoan
$ lxc exec devel1
Public bug reported:
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the
kernel. on a kernel level this works just fine and the system reboots
immediately ...
when in the initramfs during boot and a panic
targeting to xenial and bionic since we need this SRUed for Ubuntu Core
installs.
** Description changed:
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the
- kernel. on a kernel level this works just fine
** Tags added: rls-ee-incoming
--
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/1831252
Title:
panic=-1 is completely ignored by the initrd causing unexpected
Thank you for the explanation Till.
I believe the lack of previous complaints is because this happens in a
pretty unique conditions (very high MaxJobs and large batches of jobs).
The test case however was based on a real-life scenario reported to me.
--
You received this bug notification
Hello Dan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.22 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dimitri, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.22 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
systemd accepted to bionic/cosmic-proposed, please test
** Tags removed: verification-failed verification-failed-bionic
** Tags added: verification-needed verification-needed-bionic
verification-needed-cosmic
** Changed in: systemd (Ubuntu Cosmic)
Status: In Progress => Fix Committed
**
Hello Dan, or anyone else affected,
Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ko-Zu, 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.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dimitri, 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.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dimitri, or anyone else affected,
Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, 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.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, or anyone else affected,
Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This could be argued as Won't Fix since trusty is out of standard
support, but it did, in the end, receive an upgrade in trusty esm, so
marking Fix Released.
** Changed in: libseccomp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
This was fixed in upstream 2.3.2 which was fixed in cosmic. As of
https://usn.ubuntu.com/4001-1/ pulling back 2.4.1, this is now fixed
everywhere.
** Changed in: libseccomp (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
libseccomp was updated in trusty ESM here:
https://usn.ubuntu.com/4001-2/
--
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/1586496
Title:
Upgrade libseccomp library in
I have raised the default LogDebugHistory some years ago as most
printing problems happen during the execution of a job and this way one
gets a logging with debug verbosity only for jobs and standard verbosity
for all the rest. This way one often did not need to ask the bug-
reporting users to
Hello Dimitri, or anyone else affected,
Accepted openssl into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openssl/1.1.1b-
1ubuntu2.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags removed: need-duplicate-check
--
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/1831221
Title:
do-release-upgrade fails due to package libpam0g:amd64
Public bug reported:
While performing a release upgrade from 14.04 to 16.04, the do-release-
upgrade process crashes, apparently due to a failure installing or
upgrading the package libpam0g:amd64 1.1.8-3.2ubuntu2.1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam0g:amd64
Public bug reported:
ubuntu 16.04
GF106GL
$ sudo ubuntu-drivers autoinstall
nvidia-384
$ sudo ubuntu-bug xorg
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu
I have set this up in Xenial/Bionic/Eoan
The following syncs nicely a dir created as root to need the sudo to read it:
$ rsync -AEaogt --rsync-path="sudo rsync" -e "ssh -o
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" /tmp/foo
ubuntu@10.253.194.115:/tmp
This works among all pairs and
Ok, so not having full context as some of the discussion was happening
on IRC (and no mention of it was left on the bug here + the package was
not rejected from the queue), I have possibly prematurely accepted the
libnet-ssleay-perl SRU. After getting logs from Rik I see there's still
no consensus
In a recent test with MaxJobs of 4 I was easily able to reach over
65 GB of memory consumption within 60 mins, while with LogDebugHistory
set to 0 the consumption was below 400 MB.
My recommendation is to lower the default LogDebugHistory value back to
what is upstream: 200.
--
You received
Solved on 18.04.2
** Changed in: software-properties (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/930972
Title:
Solved on 18.04.2
** Changed in: apport (Ubuntu)
Status: New => Fix Released
--
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/785447
Title:
Connection to error
Solved on 18.04.2 with gnome-shell.
** Changed in: d-conf (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to d-conf in Ubuntu.
https://bugs.launchpad.net/bugs/775502
Title:
** Tags added: rls-ee-incoming
--
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/1831021
Title:
Extremely high memory consumption under heavy workload
Status in cups package
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Hello Dimitri, or anyone else affected,
Accepted libnet-ssleay-perl into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnet-
ssleay-perl/1.84-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this
Ok, I see it's simply missing another SRU that's already in the queue.
Looking at it since it's needed to unblock everything.
** Changed in: libnet-ssleay-perl (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags removed: verification-failed-bionic
** Tags added:
The libio-socket-ssl-perl SRU seems to have broken dependencies, causing
build failures for other SRUs (ibus-libpinyin) and image builds.
libio-socket-ssl-perl : Depends: libnet-ssleay-perl (>= 1.84-1ubuntu0.1)
but it is not going to be installed
I'm actually considering removing the SRU from
** Description changed:
+ [Impact]
+
+ * Just as of yesterday we have a new libseccomp in all releases.
+This brings some new code and features which might impact packages.
+For qemu being one of the few that is not so much a problem in many
+cases. Prior to Disco we didn't have
69 matches
Mail list logo
