I have also tried to see if this issue arises on PopOS, which it does in
the versions after the last LTS. The current PopOS LTS does not have the
issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
** Tags added: update-excuse
--
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/1853852
Title:
hard to reproduce issues in systemd autopkgtest against new libseccomp
2.4.2
Public bug reported:
ubuntu server 18.04.3 LTS
systemd 237-3ubuntu10.31
wireguard 0.0.20191012-wg1~bionic from PPA.
We're using systemd-networkd to configure wireguard via wireguard.netdev
and wireguard.network files in /etc/systemd/network/. All endpoints have
IPv4 addresses.
When we include
** Changed in: snapd (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: initramfs-tools (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
** Changed in: snapd (Ubuntu Xenial)
Status: Invalid => Won't Fix
--
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/1771858
Title:
/snap/bin not in default PATH for
** No longer affects: python3-defaults (Ubuntu Eoan)
** No longer affects: python3-defaults (Ubuntu Disco)
** No longer affects: python3-defaults (Ubuntu Bionic)
** No longer affects: python3-defaults (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch
ubuntu@lp1796501-b:~$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
DNS=8.8.8.8
DNSSEC=yes
[DHCP]
UseDNS=no
ubuntu@lp1796501-b:~$ systemd-resolve --status ens3
Link 2 (ens3)
Current Scopes: DNS
LLMNR setting: yes
Same problem here. bluez 5.50, pulseaudio 13.0. Sony WH-1000XM3.
Fiddling with the buttons on the headset makes it show up as a HCI
device, after which it can be switched to A2DP.
@Daniel van Vugt: could you reopen this and reassign it to either bluez
or pulseaudio? At the very last it has
ubuntu@lp1850704-b:~$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
[Link]
MTUBytes=
ubuntu@lp1850704-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.33 amd64system and service manager
ubuntu@lp1850704-b:~$
root@lp1805183-b:~# dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.33 amd64system and service manager
root@lp1805183-b:~# journalctl -b -u systemd-resolved | grep Started
Nov 26 03:04:30 lp1805183-b systemd[1]: Started Network Name Resolution.
root@lp1805183-b:~# dhclient ens8
ubuntu@lp1850704-b:~$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
[Link]
MTUBytes=
ubuntu@lp1850704-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.33 amd64system and service manager
ubuntu@lp1850704-b:~$ ip
Public bug reported:
systemd-mount doesn't support lazyunmount / forceunmount
yet it should
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: core20
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Ever since the default changed to never blanking the screen, and after I
whined in comment #18 above, I have been running this in
/etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT=" consoleblank=300 "
always save a copy of grub first, and do "sudo update-grub afterwards",
then re-boot.
--
You
Installing 1:8.0-0ubuntu3.11 from xenial-proposed, the test plan and
James' addition for mediation is preserved across snapd restart all
works as expected. Marking as verification done.
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if
Installing 1:11.1-1ubuntu7.5 from bionic-proposed, the test plan and
James' addition for mediation is preserved across snapd restart all
works as expected. Marking as verification done.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug
For Ubuntu 20.04, resolvconf will not be allowed to manage
/etc/resolv.conf, this will always be managed via systemd-resolved. So
while you're right that this is a bug in the hook, it will not be a
priority to fix since the code will be rewritten and replaced.
> Alongside this, systemd's
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
** Attachment added: "user-1000.journal"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+attachment/5307828/+files/user-1000.journal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Attachment added: "system.journal"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+attachment/5307827/+files/system.journal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
I'm adding system.journal and user-1000.journal to this bug report.
Today (November 25th) at :
- 20:47 : I switched the headphones on... which didn't connect
- 20:48 : I tried to connect manually using UI (but the switch/toggle
immediately came back to "off")
- 20:49-50 : I used bluetoothctl,
Ubuntu Server 18.04.3 fresh install.
Ethernet Unmanaged in Network Manager.
SOLVED. FIXED, etc.
-
I created file /etc/netplan/01-network-manager-all.yaml
Within I entered:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
--
I edited
This bug was fixed in the package mesa - 19.2.4-1ubuntu1
---
mesa (19.2.4-1ubuntu1) focal; urgency=medium
* Merge from Debian.
* revert-set-full-thread-affinity.diff: Dropped, qemu is fixed now in
eoan and up. (LP: #1815889)
-- Timo Aaltonen Wed, 20 Nov 2019 20:17:00
Public bug reported:
I have a weird issue where an old app of mine which is written in
Eclipse RCP using SWT. It is an older Eclipse 3.x version.
I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works
fine.
When i start the app after compiling it using the latest Eclipse
Public bug reported:
When mistakenly used in the argument list it can expand to protected
content, such as /etc/shadow. Most users do not expect this.
The following example will permit 'username' to read /etc/shadow as the
* character accepts any character and spaces.
username ALL=(ALL)
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I tried all these suggestion, no joy.
Why won't dev fix? Please at least tell us what we're doing wrong. I may have
to install Desktop version because KVM/QEMU isn't playing nice with seeing the
network
Just verified that 2-sided portrait (long edge) printing does indeed
work on this printer in 19.04, so this is a regression. I'm not sure
which of the three drivers it's using. Let me know if you want me to
attach any files from 19.04.
--
You received this bug notification because you are a
Balint could you have a look this patch as a substiture for Dimitri?
Thanks!
--
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/1846787
Title:
systemd-logind leaves leftover
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.5 in a few hours, and then
in the -proposed repository.
Please help us by
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.13 in a few hours, and then in the
-proposed repository.
Please help us by testing
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Marking incomplete based on the fact that Robie has asked for additional
review.
** Changed in: systemd (Ubuntu Xenial)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Dell E310dw printer which worked well on 19.04 has problems in 19.10:
First, I went through the CUPS web interface to add the printer. The
interface gave me a choice of two entries with the same name plus one
with "driverless" added. I chose the first entry (not driverless)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Installation failed during upgradation
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxcb-present0:i386 1.11.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
Uname: Linux 3.13.0-96-generic x86_64
.tmp.unity_support_test.0:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1853880
Title:
package libxcb-present0:i386 1.11.1-1ubuntu1 failed to
If I log out the first user, the second user suddenly has sound.
And it didn't do this on Friday, when the same programs were running
before the user switch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
Yes, it seems to be a 'multiple users logged in' thing.
Use the sound in one user, then - at some seemingly random point that's
NOT while something is actually playing - discover that the sound system
is disabled. It's possible that both users have it not working, or one
to work and one not to.
Any chance fontconfig 2.13 could be backported to bionic? This is a
seriously annoying issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1832787
Title:
fontconfig
** Changed in: ubuntu-kernel-tests
Status: New => Triaged
--
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/1783881
Title:
ltp-syscalls: msgstress03 fails because
** Also affects: unattended-upgrades (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu Eoan)
Importance: Undecided
Status: New
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
** Information type changed from Public to Public Security
--
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/1853861
Title:
[SRU] Unattended-upgrades silently
** Description changed:
[Impact]
- * When autoremovable kernel packages are present on the system, there are
updates to apply and Unattended-Upgrade::MinimalSteps is set to "false", the
autoremovable kernel packages are not removed and the updates are not applied.
- * The root cause is
Ok, confirmed the patch debian/patches/test-expect-mmap-to-fail-in-
seccomp-test-on-s390-and-s390.patch has to be taken out to make it work
on s390x.
And most likely the same needs to happen for x86-32bit - there we don't have a
patch.
But this most likely also needs to be switched to no more
Public bug reported:
[Impact]
* When autoremovable kernel packages are present on the system, there are
updates to apply and Unattended-Upgrade::MinimalSteps is set to "false", the
autoremovable kernel packages are not removed and the updates are not applied.
* The root cause is u-u not
What is the output of:
sudo apt-get -f install
?
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
*** This bug is a duplicate of bug 500175 ***
https://bugs.launchpad.net/bugs/500175
** This bug has been marked a duplicate of bug 500175
Canceling an installation in Software Center crashes debconf with "Use of
uninitialized value $reply in scalar chomp at
Adding [1] might be worth in general - this is the patch for the arm
related discussion which seems applied upstream.
[1]:
https://github.com/systemd/systemd/commit/4df8fe8415eaf4abd5b93c3447452547c6ea9e5f
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks for the clarification.
On Mon, Nov 25, 2019 at 11:36 AM Sebastien Bacher
wrote:
> Looks like the xserver hit an error
> BUG: triggered 'if (axnum >= dev->valuator->numAxes)'
> BUG: ../../Xi/exevents.c:2103 in InitValuatorAxisStruct()
>
> ** Summary changed:
>
> - normal usage then all
I'm currently checking if I can build locally for quick turnaround times
of tests or if I need full LP builds every time ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Uh there is something related as Ubuntu Delta:
From: Balint Reczey
Date: Tue, 22 Oct 2019 17:10:17 +0200
Subject: test: expect mmap to fail in seccomp test on s390 and s390x
(cherry picked from commit a81f7aad9a5ddeebbce002e2da36e1dd84f51b36)
---
src/test/test-seccomp.c | 2 +-
1 file changed,
in GDB with follow-fork-mode child I can check which call is actually
failing in the child:
It is this one:
p = mmap(NULL, page_size(), PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS,
-1,0);
assert_se(p == MAP_FAILED);
It expects a fail (due to seccomp block) but does not get that.
Take it
I have the same issue with PL BackBeat PRO in 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/1845046
Title:
Bluetooth headphones/speaker default to low quality
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x03fffdd2b232 in __GI_abort () at abort.c:79
#2 0x03fffdb03a64 in log_assert_failed_realm () from
/lib/systemd/libsystemd-shared-243.so
#3 0x02aa746e in test_memory_deny_write_execute_mmap ()
x86 32bit is rather similar:
/* test_memory_deny_write_execute_mmap */
Operating on architecture: x86
Failed to add shmat() rule for architecture x86, skipping: Invalid argument
Assertion 'p == MAP_FAILED' failed at src/test/test-seccomp.c:493, function
test_memory_deny_write_execute_mmap().
Seems to be recreatable with
$ sudo /usr/lib/systemd/tests/test-seccomp
--
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/1853852
Title:
hard to reproduce issues in systemd
Isolated to the breaking test:
old: https://paste.ubuntu.com/p/n7BDf3Npwp/
bad: https://paste.ubuntu.com/p/5y5G4GrJYf/
--
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/1853852
Public bug reported:
Hi,
I'm mostly reporting this if to one of the people watching systemd more closely
this is in any form a known issue or if there are any hints.
I recently merged libseccomp 2.4.2 and after a few initial cleanups that worked
well.
But on propsoed-migration I hit systemd
The verification of the Stable Release Update for python3.6 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 python3.6 - 3.6.9-1~18.04
---
python3.6 (3.6.9-1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1835738, backport 3.6.9 to 18.04.
* Python 3.6.9 release.
* Remove patches applied upstream:
- CVE-2018-20852.patch
-
This bug was fixed in the package python3.7 - 3.7.5-2~19.10
---
python3.7 (3.7.5-2~19.10) eoan-proposed; urgency=medium
* SRU: LP: #1835738, backport 3.7.5 to 19.10.
-- Matthias Klose Wed, 20 Nov 2019 10:21:52 +0100
** Changed in: python3.7 (Ubuntu Eoan)
Status: Fix
This bug was fixed in the package python3.7 - 3.7.5-2~18.04
---
python3.7 (3.7.5-2~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1835738, backport 3.7.5 to 18.04.
python3.7 (3.7.5-2) unstable; urgency=medium
* python3.7-dev: Depend on zlib1g-dev, needed to link as an
Thanks! I have hinted virtualbox and will no proceed with releasing
those to -updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1835738
Title:
SRU: Update
The attachment "fix display bug after invoking ^G help" seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
The verification of the Stable Release Update for systemd 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 encounter a
The verification of the Stable Release Update for systemd 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 encounter a
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
The verification of the Stable Release Update for systemd 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 encounter a
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
The verification of the Stable Release Update for systemd 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 encounter a
The verification of the Stable Release Update for systemd 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 encounter a
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
The verification of the Stable Release Update for systemd 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 encounter a
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
The verification of the Stable Release Update for systemd 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 encounter a
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
The verification of the Stable Release Update for systemd 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 encounter a
Public bug reported:
As soon as I've booted my ubuntu 19.10, I've plugged my headphones and
got some clicking sound, but then there was no sound at all afterwards.
The device shows on Settings > Output and it's detected by alsamixer
also.
The headphone works normally on my phone.
This is the
Public bug reported:
There is a silly display bug in nano-4.3
(https://savannah.gnu.org/bugs/?57295): when opening some file (for
example, 'nano README') and typing the sequence Ctrl+W Ctrl+G Ctrl+X,
the Search help text stays on the screen whereas the text of the README
file should be
The verification of the Stable Release Update for systemd 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 encounter a
This bug was fixed in the package systemd - 242-7ubuntu3.2
---
systemd (242-7ubuntu3.2) eoan; urgency=medium
[ Dan Streetman ]
* d/extra/dhclient-enter-resolved-hook:
- Replace use of bash-only &> with > and 2> (LP: #1849608)
*
This bug was fixed in the package systemd - 242-7ubuntu3.2
---
systemd (242-7ubuntu3.2) eoan; urgency=medium
[ Dan Streetman ]
* d/extra/dhclient-enter-resolved-hook:
- Replace use of bash-only &> with > and 2> (LP: #1849608)
*
This bug was fixed in the package systemd - 242-7ubuntu3.2
---
systemd (242-7ubuntu3.2) eoan; urgency=medium
[ Dan Streetman ]
* d/extra/dhclient-enter-resolved-hook:
- Replace use of bash-only &> with > and 2> (LP: #1849608)
*
This bug was fixed in the package systemd - 242-7ubuntu3.2
---
systemd (242-7ubuntu3.2) eoan; urgency=medium
[ Dan Streetman ]
* d/extra/dhclient-enter-resolved-hook:
- Replace use of bash-only &> with > and 2> (LP: #1849608)
*
The verification of the Stable Release Update for systemd 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 encounter a
The verification of the Stable Release Update for systemd 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 encounter a
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
This bug was fixed in the package systemd - 242-7ubuntu3.2
---
systemd (242-7ubuntu3.2) eoan; urgency=medium
[ Dan Streetman ]
* d/extra/dhclient-enter-resolved-hook:
- Replace use of bash-only &> with > and 2> (LP: #1849608)
*
This bug was fixed in the package systemd - 242-7ubuntu3.2
---
systemd (242-7ubuntu3.2) eoan; urgency=medium
[ Dan Streetman ]
* d/extra/dhclient-enter-resolved-hook:
- Replace use of bash-only &> with > and 2> (LP: #1849608)
*
The verification of the Stable Release Update for systemd 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 encounter a
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183
This bug was fixed in the package systemd - 242-7ubuntu3.2
---
systemd (242-7ubuntu3.2) eoan; urgency=medium
[ Dan Streetman ]
* d/extra/dhclient-enter-resolved-hook:
- Replace use of
Here's the change that was made: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/zesty/commit/?id=a87ae50beda8c46c543b39e19070549cf355eb65
It's just the default of the consoleblank= kernel parameter. You can
override it by specifying that parameter to the kernel at boot time
** Changed in: glib2.0 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
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/1844853
Title:
IBus no longer works in Qt
1 - 100 of 110 matches
Mail list logo
