Thanks for your report. This looks like a request for a Stable Release
Updates (SRU) rather than an actual bug report. Since we use this bug
tracker to track bugs in Ubuntu, I'm marking this bug as Invalid.
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
You received this bug
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=93708
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu
Thank you for your report.
This looks like a local configuration problem, rather than a bug in Ubuntu.
You can find pointers to get help for this sort of
** Bug watch added: MySQL Bug System #92387
http://bugs.mysql.com/bug.php?id=92387
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=92387
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server/Client
** Changed in: zsh (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to apache2 in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
Hello,
This website is used to report and track problems in the Ubuntu
operating system. From what I understand from your report you've got
banned from an online service or game, which is unlikely to be related
to Ubuntu. For this reason I'm marking this report as Invalid.
If you believe you
Thanks Andreas for this report. Apparently the same problem happens in
Eoan too. The minimal steps to reproduce are:
1. start a fresh LXD container
2. apt update
3. apt install apache2 libaprutil1-dbd-mysql
4. a2enmod authn_dbd (also enables the dbd module)
5. systemctl restart apache2
6. curl
** Also affects: autofs (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968675
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to openldap in Ubuntu.
Matching
** Bug watch added: Samba Bugzilla #14363
https://bugzilla.samba.org/show_bug.cgi?id=14363
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=14363
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Bug watch added: Red Hat Bugzilla #1836427
https://bugzilla.redhat.com/show_bug.cgi?id=1836427
** Also affects: samba via
https://bugzilla.redhat.com/show_bug.cgi?id=1836427
Importance: Unknown
Status: Unknown
** No longer affects: samba
** Bug watch added: Samba Bugzilla
Hi Hassen,
The patches had to be retrieved to patch mysql < 5.7.29, but since the
upstream version containing the fix got packaged in Ubuntu there is no
need to do so anymore.
Coming to your comment, you claim that the upstream patch didn't work
for your. This could mean two things:
1. The
I verified that apache2 builds fine against lua5.3 and filed [1] in
Debian. This is similar to [2] and the apache2 maintainers promptly
bumped the build-dep back then.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979501
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820243
** Bug
Hello and thanks for you follow up! Happy to hear that you found the
root cause of the issue. As this was a local configuration problem
rather than a bug in Ubuntu I'm setting the status of this bug to
Invalid. Should you believe there is actually a bug here please comment
back with your findings
I think "Step I" of this bug has been reached: we have only lua5.3 in
main.
Eventually we'll get to "Step II" and move to lua5.4, which is supported
by apache2 >=2.4.47 [1], but there's no MIR for lua5.4 at the moment
(LP: #1909665 lua5.4 MIR is a Wontfix), so no action is required at the
moment.
** Project changed: mysql-server => ruby-mysql2
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1942476
Title:
** Summary changed:
- smbclient cannot connect anonymously in Kerberos context (freeipa)
+ [SRU] smbclient cannot connect anonymously in Kerberos context (freeipa)
** Also affects: samba (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu Hirsute)
** Bug watch added: Samba Bugzilla #14344
https://bugzilla.samba.org/show_bug.cgi?id=14344
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=14344
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Hello Christoph,
`systemctl reload apache2` is indeed the same of `apache2ctl graceful`:
ExecReload=/usr/sbin/apachectl graceful
(apachectl is a symlink to apache2ctl). This said, I see the issue you
are reporting: there is effectively no easy way to do a graceful reload
of apache2 now. I think
The upload to the devel release targeted impish, but actually landed in
jammy. Added an Impish task for the SRU.
** Also affects: samba (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support
(unassigned) => Paride Legovini (paride)
** Changed in: samba (Ubuntu Focal)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: samba (Ubuntu Hirsute)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=105288
Importance: Unknown
Status: Unknown
** Tags added: regression-update
** Changed in: mysql-8.0 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of
Hi Marc, thanks for the heads-up. That's right we don't need to bump the
Jammy version anymore. We can mark this as Fix Released.
** Changed in: samba (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server/Client
Hello Mark,
I think you filed this bug report against the wrong package: this is
Apache2, the web server. I'm marking this but report as Invalid. Feel
free to file a new bug report against the correct package, however my
suggestion is to go through this first:
That's great to hear, even if of course it would be even nicer to
understand what happened. As we never fully recognized this as a bug,
and the problem isn't reproducible, I'm marking this report as Invalid.
Feel free to comment back and change the bug status back to New (or file
a new bug report)
Thanks, I added a new Apache2 project task to this bug, tracking the
upstream bug you filed, so we'll get notified of changes there.
** Also affects: apache2 via
https://bz.apache.org/bugzilla/show_bug.cgi?id=65737
Importance: Unknown
Status: Unknown
--
You received this bug
** Also affects: apr-util (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
Hi Antonios and thanks for this bug report. I'm marking this report as
Fix Released as according to the version numbers this bug is fixed in
Ubuntu 22.04 LTS (shipping apache2 2.4.52). I am however adding tasks
for the stable releases, as by looking a the patch you pointed to
(thanks!) I think
** Also affects: apache2 (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to apache2 in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
This is fixed in Focal. I doubt mod_brotli support will be enabled in
Bionic, as the use case is not compelling enough. The SRU process [1]
has a "we sometimes want to introduce new features" case, but I don't
think mod_brotli support satisfies its requirements.
I'm marking the Bionic task as
This has been likely fixed by [1], thanks Andreas for the pointer.
According to d/changelog [1] was first released in 4.6-2ubuntu1 (Eoan),
so I'm marking this as Fix Released.
[1]
https://git.launchpad.net/ubuntu/+source/squid/commit/?id=665afbf87f5d32d587445ff54de41ad79de2efde
** Changed in:
Hi Dimitri, I had a look at what we have on the supported releases and
I'm going to update the tasks accordingly.
The patch is not trivial and, as the upstream bug also notes, the bug
requires NetApp to be reproduced (which makes testing/verification
difficult), so we don't have the best premises
Looks like the culprit here is python3, as doing
apt install python3:i386
causes the removal of several important packages. This in a Jammy LXD
container and after doing `dpkg --add-architecture i386`.
The python3 package is marked Multi-Arch: allowed, so I would expect the
i386 package to be
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to samba in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
Hi again James and thanks for this bug report. I think you are right:
this bug isn't fixed upstream in the samba version shipped in Jammy, and
the Ubuntu patches are not applied in the Jammy package.
More specifically the patches are still present in the Ubuntu source
package:
Hello and thanks for this bug report. I did not try to setup a
reproducer for this, but the bug has been triaged and fixed upstream, so
there's no doubt it's valid.
According to the upstream CHANGES file the fix will be released in
apache2 2.4.55, currently not in Lunar and not in Debian, so
** Bug watch added: bz.apache.org/bugzilla/ #66302
https://bz.apache.org/bugzilla/show_bug.cgi?id=66302
** Also affects: apache2 via
https://bz.apache.org/bugzilla/show_bug.cgi?id=66302
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Hello and thanks for this bug report and for the reproducer. According
to the upstream release notes [1] this bug is fixed in apache2 2.4.55,
which is currently in Debian unstable but not in Lunar, so step 1 for
fixing this is merging apache2 from Debian to Ubuntu. From what I can
tell from the
Hello, looks like you are trying to install a package which is not part
of Ubuntu (ea-apache24-tools). We can't control or offer support for
packages which are not in Ubuntu, please contact the distributor of ea-
apache24-tools or the Ubuntu community support channels:
Thanks Andy for letting us know and glad to hear the problem has been
fixed at some point. I'll mark this bug report Fix Released.
** Changed in: samba (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server/Client
** Changed in: samba (Ubuntu)
Status: New => Triaged
** Also affects: samba (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: samba (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: samba (Ubuntu Jammy)
Importance: Undecided
40 matches
Mail list logo
