FS#33260 - [springlobby] 0.157 GUI freezes after very short amount of time

Attached to Project: Community Packages
Opened by Cameron (Rhubarb) - Tuesday, 01 January 2013, 04:50 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 03 January 2013, 12:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After a second or less (depending on host computer speed) the springlobby GUI freezes, nothing can be clicked on in the GUI.
Sometimes the GUI will work, up until you try to select a singleplayer map xor singleplayer mod.

Additional info:
* package version: 0.157
* config and/or log files etc.

Downgrading to springlobby 0.147-2 fixes the problem.
Removing old springlobby configuration files does not fix this problem.
Installing packages: fluidsynth dumb, does not fix this problem

Tested on 2 x86-64 computers running gnome3.6
Untested on 32bit x86 computers.

Steps to reproduce:
Run springlobby, wait a second or less after start up.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 03 January 2013, 12:11 GMT
Reason for closing:  Upstream
Comment by Cameron (Rhubarb) - Wednesday, 02 January 2013, 12:29 GMT
I'm not sure if this is an upstream issue or not.

See http://projects.springlobby.info/issues/1700 (springlobby 0.157 fails to build on Linux)
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 02 January 2013, 12:38 GMT
Quite likely an upstream issue. Report it and link it here.
Comment by Cameron (Rhubarb) - Wednesday, 02 January 2013, 13:04 GMT
Ignore my attached springlobby_error.log, as the errors also appear in older versions of springlobby, and are known (and harmless) upstream
- See http://projects.springlobby.info/issues/1658

I'll check bug #1700 regularly to see if there's been a fix upstream, and will report here.
Thanks Svenstaro :)
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 03 January 2013, 12:11 GMT
You should probably report a new upstream bug report for this because the bug number you mentioned has nothing to do with your actual problem. Also, since it appears to work for me, it's probably not a packaging bug. Please talk to upstream and see what the problem could be. springlobby has a fairly active development team that can help you debug.

Loading...