dedicated server module not working on windows
Bug #1090433 reported by
Nasenbaer
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| widelands |
Fix Released
|
Undecided
|
Tino | ||
Bug Description
After anouncing the shutdown of my dedicated server _aD told me, that he was unable to start a dedicated server on Windows. The problem seems to be, that Widelands (in dedicated mode) does not even try to connect to the metaserver. In normal (gui) mode connection to the metaserver works as it should.
I have not been able to take a closer look at this bug, as I have no Windows installation available at the moment.
Related branches
lp:~tino79/widelands/fix-bug-1090433
(Merged)
Revision history for this message
| _aD (ad-simplypeachy) wrote | #1 |
| Changed in widelands: | |
| assignee: | nobody → Tino (tino79) |
| status: | Confirmed → Fix Committed |
| Changed in widelands: | |
| milestone: | none → build18-rc1 |
Revision history for this message
| SirVer (sirver) wrote | #2 |
| Changed in widelands: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Just to confirm that Wireshark shows no Internet activity from Widelands at all during attempts to start a dedicated server. The config the server uses works in the Widelands client - it has the user name and password for the metaserver saved and automatically logs in. The server does read the config file (confirmed by using Process Monitor to watch file I/O).
The error report is:
Caught exception (of type '7warning') in outermost handler!
The exception said: Widelands has not been able to connect to the metaserver.
This should not happen. Please file a bug report on version build-17(Release).
and remember to specify your operating system.
This was tried on Windows 7 x64 with build 6440 using --registered=false and without.