** Tags added: server-todo
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114224
Title:
freeradius uninstalled after upgrade to 24.04
To manage notifications a
If I just change "jammy" to "noble" in apt's sources.list and attempt a
dist-upgrade, freeradius is kept and upgraded as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114224
Title:
freera
Confirmed.
From logs in /var/log/dist-upgrade:
main.log:
2025-06-13 21:16:14,690 DEBUG Remove: freeradius freeradius-utils
** Changed in: freeradius (Ubuntu)
Status: New => Confirmed
** Changed in: freeradius (Ubuntu)
Importance: Undecided => High
--
You received this bug noti
I think next steps here are a questing upload, with a quick PR which
could also get the opinion of the apparmor team (and perhaps even
propose this to apparmor upstream, they might have the sssd profile over
there too). For an SRU, I think the aa-exec test plan might not be
enough: it does test the
I would think it to be generally safe to allow sssd to read files in
/etc/sssd/pki/**.
Mimicking what the profile already has for other subdirectories of
/etc/sssd:
/etc/sssd/pki/ r,
/etc/sssd/pki/** r,
> Particularly would just /etc/sssd/pki/sssd_auth_ca_db.pem be sufficient to
> alleviate th
This is not "just a bug". It will be quite an effort to handle this
gracefully, including upgrades. Honestly, I don't see this being handled
anytime soon.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubunt
I have retried the failed autopkgtests, hopefully they will pass soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107550
Title:
ipmitool sel get is not showing hour in the timestamp details
To
# Oracular verification
## Reproducing the bug
$ lxc exec $release-test -- ipmitool sel get 1
SEL Record ID : 0001
Record Type : 02
Timestamp : 08/16/15 08/16/15 <
(...)
$ lxc exec $release-test -- apt-cache policy ipmitool
ipmitool:
Installed: 1.8.19-7ub
# Noble verification
## Reproducing the bug
$ lxc exec $release-test -- ipmitool sel get 1
SEL Record ID : 0001
Record Type : 02
Timestamp : 08/16/15 08/16/15
(...)
$ lxc exec $release-test -- apt-cache policy ipmitool
ipmitool:
Installed: 1.8.19-7ubuntu0.24.0
linuxptp was sponsored by me.
** Changed in: linuxptp (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083458
Title:
Add AppArmor profiles for lin
ntpsec as proposed here is in questing already (was in plucky also),
closing bug.
** Changed in: ntpsec (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I see this in plucky as well, while I was running "ubuntu-bug
libwayland-server0". Quite annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1997179
Title:
Screenshot- Ubuntu-bug asks 3x times f
I filed the bug while logged back into a good, working, xorg session.
Maybe that affected the information that ubuntu-bug decided to attach,
let me know if you need something else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
In plucky, I decided to try out wayland. Logged out, logged back in into
a wayland session, all seemed fine.
Until I started a google meet. See attached screenshot.
This is not the usual complaint about screen sharing not working, or
high CPU usage, or all that stuff we know
chrome is
google-chrome-stable 137.0.7151.103-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114504
Title:
chrome doesn't work in meet with wayland, just xorg
To manage
Sounds good, let's check again tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111952
Title:
Remmina prompts for RDP credentials even when they are saved
To manage notifications about this
I agree to not pursue oracular further in this case.
$ remove-package -m "Superseeded by security, decided to not purse further. See
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2098183/comments/24"; -s
oracular-proposed -e 256.5-2ubuntu3.2 systemd
Removing packages from oracular-propo
Hello Chengen, or anyone else affected,
Accepted systemd into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/255.4-1ubuntu8.9 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
I ran this command to verify that the changes on top of the latest
security update are the same as the original update that was superseeded
by security, and they are:
$ git range-diff pkg/import/255.4-1ubuntu8.6..pkg/import/255.4-1ubuntu8.7
pkg/import/255.4-1ubuntu8.8..queue/noble/unapproved/8ec2
Hello Jacopo, or anyone else affected,
Accepted cloud-init into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/24.4.1-0ubuntu0~20.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Jammy still had an autopkgtest failure on systemd, which I retried.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106167
Title:
[SRU exception] backport 5.47 to Jammy, Noble, and Oracular
To manag
The verification of the Stable Release Update for autopkgtest 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 encount
Hi, did you have a chance to look at the upstream fix[1] and determine
if it's something we can use, instead of skipping the troublesome
autopkgtest?
1. https://github.com/gerrymanoim/exchange_calendars/issues/452
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
The verification of the Stable Release Update for kdeconnect 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 encounte
> This will be a great improvement to the UI (showing why the
credentials window appeared).
That sounds good. What do you think about my test plan modification
suggestions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
The bug description hints that this failure as described here doesn't
happen all the time, but "often":
> MAAS datasource isn't often ready when cloud-init starts sending
requests to it
The test plan then asks this:
> Verify the machine boots successfully and can be SSH'ed into.
If the fail
Uploaded:
Uploading frr_10.3-3ubuntu1.dsc
Uploading frr_10.3.orig.tar.xz
Uploading frr_10.3-3ubuntu1.debian.tar.xz
Uploading frr_10.3-3ubuntu1_source.buildinfo
Uploading frr_10.3-3ubuntu1_source.changes
** Changed in: frr (Ubuntu)
Status: In Progress => Fix Committed
--
You received this
This looks good, but please amend the test plan with an extra
verification.
We should also test the cases where the prompt *should* appear. For example:
a) the credentials that were saved (username or password) are incorrect.
Ideally, not only should the prompt appear, but it should also say why
** Changed in: remmina (Ubuntu Noble)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111952
Title:
Remmina prompts for RDP credentials even when they are s
I didn't see an oracular task, and it still has version 1.4.35, same as
noble. Checking the code[1], looks like the fix is not there:
case AUTH_RDP:
key_title = _("Enter RDP authentication credentials");
key_user = "username";
So here is the plan:
- process this SRU, and if ok, accept it into focal-proposed (basically done,
see comment #32)
- find a good way to test it in focal-proposed (I have to double check the test
plan still)
If we are sure of the fix, then internally find resources to build a new
focal image for
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/486935
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110434
Title:
Merge frr from Debian Unsta
The verification of the Stable Release Update for cloud-init 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 encounte
Given the seriousness of this bug, the small change needed to fix it,
and the amount of testing done by different teams and people, I'm
waivering the 7 day aging period and doing an early release of this
update.
Thanks to all who have troubleshooted, fixed, and tested this!
--
You received this
$ remove-package -s noble-proposed -m 'emoved per request, see LP: #2063447
comment #3 and matrix thread
https://matrix.to/#/!slcYrFqWytcsbPzMxA:ubuntu.com/$32MVGqFrdQSsdDAIDSxFMmhTHhvG--UQZbsSNqI8CTM?via=ubuntu.com&via=matrix.org&via=matrix.debian.social'
netavark
Removing packages from noble-
$ remove-package -s noble-proposed -e 1.6.0-1ubuntu1 -m 'removed per request,
see LP: #2063401 comment #4 and matrix thread
https://matrix.to/#/!slcYrFqWytcsbPzMxA:ubuntu.com/$32MVGqFrdQSsdDAIDSxFMmhTHhvG--UQZbsSNqI8CTM?via=ubuntu.com&via=matrix.org&via=matrix.debian.social'
aardvark-dns
Removin
Up for review, all good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110434
Title:
Merge frr from Debian Unstable for questing
To manage notifications about this bug go to:
https://bugs.launchpa
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2113797 was released
for jammy-updates just now. Once the dust settles, I would like to come back to
this bug here and understand the impact:
a) is it really affecting only focal? Or jammy and later as well?
b) who is interested in a focal
Uploaded: https://launchpad.net/ubuntu/+source/postfix/3.10.2-1ubuntu1
** Changed in: postfix (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110451
Weird that the 10.3 release notes[1] say that they added lua 5.4
support, but I don't see it in the code, and our patches still apply.
I'll try a build without our patches, to confirm.
1. https://frrouting.org/release/10.3/
--
You received this bug notification because you are a member of Ubun
Yeah, that release notes entry is wrong. The build fails immediately:
configure: error: Lua 5.3 is required to build with Lua support. No
other version is supported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
uh, hold that thought. Something odd is going on here. I'll be back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110434
Title:
Merge frr from Debian Unstable for questing
To manage notifications
** Changed in: frr (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110434
Title:
Merge frr from Debian Unstable for questing
To manage notifications about
** Changed in: ubuntu-release-notes
Status: New => In Progress
** Changed in: ubuntu-release-notes
Status: In Progress => Confirmed
** Changed in: postfix (Ubuntu)
Status: Confirmed => Triaged
** Changed in: postfix (Ubuntu)
Status: Triaged => In Progress
** Changed
Added a release notes task because of the (so far) missing TLSRPT
support which we will have to remove, probably.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Andreas Hasenack (ahasen
This migrated.
** Changed in: siege (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110419
Title:
Merge siege from Debian Unstable for questing
Yeah, all main postfix binaries link to it. So this has to be dropped,
or an MIR created. Without an MIR (quick solution), it's delta.
** Changed in: postfix (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Except this debian change might pose a problem:
* enable TLSRPT (+Build-Depends: libtlsrpt0-dev)
Since that is in universe. Let me build this to see where exactly the runtime
dep is added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This can be a sync.
** Changed in: postfix (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110451
Title:
Merge postfix from Debian Unstable for questing
T
This bug was fixed in the package siege - 4.1.6-1
---
siege (4.1.6-1) unstable; urgency=medium
* New upstream version 4.1.6 Closes: #1095389
* configure.ac remove unnecessary macros.
* debian/rules remove custom macros.
* Added remove_unnecessary_macros.diff to remove unnecess
This can be a sync.
** Changed in: siege (Ubuntu)
Status: New => In Progress
** Changed in: siege (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hello Michael, or anyone else affected,
Accepted cloud-init into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/25.1.2-0ubuntu0~22.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
The test plan is correctly testing a fresh install (by doing purge, and
then install from proposed). Please also test the upgrade scenario, for
those systems that have already installed the bad cloud-init.
I'm thinking something like this:
- purge old cloud-init
- install cloud-init from updates (
> Will this fix be in plucky backports or should I wait until quokka?
The plan is for it to be pushed to plucky-updates. The test case is what
I'm a bit concerned about, since I couldn't reproduce it, and you can
reproduce it so easily. I wonder what I'm missing.
In the worst case, we will have t
So comment https://bugs.launchpad.net/maas/+bug/2106671/comments/26
seems to be about https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/2113797, and not this bug here which is focal only, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I pushed a build with the (big) patch from
https://bugzilla.samba.org/show_bug.cgi?id=15608 to this PPA:
https://launchpad.net/~ahasenack/+archive/ubuntu/samba-
segfault-2108981
Once those builds are finished and published, would you be able to test
those packages to see if they fix the segfaul
> what I can tell is that this image seems to work properly except that
> cloud-init is not triggered at all
> (see my bootlog for details) and thus, the whole deployment process is not
> working.
I wonder if this is a separate bug. Is there something in particular
that made you find this bug h
The latest coredump from comment #14 is this:
(gdb) bt
#0 __pthread_kill_implementation (threadid=, signo=6, no_tid=0)
at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (threadid=, signo=6) at
./nptl/pthread_kill.c:89
#2 __GI___pthread_kill (threadid=, signo=signo@entry=6) at
./nptl/pthr
I just built xed on plucky, and I also don't see the crash. How are you
accessing the samba share exactly with gimp and xed, is it via gnome's
builtin samba share access, or do you mount it with mount.cifs before?
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
> I just created an image in gimp (just a blank white box with some gibberish
> text), saved it there. Then
> opened it, edited the image, saved. Crash and corrupted gimp image. Cant copy
> it or do anything.
Is this gimp from another linux machine, or from a windows machine? I
tried these step
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/dovecot/+git/dovecot/+merge/486732
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110444
Title:
Merge dovecot from Debi
** Also affects: landscape-client (Ubuntu Plucky)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087852
Title:
[FFe][SRU] Repository profiles only act on
a) who builds the maas images on images.maas.io, assuming that's where
maas fetches them by default from?
b) Do you have the serial/hash/id of a focal image that works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
The upload for jammy was rejected because the changes file missed the
previous upload in jammy-proposed. It needs to be reuploaded with the
correct -v argument when building the source package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Is this bug also affecting jammy 22.04.4? Could using that point release
be a workaround for now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107458
Title:
Ubuntu 22.04.5 installer crashes on th
Question from the SRU team, from the point of view that there is a
cloud-init upload in focal-unapproved at the moment[1]:
1) Assuming the upload fixes the bug, is it enough to fix the bug to
have it in focal-updates? Or are extra steps needed, like generating new
focal MAAS images?
2) If genera
Hello Denison, or anyone else affected,
Accepted adsys into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.16.3~24.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
Public bug reported:
All of a sudden, my laptop's fan spun up and stayed like that. Checking
the process tree, I see these two processes using a lot of cpu:
5373 andreas 39 19 885984 37112 19604 S 76,4 0,2 27:30.28
/usr/libexec/localsearch-3
18590 andreas 39 19 1392512 110408
Sponsored the second debdiff, with a small changelog modification in the
text and the version:
diff --git a/debian/changelog b/debian/changelog
index c684de50..336101d7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+intel-compute-runtime (24.52.32224.13-0ubuntu4) questing;
I'm sorry, I don't quite understand this bug report.
The title talks about "wrong fs type".
The package the bug is against is nfs-utils.
The partition that is showing an error in your logs seems to be NTFS:
juin 06 13:54:47 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened
to use chkdsk.
Note that focal was not included in LP: #2104165
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106671
Title:
Deployments using a bonded interface on the "MAAS" management network
are broken
To m
Uploaded to noble-unapproved and oracular-unapproved.
** Changed in: ipmitool (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: ipmitool (Ubuntu Oracular)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
What's the status in questing? The launchpad task is set to "new".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110931
Title:
digimend-dkms FTBS in Noble with the linux-6.14-hwe kernel
To manage
> I've upgraded a host to nova (3:25.2.1-0ubuntu2.8) but still got the same
> error: "libvirt.libvirtError:
> Node device not found: no node device with matching name"
Hi Guilherme,
could you please respond to Edward's questions in comment #13? This is
important, as we don't want to risk releas
jammy autopkgtests[1] have cleared!
1. https://ubuntu-archive-team.ubuntu.com/proposed-
migration/jammy/update_excuses.html#wireless-regdb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2094190
Title:
> b) I'm not sure if this implies a verification failure. We need a re-upload
> with a very small change for
> a specific patch that only applies to noble. If that constitutes a failure, I
> can update the verification
> tag.
If the package currently in noble-proposed was found to have a defe
The verification of the Stable Release Update for update-notifier 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 enc
The verification of the Stable Release Update for qtdeclarative-
opensource-src 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 even
The verification of the Stable Release Update for broadcom-sta 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 encoun
Ok, two things.
a) Regarding "we don't currently have released the charms for oracular".
Oracular is a perfectly normal ubuntu release, supported until its EOL
date. Why would you not have charms for oracular? Are you claiming that
the openstack team does not support oracular?
From the openstack
Since the SRU exception was claimed in the description of this bug, I
would also expect the QA Process outlined in that exception to be
followed, and not just the outlined test plan.
Specifically:
"""
When a new version of fwupd or fwupdate is uploaded to -proposed, the following
will be done:
T
The verification of the Stable Release Update for libreoffice 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 encount
It's not clear to me if this can be released.
The wiki page lists this as a step of the qa process:
The appropriate signed packages have been uploaded as well
The current fwupd* packages in, for example, noble, are:
fwupd| 1.9.16-1 | noble |
This is missing the oracular verification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092139
Title:
Rename media device as ipu6-downstream in Noble
To manage notifications about this bug go to:
> * Then run the tests as root (utest/trace-utest), on an s390x machine
(running oracular or noble)
It's not clear from the verification comments that the steps were run on s390x
hardware. Unfortunately the steps where the version is shown do not show the
architecture. For example:
ubuntu@d
The verification of the Stable Release Update for libtraceevent 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 encou
The verification of the Stable Release Update for landscape-client 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 en
The verification of the Stable Release Update for cloud-init 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 encounte
The verification of the Stable Release Update for vision-drivers 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 enco
The verification of the Stable Release Update for gnome-control-center
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 yo
The verification of the Stable Release Update for gnome-control-center
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 yo
The verification of the Stable Release Update for gnome-control-center
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 yo
The verification of the Stable Release Update for libreoffice 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 encount
I would ask to include in the test plan a single run of the charmed-
openstack-tester, just to confirm that the package in proposed has no
regressions. I know you have run this many many many times with the test
packages before this SRU (THANKS!), but I hope a single run is not too
much extra effor
Hello Lucas, or anyone else affected,
Accepted neutron into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:20.5.0-0ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
** Changed in: samba (Ubuntu)
Status: Incomplete => Triaged
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: samba (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
could be https://bugzilla.samba.org/show_bug.cgi?id=15803, which was
fixed via https://bugzilla.samba.org/show_bug.cgi?id=15608
I'll take a closer look next time I work on bugs.
** Bug watch added: Samba Bugzilla #15803
https://bugzilla.samba.org/show_bug.cgi?id=15803
** Bug watch added: Samb
** Also affects: samba (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu Noble)
Status: New => In Progress
** Changed in: samba (Ubuntu Noble)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification b
** Description changed:
[ Impact ]
The samba-tool gpo commands crash because the python code is using a
method that was removed the python version available in noble. This
crash prevents the use and management of group policy objects in a samba
active directory controller.
[ Test
** Description changed:
[ Impact ]
The MOTD policy sets the message of the day text for domain joined linux
computers to which the policy applies. The message can be set with
"samba-tool gpo manage motd set", but due to this bug, it can only be
set once, and not updated again (unless
1 - 100 of 7653 matches
Mail list logo
