Thanks for the reply. I've not yet sorted out the problem as it happens.
I'll take your advice and ask on another forum. I am a bit puzzled
because my steps to reproduce are very simple - apparently just a clean
install - but I dare say something is misconfigured somewhere somehow.
--
You
> Given you are suggesting a Support site, does that mean that I've just
> done something silly and it's not a bug? (I can believe that.)
Hi apsaras, hopefully by now you've sorted out a solution to your issue,
but just to follow up, the link Chris pointed to has an excellent run
down of what
Thanks for the reply. I ran the apport-collect command, though it said
that no new information was going to be added.
Given you are suggesting a Support site, does that mean that I've just
done something silly and it's not a bug? (I can believe that.)
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
The apache2 error log did not have more information:
/etc# ls -l /var/log/apache2/
total 0
-rw-r- 1 root adm 0 Dec 4 10:48 access.log
-rw-r- 1 root adm 0 Dec 4 10:48 error.log
-rw-r- 1 root adm 0 Dec 4 10:48 other_vhosts_access.log
The config file that is tripping it up is