This bug was fixed in the package binutils - 2.40-2ubuntu4
---
binutils (2.40-2ubuntu4) lunar; urgency=medium
* debian/binutils-common.preinst: remove /etc/gprofng.rc if it has not been
modified to avoid unnecessary conffile prompt on upgrade (LP: #2015778)
-- Nick Rosbrook
All autopkgtests for the newly accepted openssh (1:8.2p1-4ubuntu0.7) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.44.1-1ubuntu1.2 (amd64, ppc64el)
Please visit the excuses page listed below and investigate the failures,
I was experiencing the same issue on Kubuntu 22.04.2. It ships 22.0.1
mesa version and this bug was fixed on 22.3.0 (as the tag says).
Search for kisak-mesa stable ppa to upgrade your mesa version to 22.3.7,
issue is gone there.
--
You received this bug notification because you are a member of
Tested openssh-server/focal-proposed,now 1:8.2p1-4ubuntu0.7 amd64
[installed]
creating /etc/ssh/sshd_config.d/.conf:
Match User
PasswordAuthentication No
worked as expected: prohibited password login while allow publickey
authentication
** Tags removed: verification-needed-focal
** Tags
Hello Gerard, or anyone else affected,
Accepted openssh into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.2p1-4ubuntu0.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
For me installing `dbus-user-session` fixed this issue
--
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/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap
Hello Thomas, or anyone else affected,
Accepted krb5 into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/krb5/1.19.2-2ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I commented out the suggested line but the only effect is that switching
accounts is now completely impossible. More specifically, it prevents me from
getting past the login screen:
1. I select "switch user" from my running user session
2. I am sent to the login screen
3. I select a different
The attachment "binutils_2.40-2ubuntu4.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
Please, please fix this.
That hampers the switch from an android to an ubuntu touch device very
seriously.
I bought a Pixel 3a and managed to install it. But exporting over 600 contacts
from my old phone to vcard and then not being able to even import the important
ones due to the buggy smb in
This bug was fixed in the package livecd-rootfs - 2.828
---
livecd-rootfs (2.828) lunar; urgency=medium
* 099-ubuntu-image-customization.chroot: Remove redundant creation of oem
user and oem-config-prepare (LP: #2016285)
-- Dave Jones Fri, 14 Apr 2023 09:48:31
+0100
**
I have changed the patch to hardcode the expected md5sum instead.
** Patch added: "binutils_2.40-2ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+attachment/5664098/+files/binutils_2.40-2ubuntu4.debdiff
--
You received this bug notification because you are
I tested the attached patch using my PPA
https://launchpad.net/~enr0n/+archive/ubuntu/lp2015778/+packages, and I
did not get the conffile prompt during upgrade.
root@kinetic:~# apt-cache policy binutils-common
binutils-common:
Installed: 2.39-3ubuntu1.1
Candidate: 2.39-3ubuntu1.1
Version
Public bug reported:
Web pages display and app launch are VERY slow for a PC having this
configuration. There is really a problem about display since I bougth
this PC.
And ...
Since last big upgrade (including some Nvidia stuff) :
No more gear on login to switch to Wayland/X11.
Night mode in
This bug was fixed in the package ubuntu-settings - 23.04.5
---
ubuntu-settings (23.04.5) lunar; urgency=medium
* ubuntu-raspi-settings-desktop: Don't attempt to prepare oem-config in
postinst; there's no guarantee oem-config is installed yet and it cannot
be a dependency
This bug was fixed in the package ubuntu-settings - 23.04.5
---
ubuntu-settings (23.04.5) lunar; urgency=medium
* ubuntu-raspi-settings-desktop: Don't attempt to prepare oem-config in
postinst; there's no guarantee oem-config is installed yet and it cannot
be a dependency
Public bug reported:
free command: in Italian header is misaligned and wrongly translated
gratuiti is 'for free' or 'gratis' or 'toll free'
'free' may be translated with 'liberi'
total = totali ... ok
used = usati ... ok
free = liberi ... to be changed
shared = condivisi
*** This bug is a duplicate of bug 2015962 ***
https://bugs.launchpad.net/bugs/2015962
** Package changed: indicator-messages (Ubuntu) => accountsservice
(Ubuntu)
** Changed in: accountsservice (Ubuntu)
Status: New => Fix Released
** This bug has been marked a duplicate of bug
You have been subscribed to a public bug:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
indicator-messages. This problem was most recently seen with package version
13.10.1+18.10.20180918-0ubuntu3, the problem page at
@enr0n ah, that makes sense (and apologies to @zhsj; I suspect I
misinterpreted comment 2!)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/2015778
Title:
conffile prompt
Thank you so much to everyone involved :)
--
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/2004478
Title:
systemd-networkd's dhcp4 client ignores local subnet routes
Verified kinetic in a schroot:
```
(kinetic)bdrung@deep-thought:/$ dpkg -s tzdata | grep Version
Version: 2023c-0ubuntu0.22.10.1
(kinetic)bdrung@deep-thought:/$ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z"
Fri Jul 1 12:00:00 CEST 1960
(kinetic)bdrung@deep-thought:/$ TZ=Europe/Berlin date -d
Public bug reported:
NSS should be rebuilt with this patch:
diff --git a/debian/libnss3.dirs b/debian/libnss3.dirs
new file mode 100644
index ..0f796964
--- /dev/null
+++ b/debian/libnss3.dirs
@@ -0,0 +1 @@
+etc/nss
diff --git a/debian/rules b/debian/rules
index 5ab1ced0..51bee160 100755
There's more complexity of course because I only talk about the first
of the two solvers apt runs. The first solver marks the changes based on
following the graph from the user-initiated actions downward to
dependencies, marking Depends for install, Conflicts for remove, and so
on.
If that
** Information type changed from Private Security to Public Security
--
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/2016023
Title:
viewing an apport-cli crash with default
Public bug reported:
When trying to find my home network in the wifi network list I am not
able to view it. I can view the network with Windows (on same hardware),
with my phone, my various smart devices can all find and connect to it
to, just not my Ubuntu OS. Two other nearby networks show up
Hello,
thanks for the update!
I understand the reluctance to change something like that. But I still don't
understand why the issue is not present when the version 245.4-4ubuntu3.19 is
installed instead of 245.4-4ubuntu3.20.
> root@ubuntu2004:~# apt list --installed systemd
> Listing... Done
>
** Changed in: systemd (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2016141
Title:
[focal] cannot resolve dependency when
Hello Benjamin, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Benjamin, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Benjamin, or anyone else affected,
Accepted tzdata into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.22.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello errors.ubuntu.com, or anyone else affected,
Accepted apport into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.23.1-0ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package.
Setting to critical as this currently prevents the creation of the
ubuntu rpi desktop images.
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-settings (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because
Public bug reported:
Users upgrading Ubuntu desktop for Raspberry Pi from kinetic to lunar
may notice that the new growroot-almost.service persistently fails as
the root is already resized. The unit should be updated to fail silently
and prevent future runs.
** Affects: ubuntu-settings (Ubuntu)
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/441072
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
Public bug reported:
There are two (semi-related) issues which are currently preventing the
creation of Ubuntu desktop images for the Raspberry Pi:
The first is that livecd-rootfs is erroneously trying to create the oem
user (and run oem-config-prepare) twice in live-
Fix-released in livecd-rootfs 2.818
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2004430
This was fixed-released in livecd-rootfs 2.818
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
** Attachment added: "brightness.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2016281/+attachment/5663971/+files/brightness.png
** Description changed:
After each brightness-step change (via using Fn+arrow up-/arrow-down
keys), system freezes for ~500ms. With my notebook's 10
Public bug reported:
After each brightness-step change (via using Fn+arrow up-/arrow-down
keys), system freezes for ~500ms. With my notebook's 10 brightness-
levels, this often results in total delay from 10x 500ms, = 5 entire
seconds for the notebook finishing a multi-step brightness-change in
** Package changed: ubuntu => alsa-driver (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/2016244
Title:
Intel Tiger Lake internal sound card not detected
You have been subscribed to a public bug:
Huawei Matebook D14 with Core i3-1115G4 no sound card at all, "Dummy
output" only, no even HDMI output. The codec is ESSX8336 I suppose.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu
This bug was fixed in the package icu - 72.1-3ubuntu2
---
icu (72.1-3ubuntu2) lunar; urgency=medium
* d/p/test-canonical-ids.patch: update TestCanonicalIDs to match latest
tzdata, including the de-aliasing due to pre-1970 data (LP: #2016021)
-- Simon Chopin Wed, 12 Apr 2023
Please also enable debug in /etc/gdm3/custom.conf and check for any
crash reports in /var/crash/
--
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/2006059
Title:
systemd
Please try editing /usr/lib/systemd/user/org.gnome.Shell@x11.service and
comment out:
# ExecCondition=/bin/sh -c 'test "$XDG_SESSION_TYPE" = "%I" || exit 2'
If that doesn't fix it then it would seem the issue is that Xorg hasn't
been set up for us before we try to start gnome-shell on it.
--
Looks like we even declared it fixed in bug 1945008.
--
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/2006059
Title:
systemd refuses to start secondary Xorg logins
All upstream references do seem to point to
https://gitlab.gnome.org/GNOME/gdm/-/issues/733 but the "fix" for that
is already in gdm3 version 41.3 and later. Yet the bug still happens.
Some people are focussed on the cgroup errors that come before it, but I'm not
sure if they're really related:
*** This bug is a duplicate of bug 2006059 ***
https://bugs.launchpad.net/bugs/2006059
Moved to bug 2006059.
** This bug has been marked a duplicate of bug 2006059
gdm requires a second login to start xorg session instead of wayland
--
You received this bug notification because you are
*** This bug is a duplicate of bug 2006059 ***
https://bugs.launchpad.net/bugs/2006059
** Attachment added: "syslog.gz"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016193/+attachment/5663886/+files/syslog.gz
** Summary changed:
- "switch to" a new user immediately aborts,
This is the expected behavior of apt, and a deeply integral part of the
solver algorithm, that it does not try to remove packages that have an
upgrade available. So that's not something I'd want to touch because the
regression potential is huge.
You can always use pass systemd-timesyncd- to apt
This looks exactly like I would expect:
1. Xorg fails to start in the same way as bug 2015386:
Apr 13 23:35:23 nvidia-dgx-station-c25989 systemd[3916]: Condition
check resulted in GNOME Shell on X11 being skipped.
2. Wayland fails to start because the server driver doesn't support it:
51 matches
Mail list logo
