Attached debdiff for adsys 0.14.1 backport to Mantic
** Patch added: "adsys_0.14.1~23.10.debdiff"
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+attachment/5773212/+files/adsys_0.14.1~23.10.debdiff
--
You received this bug notification because you are a member of Desktop
Pack
Attached debdiff for Go 1.22 backport to Mantic
** Patch added: "golang-1.22_1.22.2-2~23.10.debdiff"
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+attachment/5773187/+files/golang-1.22_1.22.2-2~23.10.debdiff
--
You received this bug notification because you are a member of De
** Patch removed: "ubuntu-proxy-manager_0.1~22.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+attachment/5761552/+files/ubuntu-proxy-manager_0.1~22.04.1.debdiff
** Patch added: "ubuntu-proxy-manager_0.1.1~22.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+sour
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2059756
Title:
[SRU] adsys 0.14.1
Status in adsys package in Ubuntu:
Fix Released
Status in golang-1.22 package in Ubuntu:
New
Status
** Patch added: "ubuntu-proxy-manager_0.1~22.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/golang-1.22/+bug/2059756/+attachment/5761552/+files/ubuntu-proxy-manager_0.1~22.04.1.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscr
** Patch added: "golang-1.22_1.22.1-1~ubuntu22.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/golang-1.22/+bug/2059756/+attachment/5761550/+files/golang-1.22_1.22.1-1~ubuntu22.04.1.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is su
** Also affects: golang-1.22 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2059756
Title:
[SRU] adsys 0.14.1
Status in adsys packa
@francisreyes internally, adsys uses /run/adsys/krb5cc/$HOST as the
machine krb5 ticket (which it sources from /var/lib/sss/db/ccache_DOMAIN
in a sssd setup) - so you can mimic what adsys does by exporting
KRB5CCNAME to the path above before running the adsys-gpolist script.
--
You received this
Public bug reported:
This is a regression from when we added support for multiple AD backends
(see https://github.com/ubuntu/adsys/pull/467)
Previously adsys would use the first domain from `sssd.conf` and
potentially override it if `ad_domain` is explicitly set for the domain,
see:
https://githu
** Changed in: adsys (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2051363
Title:
Cannot perform certificate auto-enroll without NDES insta
Public bug reported:
NDES role should not be mandatory in order to perform certificate auto-
enrollment with adsys.
Samba/ADSys is able to take advantage of the NDES endpoint to install
the root certificate chain, but is also able to infer the certificate
information from LDAP.
Due to a bug in t
Hey, thanks for your bug report.
Given that smbclient fails in a similar manner, this suggests that the
issue is not limited to adsys but other programs interacting with AD
too. Unfortunately NT_STATUS_INVALID_PARAMETER is a very common catch-
all error and the root cause could be very environment
Public bug reported:
The nfs-common package is required if NFS shares are to be mounted on
the client. Unlike cifs-utils, this package is not installed by default
on Ubuntu Desktop. Given that we declare the former as a dependency we
should do the same with nfs-common.
** Affects: adsys (Ubuntu)
This looks alright to me, GPOs are fetched and applied. Are you
experiencing any other issues? If not I'll move forward with the fix
from the PPA.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net
Hey,
Unfortunately with Samba logs there's a lot of noise to filter out. I
compared one of your runs with my (successful) run and I noticed
something interesting.
We do a LDAP search to get the list of GPOs using the domain controller
exposed by SSSD via D-Bus. For you the DC is autoselected as
"
Hi,
I've prepared a version of adsys with debug logs enabled for
libsmbclient, this way we can pinpoint exactly what causes the
libsmbclient call inside adsys to fail.
You can install the package using the following commands:
sudo add-apt-repository ppa:gabuscus/adsys-smbclient-debug
sudo apt up
Interesting - so we are able to get the list of GPOs, _and_ smbclient is
able to print the contents of the GPT.INI file, but adsys still fails.
At this point I'm out of ideas, I would suggest the following:
- upgrade the system to make sure you are running the latest available versions
of adsys (
Thanks for getting back. Noticing a couple of things about your pasted output:
- Did you run the first set of commands in a root session? This is necessary
because the user needs to be able to read the
`/var/run/adsys/krb5cc/$(hostname)` file. You can confirm this by trying to
`cat` the file - i
Thanks for reaching back. Unfortunately we haven't been able to
reproduce this issue and we suspect it's somehow related to the Windows
environment or libsmbclient itself.
Could you try the following?
In a root console, execute the following:
export KRB5CCNAME=/var/run/adsys/krb5cc/$(hostname)
a
Hello,
The issues described for 22.10 and 23.04 were fixed by
https://github.com/ubuntu/adsys/pull/699 and are available since adsys
v0.12.0. However this is only available in Mantic which is not yet
released.
For the "invalid argument" issue encountered in 22.04, could you confirm
the version of
** Description changed:
Ubuntu Proxy Manager is a D-Bus mediated service that allows for
managing system proxy settings via multiple backends (APT, environment
variables and GSettings).
We request a FFe for this new source package (ubuntu-proxy-manager). As
it's a new source package t
Public bug reported:
Ubuntu Proxy Manager is a D-Bus mediated service that allows for
managing system proxy settings via multiple backends (APT, environment
variables and GSettings).
We request a FFe for this new source package (ubuntu-proxy-manager). As
it's a new source package the risk of it b
Hey Timo,
Yes, as we have LP bugs for everything else that went in adsys as well:
- https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982349
- https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982348
- https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982347
- https://bugs.launchpad.ne
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://
** Description changed:
[Impact]
When logging in (either via login or ssh) to an AD account using
different case combinations, adsysd uses the specified account name
instead of the lowercase one reported by getent/whoami to apply the
GPOs. I believe this comes from the pam_get_item ca
** Description changed:
As part of our entreprise desktop offering, there is the request to
backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS.
ADSys is our Active Directory GPO integration. It’s available starting
Ubuntu 21.04.
adsys-windows contains Windows-spec
** Description changed:
[Impact]
Adsys cannot currently manage GSettings power management keys, such as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/
** Description changed:
As part of our entreprise desktop offering, there is the request to
backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS.
ADSys is our Active Directory GPO integration. It’s available starting
Ubuntu 21.04.
adsys-windows contains Windows-spec
Public bug reported:
As part of our entreprise desktop offering, there is the request to
backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS.
ADSys is our Active Directory GPO integration. It’s available starting
Ubuntu 21.04.
adsys-windows contains Windows-specific files includ
Public bug reported:
[Impact]
Adsys cannot currently manage GSettings power management keys, such as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/settings-daemon/plu
Public bug reported:
[Impact]
Before applying policies, adsys checks for the existence of an Ubuntu
Pro subscription. If not found, all keys with the exception of dconf
keys are filtered, as they require Ubuntu Pro.
Annotate the generated ADMX/ADML files with this information.
[Test Plan]
* Op
Public bug reported:
[Impact]
When logging in (either via login or ssh) to an AD account using
different case combinations, adsysd uses the specified account name
instead of the lowercase one reported by getent/whoami to apply the
GPOs. I believe this comes from the pam_get_item call here:
https:
Public bug reported:
[Impact]
The Default Domain Policy for Computers has a bunch of
SystemCertificates keys with no data which adsys fails to parse. Here
are some examples:
Software\Policies\Microsoft\SystemCertificates\ACRS\Certificates
Software\Policies\Microsoft\SystemCertificates\ACRS\CRLs
Public bug reported:
[Impact]
In addition to empty data, some Microsoft policy entries happen to have
empty values as well. See the following entry:
// [key;value;type;size;data]
: 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f.
0010: 7400 7700 6100 7200 6500 5c00 5000 6f00
Public bug reported:
[Impact]
Policies with unsupported types are currently unable to be parsed. Even
if Ubuntu doesn't support these types we should still be able to parse
the Microsoft ones - otherwise we are unable to apply any of the GPOs.
This is a common occurence on Microsoft's policies l
** Description changed:
[Impact]
ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed
folders. adsysctl expects the folders to be title cased (e.g. Machine),
but they are uppercase (e.g. MACHINE). This prevents any GPOs from being
applied.
This is a common occure
Public bug reported:
[Impact]
ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed
folders. adsysctl expects the folders to be title cased (e.g. Machine),
but they are uppercase (e.g. MACHINE). This prevents any GPOs from being
applied.
This is a common occurence with GPOs creat
43 matches
Mail list logo
