For anyone wanting a fix for this add this to your NGG stylesheet:
.widget_slideshow h4 {
display:none;
}
The downside to this fix is that it is an ALL or NONE type of solution.. It removes the widget title for ALL NGG widgets.. For me this is not a big issue as I am using slideshows in my widgets and prefer to not display the title above any of them.. but for others, this may not be a fully satisfying solution..
Again I am running the LATEST version of NGG and despite the fact that this is reported FIXED in V1.5.1 – 23.03.2010, I can definitely report that this does not work for me in THREE separate installs of NGG.. Hence the need for me to find a workaround solution that doesn’t get wiped out everytime I upgrade NGG as the fix below does.
Commented out line 29 as per this thread: http://wordpress.org/support/topic/plugin-nextgen-gallery-slideshow-widget-remove-sidebar-title?replies=5
nextgen-gallery/widgets/widgets.php
you have to remove the line
$title = apply_filters(‘widget_title’, empty( $instance[‘title’] ) ? __(‘Slideshow’, ‘nggallery’) : $instance[‘title’]);
That does the trick. 🙂
I am having the same problem with the NextGEN Widget, not the slideshow. Now version 1.9.10 and this is still happeing. I found the similar line of code at #262.
$title = apply_filters('widget_title', empty($instance['title']) ? ' ' : $instance['title'], $instance, $this->id_base);
I’ve tried commenting the line and removing the   (semi-colons removed so the test actually shows). All this does is give me a narrower title bar. Does anyone have any other suggestions?
This bug seems to have been hanging around for years. Come-on guys get it together and fix this!!
Ok, a two fold hack for widgets.php.
Line #262 remove  .
$title = apply_filters('widget_title', empty($instance['title']) ? '' : $instance['title'], $instance, $this->id_base);
Line #307 change
echo $before_widget . $before_title . $title . $after_title;
to
echo $before_widget;
if (!empty($title)) echo $before_title . $title . $after_title;
If anyone has a better solution I would love to hear it. This still should be fixed in the plugin so it doesn’t need to be reapplied after an update!!
