© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Hi,
the problem you are having is caused by a bug inside of Wine and is not directly related to Pipelight, which makes it much more difficult. Solving problems inside of Wine is a really time consuming job since it may be everywhere in the 2.5 million lines of code and you need experience with the windows API to be able to trace it down. Since your logs do not show up any direct warnings or errors, you would need to play around with Wines 406 debug channels till you hit the right one and hopefully get a more useful error message, but there is no guarantee for that. The error message is often somewhere in between million of other unrelated messages, so its really like searching for a needle in a haystack.
Although I don't want to prevent you from resolving problems in Wine yourself, I think this may be a waste of time, since it is really hard to find such problems if you did not take part in Wine yet. It also takes a lot of time to get started with all this stuff before you could actually search for the problem. It would be much more time efficient if we could search for the cause on our own.
The only idea which I currently have is to create a debug log with some more Wine debug output, so that we may be able find the error. Close all firefox windows and run the following command:
WINEDEBUG=
open the website of your school and reproduce the error. Now attach the file debug-pipelight.log to the bug report.
Michael