Bugzilla – Bug 752
Windows XP shortcut links crash SlimServer (SQL version only)
Last modified: 2008-08-18 10:53:01 UTC
This is probably a known problem, but I thought I'd better file a bug report anyway.... The 21/12 nightly build crashes when it tries to follow a Windows shortcut (.lnk). The log message is as shown below (I've stolen this from a mail on the developer's list): C:\Program Files\SlimServer\server>slim --d_info 2004-12-23 10:07:05.6794 loading types config file... 2004-12-23 10:07:05.6820 Tag database support is ON, saving into: C:\Program Files\SlimServer\server\Cache\slimserversql.db 2004-12-23 10:07:05.7530 Connected to database dbi:SQLite:dbname=C:\Program Files\SlimServer\server\Cache\slimserversql.db 2004-12-23 10:07:05.7681 No upgrades found for database v. 3 2004-12-23 10:07:05.9233 Clearing ID3 cache 2004-12-23 10:07:05.9235 clearing validity for rescan 2004-12-23 10:07:05.9236 Starting background scanning. 2004-12-23 10:07:05.9239 Starting music folder scan 2004-12-23 10:07:05.9549 CacheItem: Checking status of file:///E:/SlimServer/Music (TTL: 0). 2004-12-23 10:07:05.9835 Request for AGE on file file:///E:/SlimServer/Music 2004-12-23 10:07:06.0607 Starting background import monitors. 2004-12-23 10:07:07.1372 CacheItem: Checking status of file:///E:/SlimServer/Music/CD.lnk (TTL: 0). 2004-12-23 10:07:07.1504 deleting file:///E:/SlimServer/Music/CD.lnk from cache as it has changed 2004-12-23 10:07:07.5261 cached an 1 item playlist for file:///E:/SlimServer/Music/CD.lnk 2004-12-23 10:07:07.5269 CacheItem: Checking status of file:////Ftl8400/Audio/CD (TTL: 0). 2004-12-23 10:07:07.6510 Request for AGE on file file:////Ftl8400/Audio/CD Can't use an undefined value as an ARRAY reference at /PerlApp/Slim/Utils/Scan.pm line 194. This is 100% reproducible, and still occurs if the shortcuts point to somewhere else on the same drive. It looks like the new SQL back-end simply can't handle windows shortcuts yet.
Dan: can you take a look at this?
Chris - can you try the most recent 6.0 nightly build? I believe we've gotten this fixed. I'm unable to reproduce this. Thanks.
Just tested it using the 2005-01-13 nightly, and it now works! Thanks for that - I guess this bug can be closed now.... Chris