default page, ubuntu_logo.png is missing

Confirmed issue as described. CLI test case for verifying issue:

$ sudo apt-get install -y apache2
$ sudo apt-get install -y linkchecker
$ linkchecker --check-extern /var/www/html/index.html
...
URL `/icons/ubuntu-logo.png'
Name `Ubuntu Logo'
Parent URL file:///var/www/html/index.html, line 196, col 9
Real URL file:///icons/ubuntu-logo.png
Check time 0.001 seconds
Result Error: URLError: <urlopen error [Errno 2] No such file or directory: '/icons/ubuntu-logo.png'>

URL `/manual'
Name `manual'
Parent URL file:///var/www/html/index.html, line 258, col 40
Real URL file:///manual
Check time 0.003 seconds
Result Error: URLError: <urlopen error [Errno 2] No such file or directory: '/manual'>
 1 thread active, 0 links queued, 4 links in 4 URLs checked, runtime 1 seconds

I've reproduced this on both bionic and impish. Since this is more a cosmetic issue with an example web page, I am doubtful the impact significant enough to be valid for SRU (feel free to make a case otherwise though). So, I'll target to ubuntu-devel only at this time.

Hello,

This issue should only happen when opening /var/www/html/index.html directly. The Ubuntu logo should appear when accessing the file through the webserver: http://127.0.0.1

The image shows up properly when accessing it this way because /usr/share/apache2 is the location apache2 considers to be its filesystem base. Therefore a call to /icons/ubuntu-logo.png is actually a call to /usr/share/apache2/icons/ubuntu-logo.png.

I can confirm this is still an issue with a fresh install of Ubuntu 23.10 over http://localhost

The file /usr/share/apache2/icons/ubuntu-logo.png just does not exist

Thanks Marc, I am also able to reproduce.

Reproduction steps:

$ lxc launch images:ubuntu/23.10/desktop mantic-desktop --vm -c limits.cpu=4 -c limits.memory=4GiB --console=vga

In VM:
$ sudo apt update -y
$ sudo snap install firefox

In firefox inside the VM:
type in "localhost"

Top left of the welcome page shows "Ubuntu Logo" instead of displaying the logo.

Tried it on Jammy, and I see the logo, so setting to invalid.

I reproduced it on Mantic so far.

Lunar is fine. I'll submit an MP for Mantic/Noble soon.

I'm adding an autopkgtest in Noble so hopefully this gets caught in future merges.

This bug was fixed in the package apache2 - 2.4.57-2ubuntu3

---------------
apache2 (2.4.57-2ubuntu3) noble; urgency=medium

  * d/icons/ubuntu-logo.png: add Ubuntu image for welcome page (LP: #1947459).
  * d/t/check-ubuntu-branding: add check for ubuntu branding.

 -- Mitchell Dzurick <email address hidden> Mon, 13 Nov 2023 10:49:48 -0700

Just a quick comment about the test case: you don't need to deploy a "heavy" ubuntu desktop VM and use the browser from the VM. Use a lxd, and access it from your host with the browser pointing at the IP of the lxd container.

I'm going to submit another MP for Mantic soon since Mantic got updated before my change got in.

Also possible to visit https://packages.ubuntu.com/mantic/all/apache2-data/filelist and check for the presence of ubuntu-logo.png.

Hello psl, or anyone else affected,

Accepted apache2 into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apache2/2.4.57-2ubuntu2.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted apache2 (2.4.57-2ubuntu2.2) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

backuppc/4.4.0-8 (s390x)
libapache2-mod-python/3.5.0+git20211031.e6458ec-1build1 (armhf)
libsoup3/3.4.2-4 (arm64)
mediawiki/1:1.39.4-2 (armhf)
mediawiki-extension-codemirror/4.0.0~git20221204.b897975-1 (armhf)
mediawiki-skin-greystuff/1.2.5~git20220922.60bda8c-2 (armhf)
mod-wsgi/4.9.4-1build1 (armhf)
passenger/6.0.17+ds-1build1 (armhf)
piuparts/1.1.7 (amd64, arm64, ppc64el, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/mantic/update_excuses.html#apache2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

I'll look into helping the autopkgtest regressions this week. It shouldn't be caused by the change from this bug, but It'll be needed to get the package through.

I've retriggered the 7 failed tests in case they are just flaky.

The four failures for piuparts may be something else.

The 4 piuparts errors have cleared.

The remaining 3 failures are all on armhf, and while the logs aren't detailed I get the impression the test client isn't connecting with the apache2 server for performing the tests. So it seems like some irregularity in how apache2 runs on armhf.

Other than disabling the test or just keep retriggering, I think the right next action would be to enable more logging output such as capturing the access.log, error.log, journalctl, and the apache2 service status. Hopefully that captures some further info that might clue us in on what's going on.

If someone has access to armhf vm's similar to the autopkgtest environment, it might be worth trying out installing these components and see if apache2 works.

Bryce, I agree on the not connecting to the server idea. 2 of the tests (mod-wsgi && libapache2-mod-python) have the very similar failures along the lines of

808s autopkgtest [00:07:38]: test nodejs: - - - - - - - - - - stderr - - - - - - - - - -
808s --2024-02-02 00:07:33-- http://localhost/testnodejs/
808s Resolving localhost (localhost)... 127.0.0.1
808s Connecting to localhost (localhost)|127.0.0.1|:80... connected.
808s HTTP request sent, awaiting response... 404 Not Found
808s 2024-02-02 00:07:33 ERROR 404: Not Found.

I don't have a vm similar to the environment right now but I could trigger autopkgtest against my private PPA which is a little slow but better than nothing.

We are talking about re-adding a missing image for mantic, which is present on both lunar and noble. Whatever tests are failing are obviously not as a result of re-adding that image and should not hold anything up.

Whatever issues you are seeing now belong in a new bug report.

That is true, I made a new bug to track the armhf failures - https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2052322

The current mantic-proposed upload through this bug is blocking bug 1927742.

We should squash this change with 1927742 for the Mantic upload.

Working on the squash now. I'll also see about resolving the migration issues, typically they've been flaky issues (hardware network or service timing).

Bryce, Mitchell and I agreed to upload the fix for bug 1927742 on top of the fix for bug 1947459 into mantic-proposed, combining these into a single SRU. This means that the SRU verification state for bug 1947459 in Mantic will be reset and needs to be performed again.

No need for block-proposed-mantic now that these will be combined.

Hello psl, or anyone else affected,

Accepted apache2 into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apache2/2.4.57-2ubuntu2.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Now that there are two sets of fixes and verifications flying round, please make sure that you verify 2.4.57-2ubuntu2.3 from the beginning and confirm that this was the version tested in your SRU verification report. Thanks!

All autopkgtests for the newly accepted apache2 (2.4.57-2ubuntu2.2) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

libapache2-mod-python/3.5.0+git20211031.e6458ec-1build1 (armhf)
mod-wsgi/4.9.4-1build1 (armhf)
passenger/6.0.17+ds-1build1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/mantic/update_excuses.html#apache2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted apache2 (2.4.57-2ubuntu2.3) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

libapache2-mod-python/3.5.0+git20211031.e6458ec-1build1 (armhf)
mod-wsgi/4.9.4-1build1 (armhf)
passenger/6.0.17+ds-1build1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/mantic/update_excuses.html#apache2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Hello, I tested version 2.4.57-2ubuntu2.3 from proposed.

1. Recreating the issue
$ lxc launch ubuntu:mantic mantic-apache2

2. update the archives, and install apache2
$ lxc exec mantic-apache2 -- sudo apt update -y
$ lxc exec mantic-apache2 -- sudo apt install -y apache2

3. Get the ip address
$ lxc exec mantic-apache2 -- hostname -I | cut -d' ' -f1

4. Open up any browser and put the IP address from step 3.

5. Enable proposed and update
$ lxc shell mantic-apache2
# cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF
# apt update -y

6. pin proposed higher than other archives (only do this on a test system)
# cat <<EOF >/etc/apt/preferences.d/proposed-updates
Package: *
Pin: release a=$(lsb_release -cs)-proposed
Pin-Priority: 501
EOF

7. Update apache2
# apt install -y apache2=2.4.57-2ubuntu2.3
# dpkg -s apache2 | grep Version:
Version: 2.4.57-2ubuntu2.3

8. Try logging in to IP from step 3
Confirmed logo is visible.

This bug was fixed in the package apache2 - 2.4.57-2ubuntu2.3

---------------
apache2 (2.4.57-2ubuntu2.3) mantic; urgency=medium

  * d/c/m/setenvif.conf, d/p/fix-dolphin-to-delete-webdav-dirs.patch: Add
    dolphin and Konqueror/5 careful redirection so that directories can be
    deleted via webdav.
    (LP: #1927742)

apache2 (2.4.57-2ubuntu2.2) mantic; urgency=medium

  * d/icons/ubuntu-logo.png: add Ubuntu image for welcome page (LP: #1947459).

 -- Bryce Harrington <email address hidden> Wed, 24 Jan 2024 22:51:25 -0800

The verification of the Stable Release Update for apache2 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.