Bug 429995

Summary: Unexpected Media Server listening on *:8200 - Should have been informed / given the option during 1st run setup.
Product: [Applications] digikam Reporter: Shawn Hughes <sh>
Component: Plugin-Generic-MediaServerAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: wishlist CC: caulier.gilles, metzpinguin
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed In: 7.2.0
Sentry Crash Report:

Description Shawn Hughes 2020-12-04 00:02:17 UTC
SUMMARY
Dismayed to find digikam provided kipi-plugins by default, and along with it installed a new network service on my computer.

STEPS TO REPRODUCE
1. apt-get install digikam
2. launch digikam
3. 

OBSERVED RESULT
minidlna    8u  IPv4  31166      0t0  TCP *:8200 (LISTEN)

EXPECTED RESULT
Be forced to choose whether I want to host a Media Server during install or first run.

SOFTWARE/OS VERSIONS

Linux: Debian 10 / XFCE
(available in About System)
KDE Plasma Version:  n/a
KDE Frameworks Version: n/a
Qt Version: 5.11

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2020-12-04 03:54:26 UTC
witch digiKam version did you use ? 

Gilles Caulier
Comment 2 Maik Qualmann 2020-12-04 10:19:20 UTC
Debian 10 was supposed to ship digiKam-5.9.0, which is a very, very old version. But even this version did not start the media server automatically by default. Go to the media server and disable the start.

Maik
Comment 3 Shawn Hughes 2020-12-04 11:08:07 UTC
using digikam v5.9
Yup, a bit old, but that's what's in Debian Stable repo.

If wish already granted in newer versions, great, but didn't seem like 
something that would change w/o a request.
I've already disabled / removed the unwanted service, so mitigated for now.

Thank You,

Shawn Hughes

On 12/3/20 10:54 PM, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=429995
>
> caulier.gilles@gmail.com changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |caulier.gilles@gmail.com
>
> --- Comment #1 from caulier.gilles@gmail.com ---
> witch digiKam version did you use ?
>
> Gilles Caulier
>
Comment 4 Shawn Hughes 2020-12-04 11:22:27 UTC
Maik,

Thank you:
Seems you're saying I explicitly enabled the Media Server.
While I don't recall turning on anything like 'media server' (I just 
installed digikam on Nov 11), I'll take your word for it and pay closer 
attention next time.

rdepends reports minidlna is used by kipi-plugins which appears to 
primarily provide for pushing images to social networks.
Any chance this is an unintended feature of kipi-plugins?

My apologies to all I've interrupted if this is a non-issue.

Otherwise, I am completely thrilled with digikam. Many thanks to all who 
made it happen.

--
Shawn Hughes

On 12/4/20 5:19 AM, Maik Qualmann wrote:
> https://bugs.kde.org/show_bug.cgi?id=429995
>
> Maik Qualmann <metzpinguin@gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |metzpinguin@gmail.com
>
> --- Comment #2 from Maik Qualmann <metzpinguin@gmail.com> ---
> Debian 10 was supposed to ship digiKam-5.9.0, which is a very, very old
> version. But even this version did not start the media server automatically by
> default. Go to the media server and disable the start.
>
> Maik
>
Comment 5 caulier.gilles 2020-12-04 11:48:33 UTC
1/ minidlna just export media to compatible UPNP/DLNA device as TV, tablet, smartphone, etc. This do not deal with social network.

2/ Since digiKam 6, we do not support Kipiplugins, but a new plugin architecture named DPlugin. With this transition, we left minidlna in favor of Netpune/Patinium framework to export to UPNP device (same framework in used in Kody media center).

3/ the new DPlugin UPNP export tool do not export anything by default

Gilles Caulier
Comment 6 Shawn Hughes 2020-12-04 12:25:00 UTC
per comment 5, clearly not an issue with current versions.