Bug 4802 – Use of uninitialized value in concatenation

Bug 4802 - Use of uninitialized value in concatenation

Summary:

Use of uninitialized value in concatenation

Status:	RESOLVED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Misc
Version:	6.5.2
Platform:	PC Windows XP

Importance:	P2 trivial (vote)
Target Milestone:	---
Assigned To:	Ross Levine

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-03-04 19:11 UTC by Jim McAtee
Modified:	2007-04-05 16:32 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jim McAtee 2007-03-04 19:11:46 UTC

I'm seeing this warning on startup:

2007-03-04 20:02:28.2482 Use of uninitialized value in concatenation (.) or string at C:\Program Files\SlimServer Dot 6\server/Slim/Display/Lib/Fonts.pm line 379.

It's also present in the trunk:

[21:28:50.5675] Slim::Utils::Misc::msg (1140) Warning: [21:28:50.5668] Use of uninitialized value in concatenation (.) or string at C:/Program Files/SlimServer Dot3/server/Slim/Display/Lib/Fonts.pm line 395.

Comment 1 Jim McAtee 2007-03-04 19:30:32 UTC

I should have mentioned this is running the Perl code on Windows XP.  Trying to debug another problem I notice this is only being logged when the Perl version is run as a Windows service.  I don't see the warning when run from the command line.

Comment 2 Ross Levine 2007-03-05 14:53:54 UTC

I'll assign this one to me for now, I should have some time to work on this later today.

Comment 3 Ross Levine 2007-03-12 16:58:11 UTC

Sorry for the delay I've only just now established an XP image with active perl installed running trunk. I'm not seeing this error message, when are you seeing it? On boot, while starting SlimServer? Any 3rd party plugins or anything installed?

Comment 4 Adrian Smith 2007-03-15 13:25:50 UTC

I suspect you only see this is perl is run with warnings enabled and the fontcache file is removed - this will happen when you first run slimserver on a new install.

Jim - I assume you see two warnings when starting a server with no fontcache file?

Comment 5 Adrian Smith 2007-03-15 15:06:28 UTC

Jim does change 11641 in trunk fix this for you?  You need to remove the Cache/fontcache file and restart to see this error anyway.  I'm minded to just fix this in 7.0.

Comment 6 Ross Levine 2007-04-05 16:32:35 UTC

If its alright with you Jim I'd like to mark this bug as worksforme. If you're still seeing the error please feel free to re-open this bug with more details.