Latest SC7 build - settings page won't load

[Mark Lanctot]

I wish I could tell you which build it is, but I can't load the settings page. It's the .deb available today.

My home page seems to load (a little slowly) and display OK, but the browser indicates that the page is still loading by displaying "Waiting for 192.168.1.8", a 3/4 complete progress bar, and a spinning page load icon.

The settings page doesn't load at all, I get a new tab but nothing is displayed.

I'm using Swiftweasel 2.0.0.11 - this is a CPU-optimized build of Firefox 2.0.0.11. Since this is a rare browser, I also used Firefox 2.0.0.8 32-bit and Firefox 2.0.0.11 64-bit, same results.

The PC viewing the server is Ubuntu 7.10 AMD64, all updates installed, Intel Core 2 Duo E6600, 2 GB RAM. The SC7 server PC is more moderately spec'd, AMD Duron 1.2 GHz, 512 MB RAM. The SC7 server is basically idle while (interestingly) the viewing PC is under light load as it tries to load the page.

It's the same story on the SC7 server using Swiftweasel and Firefox trying to load localhost except the processor locks at 100% as it tries to view the page.

Is there anything I can do to assist debugging? This behaviour survives an SC restart and a browser restart even after clearing cache.

[bonze]

Not sure if this is related.

I'm running the latest Windows version:
SqueezeCenter Version: 7.0 - 16243 - Windows Server 2003 - EN - cp1252.
Accessing via IE7 - default web interface

When I first click on Settings, I get all the ususal tabs.
Clicking on each one, I get a double refresh of the screen, and the PC clicks twice. There's also a white line between the tabs and the tab content.
It's as though there are two outputs for each tab click. ??

[kdf]

Quoting Mark Lanctot
<Mark.Lanctot.33775c1200351002 (AT) no-mx (DOT) forums.slimdevices.com>:


> Is there anything I can do to assist debugging? This behaviour
> survives an SC restart and a browser restart even after clearing cache.

first stop, check the log. If you've ended up with any corrupted
templates, it will spit out there. Otherwise, view source (if
available), and network.http set to debug for even more info in the
log. Firebug can also be your friend when using Firefox. Other
add-ons, not always friendly. Some can kill SC browsing.

It should work, but I don't use the .deb so can't confirm directly.
-kdf

[mherger]

> It should work, but I don't use the .deb so can't confirm directly.

Is this what you fixed in 16266?

Michael

[kdf]

On 14-Jan-08, at 10:10 PM, Michael Herger wrote:

>> It should work, but I don't use the .deb so can't confirm directly.
>
> Is this what you fixed in 16266?
no, that was just an overlap for the "unused menu items" section title
and the menu options.
I've not seen any blank settings pages.
-kdf

[fjunger]

I'm having the same problem that the settings page won't load.
Even Squeezecenter isn't displayed properly. There is always "Waiting for localhost..." shown in the statusbar of the browser.

I'm using Ubuntu 7.10 and Firefox 2.0.0.11.

Regards,

Frank

[kdf]

I'm having the same problem that the settings page won't load.
Even Squeezecenter isn't displayed properly. There is always "Waiting for localhost..." shown in the statusbar of the browser.

I'm using Ubuntu 7.10 and Firefox 2.0.0.11.

check the SC server.log and/or install firebug and let us know if it says anything in the firebug console when you try to load the page.

Also make sure that you've cleared the browser cache and reloaded.

-kdf

[fjunger]

Just checked the server.log. Seems to be a problem with Perl, but I am no expert here.

[08-01-15 19:17:01.3676] Slim::Networking::Select::select (245) Error: Select task failed: Can't use an undefined value as a SCALAR reference at /usr/share/perl5/Slim/Web/Graphics.pm line 188.

Any ideas?

[Patrick Dixon]

SqueezeCenter Version: 7.0 - 16284 - Debian - EN - utf8

I have another problem with today's deb - AlienBBC has disappeared from the WebUI (default skin)! It's still there in the player UI.

[mudlark]

One agrees and we are not the only ones...

If you have any alien bbc favourites on the webpages they will probably still work.