** Description changed:
As we know, command "look" display lines beginning with a given string,
and the lines are from file "/usr/share/dict/words" by default.
Problem is
- - if we run "look a" or "look b", the result only contains words beginning
with upper-A or upper-B.
- - if we
Public bug reported:
As we know, command "look" display lines beginning with a given string,
and the lines are from file "/usr/share/dict/words" by default.
Problem is
- if we run "look a" or "look b", the result only contains words beginning
with upper-A or upper-B.
- if we run "look" for
This bug was fixed in the package network-manager - 1.42.4-1ubuntu5
---
network-manager (1.42.4-1ubuntu5) mantic; urgency=medium
* d/network-manager.postinst: fix netplan migration logic.
The "continue" is being executed in a subshell so it's not skipping the
next commands.
This bug was fixed in the package network-manager - 1.42.4-1ubuntu5
---
network-manager (1.42.4-1ubuntu5) mantic; urgency=medium
* d/network-manager.postinst: fix netplan migration logic.
The "continue" is being executed in a subshell so it's not skipping the
next commands.
Hello Cristobal, can you make changes from that interface? Or is it
read-only?
Thanks
** Information type changed from Private Security to Public Security
** Changed in: ubuntu-settings (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Package changed: ubuntu => cups (Ubuntu)
--
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/2022107
Title:
printing dubugging doesnt work!
Status in cups package in Ubuntu:
Am I reading the ps faux output from comment #5 correctly, that
needrestart is responsible for starting a dpkg process that starts a
debconf frontend, but there's no terminal available to this process?
Why is needrestart doing operations that would need a debconf frontend?
Should it be doing
I was not able to reproduce the issue during testing following steps:
- disable updates and security
- install openjdk-17-jdk
- update configuration files
- enable updates and security
- run unattended upgrades
The package is not updated
** Changed in: openjdk-17 (Ubuntu)
Status: New =>
Awesome find! Probably for many users, that's a perfectly fine change, I
suspect that auditing home directories isn't going to be a top priority
for many people.
However, the sheer confusion of this issue is troubling: going from
these error messages to "I have to remove a systemd configuration
My use case: I want to be able to spawn a clean shell with a customized
development environment (python) from a Makefile (i.e. `make shell`
runs `bash --init-file .init_file.bash` which does not inherit cruft
from the environment (such as activated conda environments, PATHs etc.)
```
shell:
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/2021929
Title:
upgrade to exiv2 0.28.0
Status in exiv2 package in Ubuntu:
New
Bug
CUPS 2.4.3 has been released, which should fix this problem.
https://github.com/OpenPrinting/cups/releases/tag/v2.4.3
--
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/1971242
I agree that the remaining failures look unrelated to this systemd
update, and they should be hinted:
fwupd/1.7.9-1~20.04.1 armhf: This is a known issue (bug 1994143) and is
addressed by a fwupd upload in focal-proposed.
linux-azure-5.15/5.15.0-1039.46~20.04.1 amd64,
@slyon I saw that https://git.launchpad.net/network-
manager/commit/?h=netplan/lunar-
gu=900b2e15bce37363b263a224e60674f804114693 requires the `file`
package to be available. Some systems don't have installed, albeit
probably not common on desktops but I though I'd mention just in case.
That same
** Changed in: slang2 (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: rasqal (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: nginx (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/network-manager/+git/ubuntu-1/+merge/443876
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Thanks for your bug report.
This problem seems to be caused by the netplan migration logic in the
postinst script. I'm looking into it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
it seems that i've managed to update to it before it was pulled from
updates.
I just hope that 2020604 fix won't revert this fix.
choosing between a fix for kwin crash that often leads to the need to
relogin alltoghether, and a fix for minor chromium graphics glitches -
i'd prefer a fix for kwin
This is what I got from ps faux | less" and "/frontend.
Do you think is ok to kill the process? I can't think about that update
running, has I always get the same response since 7 days.
root1422 0.0 0.0 15424 7740 ?Ss Mar30 2:37 sshd:
/usr/sbin/sshd -D [listener] 0 of
I have a fix for this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2021505
Title:
Flaky DEP8 test: saslauthd
Status in cyrus-sasl2 package in Ubuntu:
In
it was pulled from updates because it caused bug 2020604, and that has a
fix pending on the SRU queue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2003339
Title:
kwin_x11:
According to the launchpad page for mesa 22.2.5-0ubuntu0.1~22.04.2
(https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.2)
the package is still in proposed, not updates. @tjaalton 's message in
#72 suggests it has been released to updates but this appears incorrect.
I'm on 22.04
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
I've proposed a fix for the core22 serie now on
https://github.com/ubuntu/gnome-sdk/pull/143
--
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/2017076
Title:
default
That's correct, but so far llvm updates have been done in tandem with
mesa backports, so I'm not too worried about those this time.
The upstream solution should take that into account, though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
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
** Tags removed: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1698083
Title:
Maximize vertically/horizontally doesn't work (in some apps) if
configured via
** Tags removed: bionic xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/124440
Title:
[enhancement] Ubuntu needs a way to set mouse wheel scrolling speed
Status in
** Tags removed: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1370953
Title:
layout switch is delayed
Status in GNOME Shell:
New
Status in console-setup
** Description changed:
+ * Impact
+
+ The libheif loader is bailing out due to a missing plugin directory
+ which leads to image viewer as eog not being able to open pictures in
+ that format anymore
+
+ * Testcase
+
+ Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog
+
I expect "frontend" to be "/usr/share/debconf/frontend" and therefore
that you have another update (still) running somewhere, waiting for you
to answer a question from debconf.
I like to look at the output of "ps faux" to get more context into what
has started process. You can either "ps faux |
** Changed in: libheif (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/2017420
Title:
Cannot open HEIF/HEIC images in
The issue is fixed in
https://launchpad.net/ubuntu/+source/libheif/1.15.1-1 , we will issue a
stable update also for Lunar
** Changed in: libheif (Ubuntu)
Importance: Undecided => High
** Changed in: gdk-pixbuf (Ubuntu)
Status: Confirmed => Invalid
** Changed in: eog (Ubuntu)
The version of libx11 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11
The version of libx11 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11
The version of libx11 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11
The version of libx11 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
** Changed in: libx11 (Ubuntu Bionic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because
The version of gpgme1.0 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The version of gpgme1.0 in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
** Changed in: gpgme1.0 (Ubuntu Bionic)
Status: Fix Committed => Won't Fix
--
You received this bug notification
The verification of the Stable Release Update for lxc 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 lxc - 3.0.3-0ubuntu1~18.04.3
---
lxc (3.0.3-0ubuntu1~18.04.3) bionic; urgency=medium
* Fix tests issue by avoiding falling back to inexistent trusty LXC images
and using the bionic ones (LP: #1939537)
lxc (3.0.3-0ubuntu1~18.04.2) bionic;
The verification of the Stable Release Update for lxc 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 lxc - 3.0.3-0ubuntu1~18.04.3
---
lxc (3.0.3-0ubuntu1~18.04.3) bionic; urgency=medium
* Fix tests issue by avoiding falling back to inexistent trusty LXC images
and using the bionic ones (LP: #1939537)
lxc (3.0.3-0ubuntu1~18.04.2) bionic;
The verification of the Stable Release Update for lxc 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 lxc - 3.0.3-0ubuntu1~18.04.3
---
lxc (3.0.3-0ubuntu1~18.04.3) bionic; urgency=medium
* Fix tests issue by avoiding falling back to inexistent trusty LXC images
and using the bionic ones (LP: #1939537)
lxc (3.0.3-0ubuntu1~18.04.2) bionic;
The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
** Changed in: network-manager (Ubuntu Bionic)
Status: Fix Committed => Won't Fix
--
You received this bug
The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the target
series has reached its End of Life.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The version of unattended-upgrades in the proposed pocket of Bionic that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.
** Changed in: unattended-upgrades (Ubuntu Bionic)
Status:
The version of unattended-upgrades in the proposed pocket of Bionic that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.
--
You received this bug notification because you are a member of
The version of unattended-upgrades in the proposed pocket of Bionic that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.
--
You received this bug notification because you are a member of
57 matches
Mail list logo
