Bugzilla – Bug 10340
Errors in log when using web UI/browsing New Music
Last modified: 2009-07-29 17:06:10 UTC
With 7.3.1, svn 24301, running on Fedora 10, browsing the web UI from a Windows XP client using Google Chrome: If, after starting SC, the user browses New Music or Genres->Some Genre->Some Artist WITHOUT having first browsed Albums, the log shows many, many error messages complaining that a HTML template requires an argument that has not been initialized. If the user first browses Albums and THEN browses New Music or Genres->Some Genre->Some Artist, no errors occur. So...something is getting initialized in the Album view that isn't getting initialized in the New Music or Genre->Artist view. Please see the attached zip file containing logs demonstrating this. server.log.2 is annotated to show which error messages correspond to which actions.
Created attachment 4446 [details] Zip file containing logs demonstrating the problem
*** Bug 10341 has been marked as a duplicate of this bug. ***
Is 10341 really a duplicate of this? I don't get the same error messages in my log file, and browsing to "Albums" first does not alleviate the problem in my situation.
Do you have cookies disabled in your browser or are you using some kind of "privacy" protecting application? I still can't reproduce the issue.
Ross, are you able to verify this bug
No privacy stuff. Just running plain-jane anti-virus (Windows Live Onecare) on this Windows XP Pro box. I'll test from my Mac Mini using Safari as the browser and report if it causes the same error messages in the same circumstances as Chrome seems to from this Windows client.
Also, Chrome is set to "Allow all cookies".
I'm seeing the same error messages in the log regardless of what web browser I'm using and regardless of which platform the client is browsing from. Attached is a new server log covering browser sessions from 1). Google Chrome from Windows XP; 2). Firefox 3.04 from Windows XP and 3). Safari from Mac OSX.
Created attachment 4462 [details] Zipped server.log with error messages from Chrome, Firefox & Safari
I'm not able to reproduce this with 7.3.1 - 24324. How consistently can you reproduce this?
I can reproduce this with absolute consistently. The ONLY time these errors don't show up in the log is when I browse Music Library->Albums first. In EVERY other instance (Music Library->New Music; Music Library->Genres->Some Genre->Some Artist, etc.) the errors are emitted.
These errors seem to be independent of the audio file type being browsed. I.E. both whole-album flacs with embedded cues and single track per file mp3s both cause the error to be emitted.
Thanks Gordon. Can you please share the music directory path? Any foreign characters, network drive, anything else that could cause something unusual like this? As mentioned I don't see this on a new virtual image of FC10 (accessing from XP machine with Chrome). I'm hoping more details about your setup will help us track down the problem; thanks again!
Re foreign characters in paths: yes, for some. But none of the paths that I'm accessing that produce these errors have them. E.g. /mnt/media/Music/g_German_Baroque/Bach, J S which has no diacritics, produces the errors. I'll attach my server.prefs so you can see all the details. One thing you won't see in there: all the music flacs are stored on a NTFS formatted drive that's mounted via ntfs-3g: /dev/sdb1 /mnt/media ntfs-3g rw,defaults,noatime,umask=0000 0 0 /dev/sdc1 /mnt/backup ntfs-3g rw,defaults,noatime,umask=0000 0 0 I'd be surprised if this ends up being the culprit though. NTFS via ntfs-3g seems completely transparent to the OS.
Created attachment 4468 [details] Zipped server.prefs file
Michael, does this line in the log mean anything to you? [08-12-12 12:58:45.8290] Slim::Utils::Misc::msg (1126) Warning: [12:58:45.8285] Use of uninitialized value in sysread at /usr/share/squeezecenter_trunk/server/Slim/Player/Protocols/File.pm line 216.
I'm sorry, no déjà vu. For protocol stuff Andy and Alan are a better bet.
Andy or Alan, can you help me understand this log?
The sysread warning is fixed a few weeks ago, please update to the latest 7.3.3 nightly.
We are now planning to make a 7.3.3 release. Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future. Thanks!
Gordon, do you still see this after the updates Andy mentions?
Please feel free to re-open, we believe this is fixed.