This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
aws-6.11' to 'verification-done-noble-lin
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2072586
Title:
Running "dconf update" with different umask affect
** Description changed:
[ Impact ]
This was originally reported by a user applying the DISA-STIG on Ubuntu
desktop [1], which requires a global umask of 077. The global dconf databases
in /etc/dconf/db are intended to be read by many users (mode 644).
dconf uses g_file_set_contents
** Merge proposal linked:
https://code.launchpad.net/~whershberger/ubuntu/+source/glib2.0/+git/glib2.0/+merge/485046
** Merge proposal linked:
https://code.launchpad.net/~whershberger/ubuntu/+source/glib2.0/+git/glib2.0/+merge/485047
** Merge proposal linked:
https://code.launchpad.ne
** Description changed:
[ Impact ]
This was originally reported by a user applying the DISA-STIG on Ubuntu
desktop [1], which requires a global umask of 077. The global dconf databases
in /etc/dconf/db are intended to be read by many users (mode 644).
dconf uses g_file_set_contents
** Description changed:
+ [ Impact ]
+
+ This was originally reported by a user applying the DISA-STIG on Ubuntu
+ desktop [1], which requires a global umask of 077. The global dconf databases
+ in /etc/dconf/db are intended to be read by many users (mode 644).
+
+ dconf uses g_file_set_contents
** Changed in: glib2.0 (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: glib2.0 (Ubuntu Oracular)
Status: Triaged => In Progress
** Changed in: glib2.0 (Ubuntu Plucky)
Status: Triaged =>
All autopkgtests for the newly accepted tzdata (2025b-0ubuntu0.24.10.1) for
oracular have finished running.
The following regressions have been reported in tests triggered by the package:
astroplan/unknown (ppc64el, s390x)
astropy/unknown (ppc64el, s390x)
chrony/unknown (ppc64el, s390x)
dask.dist
As extra context, the .jpg is opened with the glycin-image-rs loader.
$ apt-file list glycin-loaders
glycin-loaders: /usr/libexec/glycin-loaders/1+/glycin-heif
glycin-loaders: /usr/libexec/glycin-loaders/1+/glycin-image-rs
glycin-loaders: /usr/libexec/glycin-loaders/1+/glycin-jxl
glycin-loaders: /
All autopkgtests for the newly accepted tzdata (2025b-0ubuntu0.20.04.1) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
libical3/unknown (amd64, ppc64el)
php7.4/unknown (amd64, ppc64el)
postgresql-12/12.22-0ubuntu0.20.04.2 (arm64, a
Hi Nick, thanks for having the upload(s) sponsored.
I definitely makes sense to add a quick tests for all tools that call
read_utmp().
I expanded the test plan accordingly.
** Description changed:
SRU Justification:
--
[ Impact ]
- * The small but well known and po
I first upgraded apt, libapt-pkg6.0t64 to 2.8.3.
Validation for RSA1024 remaining weak:
root@noble:~# gpg --quick-gen-key j...@debian.org rsa1024
gpg: directory '/root/.gnupg' created
gpg: keybox '/root/.gnupg/pubring.kbx' created
We need to generate a lot of random bytes. It is a good idea to
As discussed before and documented in the bug description, we are
ignoring this for verification purposes, and setting this to done. The
bug will be reopened once the update has been released to be fixed
properly in a future upload.
** Tags removed: block-proposed block-proposed-noble verification
The autopkgtests for apt/noble have passed; per the documented test plan
> To validate the APT change on noble, we must rely on the test suite as
we won't have a noble->oracular upgrade bug causing it, most likely.
I am hence setting this to verification-done-noble.
** Tags removed: verification
The autopkgtests for APT have passed on all releases, so marking the bug
as verified per the test plan (as the test suite includes the tests for
this bug).
All regressions except for update-manager/noble have been resolved by
retries. The update-manager regressions in noble are caused by the
chang
** Also affects: coreutils (Ubuntu Questing)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Questing)
Importance: Undecided
Status: Won't Fix
** Also affects: coreutils (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: syst
Hello Benjamin, or anyone else affected,
Accepted tzdata into plucky-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2025b-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Since the development of the Q-release ("Questing Quokka") just started, and we
have now the coreutils package in P and Q in the same version, the versioning
for both releases need to be slightly adjusted to ensure proper upgradeability.
Hence uploading this tgz file that incl. two debdiffs (for
Bug report did not expire due to bug watch
With no response to comment #2 closing as no longer valid
** Changed in: telepathy-mission-control-5 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: hundredpapercuts
Status: Incomplete => Invalid
--
You received this bug notificatio
20 matches
Mail list logo
