Thanks for the bug report.
Please try selecting 'Ubuntu on Xorg' on the login screen and tell us if
that avoids the bug.
** Summary changed:
- Clamshell mode no longer works after todays updates
+ Laptop monitor does not turn off/disconnect when the lid is closed
** Tags added: multi-monitor
Public bug reported:
After today's updates I can no longer run my Laptop in clam shell mode.
I don't use a dock. I connect the second monitor via HDMI cable and and
external keyboard/mouse via a USB hub.
Usually I can just plugin the monitor and close the lid and the primary
display will
For completeness, a much better and simpler patch is this:
https://salsa.debian.org/pkgutopia-team/packagekit/-/blob/0c43611b82879bd71e633af02878d9c80283f7da/debian/patches/01_fix-single-candidate-pkgid-emission.patch
Maybe that will make its way into Ubuntu Jammy too, but it's not as urgent :-)
** Changed in: tracker-miners (Ubuntu)
Status: New => Fix Released
** Changed in: tracker (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
** Changed in: pulseaudio
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1960307
Title:
No gstreamer dependency
… so if there is some clash between the two packages, mayhaps they
should conflict?
PS For the sake of history: this is very old system which I use since 2009
(starting from
Ubuntu Karmic and upgrading from LTS to LTS). Resolvconf was there since 2012
and I simply
didn't know that it should be
Hmm, hmm. Maybe I found something?
My systemd-resolve which steadily crashed every 3-6 minutes for years now
survived
full 12 minutes since last restart. And it started to resolve unknown names
quickly instead of lagging on them for 10s
The change?
sudo apt remove resolvconf
(this
If your IS department is changing /etc/issue, and then you have not
handled the conffile prompt on upgrade, that isn't something we can fix
for you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
> I've read & consent to terms in IS user agreem't. \n
So where does your modified /etc/issue come from?
** Changed in: base-files (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This also affects the rnv RELAXNG validator, which although a bit long
in the tooth is still useful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to expat in Ubuntu.
https://bugs.launchpad.net/bugs/1961800
Title:
Seeing
Public bug reported:
So, we're UBports, porting Ubuntu Touch stack to Ubuntu 20.04. While
debugging why NM won't manage the phone's USB network interface, I
stumbled upon /usr/lib/NetworkManager/conf.d/10-globally-managed-
devices.conf. This file prevents NM from managing ethernet connection,
** Also affects: systemd (Ubuntu Jammy)
Importance: High
Status: Triaged
** Tags removed: rls-jj-incoming
--
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/1962038
I seem to recall somebody saying that this was a permissions issue with
the way ubiquity is launched from the live desktop environment. I think
the comment was along the lines of ubiquity running as root but the
desktop session is not so orca can't read the screen.
** Tags added: rls-jj-incoming
** Changed in: python-testtools (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-testtools in
Ubuntu.
https://bugs.launchpad.net/bugs/1960297
Title:
Please merge
Public bug reported:
I am uploading tracker 3.3.0 to Jammy now but I want to test things a
bit more before it migrates out of -proposed.
** Affects: tracker (Ubuntu)
Importance: Undecided
Status: In Progress
** Affects: tracker-miners (Ubuntu)
Importance: Undecided
This is fixed release in pending images; which are failing installation due to
other bugs.
Once those bugs are resolved, and a new image is promoted, it shouldn't
experience this zfs issue.
So we are blocked on getting Ubuntu Desktop ISO passing the daily automated
testing and getting promoted.
** Tags added: fr-2083
--
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/1962038
Title:
wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
Status in systemd package in
** Package changed: ubuntu => shadow (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1962186
Title:
Login issue screen and printscreen did not save other than tmp
You have been subscribed to a public bug:
Login screen show poor and issue with picture other than temp folder did
not works to save other directions
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: login 1:4.8.1-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname:
** Tags added: fr-2080
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
https://bugs.launchpad.net/bugs/1961425
Title:
22.04: FTBFS due to test failure
Status in The Ubuntu-power-systems project:
New
** Tags added: fr-2079
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
[Ubuntu 21.10] zlib: compressBound() returns an incorrect result on
z15
Status in
This bug was fixed in the package nss - 2:3.68.2-0ubuntu1
---
nss (2:3.68.2-0ubuntu1) jammy; urgency=medium
* New upstream release. (LP: #1959126)
* d/p/CVE-2021-43527.patch: drop patch applied upstream.
[ Fixed in 3.68.1 ]
-- Athos Ribeiro Mon, 21 Feb 2022
14:55:42 -0300
> I don't see how that Breaks is relevant. "python" != "python-is-
python2", so python3-yaml having a breaks on *python* (<< 2.7.18)
doesn't have any direct impact on the python-is-python2 package. And
Jammy ships python2 2.7.18-3 anyway.
Sorry, I now see that python-is-python2 Provides "python".
Oh, now maybe I see what you mean. If upgrading from Focal to Jammy
without going through Impish, you'll have a "too-old" version of python-
is-python2? Let me think about this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I've investigated and I don't understand the issue. Has something
changed in the archive?
On a Jammy system I was able to install python2, python2.7, python3-yaml
and python3-six, as well as manually install the python-is-python2
package from Impish. I didn't hit any co-installability problems.
I've analyzed the situation on Jammy, Impish and Focal and got the
following result:
Jammy+Impish:
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.default.rp_filter = 2
=> shadowed but equal value
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.*.rp_filter = 2
=> shadows default.rp_filter &
** Tags added: rls-jj-incoming
--
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/1962038
Title:
wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
Status in systemd
Helle
Hello
Here is the access sequence to the encrypted partition from another O.S.
zpool import -N -R /ZFS rpool && sleep 10
if [ -e /dev/zvol/rpool/keystore ] ; then
cryptsetup -v open /dev/zvol/rpool/keystore keystore-rpool && sleep 10
mkdir -p /run/keystore/rpool
mount -v
Removing the duplicate, because while the other bugs focus on the
crashes, this one focuses on dbus stopping. I don't think the crashes
matter, fwiw, dbus should not be stopping in the first place, there's no
way to gracefully recover from that.
** This bug is no longer a duplicate of bug 1961910
Libexpat1 is in wide use and reducing functionality without versioning
seems like a bad idea. After this security update those "misusing" - or
those depending from pyexpat now stopped working properly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
If this happens again try running `SNAPD_DEBUG=1 snap run telegram-
desktop` and collect the log. Since 22.04 is using unified hierarchy, we
try to ask your session's systemd to create a transient scope for it. In
your case, the log indicates that this operation failed. Looking at the
log:
Feb 23
31 matches
Mail list logo
