Public bug reported:
[IMPACT]
uptime will provide incorrect data after 52 weeks. This is at least confusing
for users utilizing this tool.
Issue is already fixed in upstream
https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749.
Latest procps releases already
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2035063
Title:
package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade:
The patch fixing the upstream linked issue is: radeonsi/vcn: fix the
incorrect dt_size
and it is in mesa main (which will be in 23.3), as well as 23.1.7, which
is already in Ubuntu mantic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags added: fr-3189
** Also affects: software-properties (Ubuntu Mantic)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: se se-sponsor-dgadomski
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2035061
Title:
uptime -p reports incorrect output after 52 weeks
Status in procps
** Changed in: procps (Ubuntu)
Assignee: (unassigned) => Robert Malz (rmalz)
** Also affects: procps (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: procps (Ubuntu Focal)
Public bug reported:
running Ubuntu off a USB drive on my hp pavilion windows 10 laptop.
This issue came up after upgrade from Bionic Beaver.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam0g:amd64 1.3.1-5ubuntu4.6
ProcVersionSignature: Ubuntu 5.4.0-162.179-generic 5.4.246
debdiff with backport for jammy
** Patch added: "uptime_jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2035061/+attachment/5699852/+files/uptime_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
debdiff with backport for focal
** Patch added: "uptime_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2035061/+attachment/5699853/+files/uptime_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Hello,
I have a job scheduled via an in-house task scheduler(using cron).
The task runs perfectly when it's run manually.
But fails when run on the cron.
The root user is used to run the task in both scenarios(Manually and
Cron).
We get the below apparmor denial when the
The attachment "uptime_jammy.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" tag, and
This bug was fixed in the package zsh - 5.9-5
---
zsh (5.9-5) unstable; urgency=medium
* [138340f9,dc77864f] Cherry pick multiple (partial) upstream commits to
migrate zsh's pcre module to pcre2. Update Build-Depends, Build-Using
and debian/tests/control from libpcre3-dev
** Changed in: zsh (Debian)
Status: Confirmed => 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/1792544
Title:
demotion of pcre3 (8.x) a.k.a pcre
Public bug reported:
When working with ubuntu core or ubuntu core desktop, neither
/etc/default/locale nor /etc/default/keyboard are modificable, so it's
not possible to set the global keyboard or the global language.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
In ubuntu core desktop, we need to be able to change these two files to
allow to set the GDM keyboard and language.
--
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/2035122
Verified for lunar and jammy:
# lxc launch ubuntu:jammy test-openssh-lunar
# lxc exec test-openssh-lunar bash
# cat
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
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/2033325
Title:
systemd fails to set unit as
We will definitely need to fix this in Jammy, but I am not sure it makes
sense to do so in Mantic given the state of x11 keymap support (see bug
2030788).
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Jammy)
Importance:
I have a patch that fixes this. We are already using it in ubuntu core
desktop. I'm preparing to upload it to the GIT repo.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
We should really address the root of this problem instead of continuing
to patch src:systemd.
--
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/2035122
Title:
Under ubuntu
This bug was fixed in the package systemd - 253.5-1ubuntu5
---
systemd (253.5-1ubuntu5) mantic; urgency=medium
* Revert "core/service: when resetting PID also reset known flag" (LP:
#2033325)
Thanks to Sergio Durigan Junior
File:
I also tried restarting cups and the printer as suggested here
https://forum.snapcraft.io/t/new-interface-cups-for-all-snaps-which-
print/29702/5 but Chromium still does not show the printer queue as a
Destination (only Save as PDF is available).
--
You received this bug notification because you
** Changed in: command-not-found (Ubuntu Kinetic)
Status: Confirmed => Won't Fix
** Changed in: libdrm (Ubuntu Kinetic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
Hi,
I have the same issue as well, on two different boxes (ubuntu 22.04)
with two different printers (HP & Samsung).
The printers show up in "system" settings. The Firefox snap is able to
print correctly, it is connected to cups-control (not cups as the
Chromium snap).
Here's the relevant
** Also affects: mesa (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2
25 matches
Mail list logo
