** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1852837
Title:
Ubuntu 19.10 boots into blinking underscore when manually
** 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/1843381
Title:
Dell system takes a long time to
[Expired for pocketsphinx (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: pocketsphinx (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pocketsphinx in
[Expired for pocketsphinx (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: pocketsphinx (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pocketsphinx in
[Expired for pocketsphinx (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: pocketsphinx (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pocketsphinx in
Public bug reported:
Hello,
I didn't exactly know which category to slected during bug report
submission, but after I updated my Ubuntu 19.10 installation yesterday,
whenever I press restart either through gui or terminal the system boot
into blinking underscore immediately after bios post
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
umockdev/0.11.1-1 (ppc64el)
A better workaround solution to this problem is the systemd
wpa_supplicant.service override.
This is better than messing with broken packages and versions.
Here is my systemd override.conf (you can apply it with `systemctl edit
wpa_supplicant`):
[Service]
Seeing same problem on my xubuntu machine after upgrade to 19.10. I
tried different GDM's (xubuntu, gnome, xfce) and tried different themes
(default, Adwaita, Breeze, DMZ). I have basic Intel graphics card with
minimal capabilities, and machine is used in production so I'm unable to
experiment
After a few tests, I confirm that the bug looks fixed to me.
--
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/1847896
Title:
Unable to shutdown or restart from log-in
After a few tests, I confirm that the bug looked fixed to me.
--
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/1847896
Title:
Unable to shutdown or restart from log-in
Upstream stated that it's fixed in gtk 3.24 which is newer Ubuntu
series, closing. The bug can still make to target bionic if we believe a
SRU for it should be workedon
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
The bug is in GTK3.
https://gitlab.gnome.org/GNOME/eog/issues/4
https://gitlab.gnome.org/GNOME/gtk/issues/657
** Bug watch added: gitlab.gnome.org/GNOME/eog/issues #4
https://gitlab.gnome.org/GNOME/eog/issues/4
** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #657
You have been subscribed to a public bug:
When a image with much higher height than width is opened, the window
decoration becomes very big, as it tries to keep the image proportional:
https://i.imgur.com/SZu0lOk.png
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: eog 3.28.1-1
Uname: Linux
@paulw2u My apologies. After double-checking, I found out that (for
whatever reason) eoan-proposed were disabled for me. I'll retest and
report here if an update doesn't help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: systemd
Status: Unknown => 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/1846232
Title:
networkd pads interface MTU by 4 bytes for
The fix has not yet been released but is in a period of testing. Did you
follow the instructions in comment #15? The updated package is in
-proposed and will be for a *minimum* of seven days from the date of
comment #15.
If you want to test whether the update works for you then please follow
the
Same for me as of this today: logging off, then navigating through the
menu in the right upper screen corner till the turn-off button and then
clicking it produces no effect in eoan.
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Committed => In Progress
--
You received this bug
Public bug reported:
I have described my problems here:
https://askubuntu.com/questions/1186588/no-sound-except-popping-noises-on-my-hp-aio-realtek-alc225-for-all-linux-distr
I still have no sound (ubuntu 19.10). Thanks in advance
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base
still there with ubuntu 19.10 everything & freshly upgraded
--
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/1847896
Title:
Unable to shutdown or restart from log-in screen
I believe this is due to
https://github.com/systemd/systemd/commit/4b151b71320bbee1549afcbad5554a40d90d63b4
and probably is
https://github.com/systemd/systemd/issues/12552
fixed by
https://github.com/systemd/systemd/pull/12574/commits
which prevents the automatic mtu bump when MTUBytes is
> This looks to be related to networkd:
sorry, I didn't read comments before posting, you found it already :)
--
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/1846232
Title:
Tests were performed with Intel Dual Band Wireless-AC 7265 card.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1827757
Title:
PMF
Status in wpa package in Ubuntu:
** Summary changed:
- vmtests: test_ip_output failing in vlan tests on eoan
+ networkd pads interface MTU by 4 bytes for vlan even when told not to
--
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: wpa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
Can confirm that this problem still exist on the latest LTS release.
I tested connecting to enterprise network with enabled and required PMF (
Protected Management Frames / Management Protected Frames or 802.11w ) on
Ubuntu 18.04.3 LTS (with all updates) - all attempts failed, when the PMF was
I found this bug report because I have the same issue, but I think it's
because the interface is "UP". When I try the same "set" command on a
"DOWN" interface, it's successful. My issue is figuring out how to run
the set command during the boot process on the eth0 interface, before it
comes up.
I can confirm that systemd 237-3ubuntu10.33 fixes this issue for me on
bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
This is also going to need the following to be fixed for focal:
LP: #1852772
LP: #1852773
--
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/1852489
Title:
[SRU]
Thanks
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
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/1852018
Title:
Audio Stops Playing Briefly
Thank you for your bug report, could you report it upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues ?
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Adding gpg to build-depends helps but then we get the following due to
missing gpg-agent:
==
FAIL: test_add_gpg_key (tests.test_dbus.TestDBus)
--
Traceback (most
Public bug reported:
==
ERROR: test_add_ppa_signing_key_multiple_fingerprints
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
** Changed in: software-properties (Ubuntu)
Status: New => Triaged
** Changed in: software-properties (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Public bug reported:
==
FAIL: test_updates_interval (tests.test_dbus.TestDBus)
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.33 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Che, 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.33 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Steve, 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.33 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Neil, 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.33 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Marc, 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.33 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 bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.33 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Bruno, 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.33 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello jrb0001, 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.33 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 bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.33 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 bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.33 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks for reporting.
I'm closing this after your comment. I strongly suspect the problem was
that focal wasn't found in the list of possible Ubuntu releases.
Whenever a new developmen cycle starts, the new code name needs to be
added in a couple of places and this can sometimes take a few days.
oops, copied too much in the last comment; the first part of that is
verification for bug 1849733 (which i pasted in there as well). After
the ^C is verification for this bug.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
bionic verification note: as mentioned in description, the commit
introducing this wasn't present in bionic so this bug isn't reproducable
with version 237-3ubuntu10.31; however that commit was added to version
237-3ubuntu10.32 in bug 1849733, so the verification here doesn't need
to check version
ubuntu@lp1849733-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
ubuntu@lp1849733-b:~$ telnet toomany100.ddstreet.org
telnet: could not resolve toomany100.ddstreet.org/telnet: Temporary failure in
name resolution
ubuntu@lp1849733-b:~$ dpkg
** Changed in: systemd
Status: Unknown => 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/1852754
Title:
networkd does not complete interface
ubuntu@lp1832672-b:~$ dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
ubuntu@lp1832672-b:~$ grep bar /etc/hosts
127.0.2.1 foo # bar
ubuntu@lp1832672-b:~$ systemd-resolve -4 bar
bar: 127.0.2.1
-- Information acquired via protocol DNS in 1.5ms.
--
Public bug reported:
There's a WiFi network to which I sometime connected and saved it and
set it to automatically connect when available; however the password was
changed, so whenever my laptop automatically tries to connect to that
network, I get the prompt to enter the password. So far all
the backport for this bug has caused regression-proposed bug 1852754
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-failed verification-failed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
[impact]
interfaces configured with .network file [Link] section specifying
MTUBytes will not be successfully brought up.
[test case]
configure interface e.g.
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
[Link]
MTUBytes=1550
start/restart networkd, the
"I think you're trying to start dhclient on an interface that's already
setup."
It just triggers a lease refresh on the existing interface, which has
the same issue.
Nov 15 14:17:10 srv-ywz63 systemd-logind[981]: New session 27 of user ubuntu.
Nov 15 14:17:10 srv-ywz63 systemd[1]: Started
Public bug reported:
'xset dpms force off' blanks the screen but does not switch off the HDMI
(LCD) monitor backlight.
'xset -q' shows DPMS is enabled.
'tvservice -o' does switch off the monitor.
No warnings/errors related to dpms in /var/log/XOrg.0.log
Not sure if this is a xorg, kernel,
> ubuntu@srv-ywz63:~$ sudo dhclient eth0
> RTNETLINK answers: File exists
I think you're trying to start dhclient on an interface that's already
setup.
root@lp1805183-b:~# dpkg -l systemd|grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
root@lp1805183-b:~#
No did not experience it with paplay
--
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/1852018
Title:
Audio Stops Playing Briefly When Emptying Trash
Status in
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
Examining the information you have given us, I wonder if you would be
better seeking Support instead of filing a bug report.
This bug report can be converted to a question (which is aimed at
support). You can
Public bug reported:
How to install Intel r HD Graphics install in Lenovo Desktop Model
No.mtm 3156-RY6
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-36-generic x86_64
ApportVersion:
I can confirm that systemd 237-3ubuntu10.32 fixes this issue for me on
disco.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
70 matches
Mail list logo
