Opened 13 years ago

Closed 13 years ago

#51 closed defect (fixed)

Lazysearch by keyword crashes on slimserver 6.5.0

Reported by: Rob McKaughan Owned by: stuarth
Priority: major Milestone: 2.3
Component: Plugin Version: 2.2.2
Keywords: Cc: rob@…


Slimserver crashes each time I do a keyword lazy search.

1 - goto lazy keyword search either via menus or search button on remote
2 - start typing keyword - after 4 characters, the server will crash. The following will be in the server log:

Can't use an undefined value as an ARRAY reference at /usr/local/slimserver/Plugins/ line 1734.

Slimserver: 6.5.0 running on fedora 4
Lazysearch: 2.2.2 (Oct-3 release)

Change History (6)

comment:1 Changed 13 years ago by stuarth

  • Milestone set to 2.2.3
  • Status changed from new to assigned
  • Version set to 2.2.2

I think I know what that is (it's a bug with my plugin, as you thought)...

Can you go to "Server Settings->Behaviour" on the SlimServer? web interface and look at the first group of settings (called "COMPOSER, BAND AND ORCHESTRA IN ARTISTS"). I suspect you've got them all turned on.

There's nothing wrong with that, but SlimServer? behaves slightly differently then and that upsets the plugin.

I can fix it, but could you confirm that by turning one of them off (eg "conductor"), then trying a search again?

comment:2 Changed 13 years ago by stuarth

  • Cc rob@… added

comment:3 Changed 13 years ago by stuarth

  • Status changed from assigned to new

comment:4 Changed 13 years ago by stuarth

  • Status changed from new to assigned

comment:5 Changed 13 years ago by stuarth

I had the opportunity so today I think I've made a change that should solve this problem. Could you try the version from here:
(best to right-click and do "save as" to prevent it being corrupted).

It's the latest development version, so the ZIP file in that folder isn't up to date - it's the file within the trunk you want.

Can you let me know how you get on with that? If it solves things I'll push out a 2.2.3 update. Many thanks for reporting it.

comment:6 Changed 13 years ago by stuarth

  • Resolution set to fixed
  • Status changed from assigned to closed

Rob reported today that this version solved the problem, so we can consider this closed in r213.

Thanks, Rob, for the report and testing. This fix will be included in the next formal release.

Note: See TracTickets for help on using tickets.