Comment 3 for bug 261587
Revision history for this message
| bengtan (bengtan) wrote Re: Failed to install | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
I agree with your observations. The problem probably exists in the PP profile code, and path.inc is merely the file that triggers it.
I know that during the early installation stages, code mustn't attempt to access the database because the database hasn't been setup yet. The referenced line in path.inc is doing just that - accessing the database in an attempt to see if any path aliases have been set. Unfortunately, I can't quite see why PP would indirectly cause a path lookup - not at such an early install stage.
Let me investigate and see what I can find.