error message when using magister in ubuntu-firefox

Bug #1249569 reported by Teunis Brand
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Pipelight
Triaged
Medium
Unassigned

Bug Description

Hello,

Thanks for pipelight! It enables me to use Magister (Dutch online school software) on Ubuntu.

But I get this error message if I use the 'ELO' function from Magister:

Details:
- ManagedRuntimeError
- System.Collections.Generic.KeyNotFoundException: [Arg_KeyNotFound]

Arguments:

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.00&File=mscorlib.dll&Key=Arg_KeyNotFound

   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

   at System.Windows.ResourceManagerWrapper.GetResourceForUri(Uri xamlUri, Type componentType)
- 4004

Distro: Ubuntu 12.04 LTS
Graphic card: nVidia GT218-ION
URL: https://jfsg.swp.nl/5.6.15.1/magister.aspx (but you have to login before the error message comes)
Wine: version which comes with pipelight
Silverlight: 5.1.20513.0
Console output: see attachment (start firefox, go to url, login, go to 'ELO', error message, exit firefox).

I hope I give enough information. It will be great if this problem can be solved so now I can only use the function 'ELO' on a windows machine.

Revision history for this message
Teunis Brand (teunisbrand) wrote :
Changed in pipelight:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Sebastian Lackner (slackner) wrote :

Hi,

thanks for the bug report. We've already heard of this problem from other people, but haven't found out how to fix it yet.

.

Two things which could be related to the problem (but didn't help to fix it):

* there is an error message:
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

in some cases (for example for RavenDB) it helps to install "winbind" to fix it. Just run:
sudo apt-get update && sudo apt-get install winbind

But some other people reported that it doesn't help for Magister.

* such errors are sometimes also related to the user agent string. Try to install a user-agent switcher if you haven't done this yet (see: https://answers.launchpad.net/pipelight/+faq/2351) and try to select different configurations.

.

The best way to find the error would be the possibility to do some tests on our own, but we haven't found any way yet to access Magister without a regular username/password. Do you know a way or where to get test accounts?

Sebastian

Revision history for this message
Teunis Brand (teunisbrand) wrote :

Hi,

Thanks for your reaction.

I've installed winbind. That fixes the ntlm_auth error.
But it generates a new one:

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so

After installing 'gnome-keyring-pkcs11.so' I tried again Magister. The same problem occurs with the 'ELO' function.

Then I tried different user agent strings, but that did not fix anything.

I've send an email to school for a test account. I hope they will agree. If so, than I will give it you but not public.

Teunis

Revision history for this message
Sebastian Lackner (slackner) wrote :

Hi,

I hope they'll agree, as this would be the easiest way to track down the error. Everything else is much more complicated, as it involves trying different changes / recompiling wine and stuff like that - unless you're very experienced with that we would have to guide you through all the steps. If you get an test account, just email me account data to my email adress: <email address hidden>

If this is not possible, it would also help to find a public available site with exactly the same error, but so far I don't know any yet.

Sebastian

Revision history for this message
Teunis Brand (teunisbrand) wrote :

Hi,

School did not yet reply my email about the test account till now. I resent my email.

There are different useraccounts for Magister.

- Parents: they have only some read functions to follow the school results of there kids.
- kids: they have an account for reading en writing to do homework with Magister.
- teacher: to write the results and new homework in Magister.

We have two accounts, for parent and student. Both give the same bug as far as I know. So I suggest to start with a parent testaccount.

Last week I did some tests with Magister on Linux and Windows. I found out some more differences and I got a new error message in Magister on Linux, it may helps you for debugging:

System.TimeoutException: [HttpRequestTimedOutWithoutDetail]
Arguments: https://jfsg.swp.nl/5.6.15.1/WCFServices/VandaagService.svc
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.00&File=System.ServiceModel.dll&Key=HttpRequestTimedOutWithoutDetail ---> System.Net.WebException
   at System.Net.Browser.ClientHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
   --- End of inner exception stack trace ---
   at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)
   at DynamicSoapProxy.ServiceClientBase`1.ClientChannelBase.OnAsyncCallback[TReturnType](IAsyncResult asyncResult)

Your offer to let me do the recompiling and tests: 20 years ago I compiled my first Linux kernel, but last fifteen years I did not do anything with Linux. So I have to learn again how it works.

Teunis

description: updated
Revision history for this message
Teunis Brand (teunisbrand) wrote :

Hi,

This week school send me an answer.
They are not able to give a test account.

I'd like to run Magister full on Linux, so what are now the possibilities?

If possible I would like to compile the source code and perform the required tests, but therefore I need instructions.

Can you give more insight in this stuff?

Teunis

Revision history for this message
Michael Müller (mqchael) wrote :

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=+ole,+urlmon,+url firefox &> debug-pipelight.log

open the website of your school and reproduce the error. Now attach the file debug-pipelight.log to the bug report.

Michael

Revision history for this message
Teunis Brand (teunisbrand) wrote :

Hi,

Thanks for your explanation.

I run the command you send me, in the attachment you 'll find the result.
I started Magister. After the error message I closed Firefox.
I made some screenshots from Magister on Firefox / Ubuntu and Windows explorer so you can see the differences. I 'll post the attachment also.
I 'll do the same thing for another error message.

Good luck to find the needle...

Teunis

Revision history for this message
Teunis Brand (teunisbrand) wrote :

screenshots from error 1

Revision history for this message
Teunis Brand (teunisbrand) wrote :

Hi,

Today I run automatic updates for Ubuntu.
After that, Magister did not work anymore.
The website is started and after that it hangs.
The login window never appears.

You can try ' jfsg.swp.nl '.

I tried everything, but nothing helped.
- reinstall pipelight.
- different user agents.

What can be the problem? Do you have any idea how to solve it?

Teunis

Revision history for this message
Sebastian Lackner (slackner) wrote :

Hi,

please try to update again, there was an issue with our wine-compholio builds and the published version didn't contain all necessary patches. We have fixed that in the meantime.

If it still occurs afterwards please report back.

Sebastian

Revision history for this message
Teunis Brand (teunisbrand) wrote :

Hi,

Thanks for your quick reaction.

Sorry, but it still occurs.

What I did a few moments ago:
- sudo apt-add-repository ppa:ehoover/compholio
- sudo apt-add-repository ppa:mqchael/pipelight
- sudo apt-get update
- sudo apt-get install pipelight-multi
- sudo pipelight-plugin --enable silverlight
- rm -rf ~/.wine-pipelight/

After that I started Firefox and opened the Magister website, but it did not work.

Teunis

Revision history for this message
Sebastian Lackner (slackner) wrote :

Hi,

I've just verified that everything still works as expected. Please check especially two things:

1) ensure that you've the right version of wine-compholio installed. pipelight was not updated during the last time. You can find the version for example with:

dpkg --list | grep "\(wine-.*-installer\|wine-compholio\|pipelight\)" | sed 's/ \+ /\t/g' | cut -f2-3;

The current version is 1.7.8-1, whereas the previous version 1.7.8 (without "-1") is broken. To install updates you have to run:

sudo apt-get update
sudo apt-get upgrade

(all the other steps are not necessary when everything is already installed)

2) Check the diagnostic page http://fds-team.de/pipelight . It might be possible that for example the user-agent switcher settings was somehow lost and you have to select the windows Firefox version again. Copy the output of the diagnostic page if you don't see immediately an error there.

Sebastian

Revision history for this message
Teunis Brand (teunisbrand) wrote :

Hi,

Thanks a lot.
It works again!
The problem was indeed version 1.7.8 without '-1'.
After running 'sudo apt-get upgrade' I have running version 1.7.8-1.
Magister runs again.

Teunis

Revision history for this message
Teunis Brand (teunisbrand) wrote :

Hi,

Today I run the debug command for the other error on Magister.
In the attachment you 'll find the output.

It's the error message I started the bug report with:

Details:
- ManagedRuntimeError
- System.Collections.Generic.KeyNotFoundException: [Arg_KeyNotFound]

Arguments:

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.00&File=mscorlib.dll&Key=Arg_KeyNotFound

   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

   at System.Windows.ResourceManagerWrapper.GetResourceForUri(Uri xamlUri, Type componentType)
- 4004

Teunis

Revision history for this message
Teunis Brand (teunisbrand) wrote :

And I did the same with Chromium.

Revision history for this message
Erich E. Hoover (ehoover) wrote :

Teunis,

Would you mind collecting a log with a different set of information?:
WINEDEBUG=+shell,+urlmon,+url,+mshtml firefox &> debug-pipelight.log

We suspect the problem is parsing a semicolon in the URL (since these are not allowed), but we're not finding any problems with the obvious routines in your logs. Thanks!

Revision history for this message
Teunis Brand (teunisbrand) wrote :

error1

Revision history for this message
Teunis Brand (teunisbrand) wrote :

error2

Hi Erich,

Thank you for searching for the bug.
I've posted the new log files.
If there's more I can do, let me know.

Teunis

Revision history for this message
kingcharles1666 (kingcharles1666) wrote :

Hi Erich,

My kids both have the same issue, I have requested their school for a dummy account.
Will report back as soon as I receive a response
Thanks for your support.

Mico

Revision history for this message
Erich E. Hoover (ehoover) wrote :

Thanks guys, we are working on this off and on - but without a dummy account it's very difficult for us to do testing. If Mico actually manages to get us one that will prove very useful.

Revision history for this message
kingcharles1666 (kingcharles1666) wrote :

I have received a reaction from the school:

Dutch:
Een dummy leerlingaccount is niet zo eenvoudig. Deze “leerling” zal ook in een studie en klas moeten zitten om iets nuttigs met de test te kunnen doen. Dit verstoort het lopende systeem.
Er is echter ook goed nieuws. De makers van Magister beginnen in april de eerste (betatest) scholen te voorzien van een geheel herziene versie van Magister6 in html5. Hierdoor zullen de huidige problemen met betrekking tot Silverlight achterhaald zijn. Vanaf augustus –planning- kunnen alle scholen over magister 6 beschikken.

Translated:
No dummy account, to complicated as they need to create a dummy student in their systems which they don't want.
Good news: Magister will roll out an HTML5 based version after August this year (according to the current plan).

Conclusion:
With HTML5 coming, trying to solve this issue seems less urgent.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.