Bug 315580 - digiKam crashed after I changed the DLNA implementation from "HUPnP API" to "miniDLNA"
Summary: digiKam crashed after I changed the DLNA implementation from "HUPnP API" to "...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-MediaServer (show other bugs)
Version: 3.0.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-21 15:32 UTC by againsttcpa84
Modified: 2017-10-01 13:55 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.8.0


Attachments
New crash information added by DrKonqi (10.54 KB, text/plain)
2013-02-21 15:50 UTC, againsttcpa84
Details
New crash information added by DrKonqi (9.65 KB, text/plain)
2013-02-24 14:34 UTC, againsttcpa84
Details

Note You need to log in before you can comment on or make changes to this bug.
Description againsttcpa84 2013-02-21 15:32:15 UTC
Application: digikam (3.0.0-beta3)
KDE Platform Version: 4.10.00
Qt Version: 4.8.3
Operating System: Linux 3.5.0-24-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
- What I was doing when the application crashed:

I exported one folder with the miniDLNA implementation and could access the files on my Android phone. Then I pressed "Stop", and twice on "Back", changed the DLNA implementation from "miniDLNA" to "HUPnP API" --> Crash

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f81871a1a00 (LWP 3714))]

Thread 7 (Thread 0x7f815f57c700 (LWP 3727)):
#0  0x00007f81809858bd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f81797ed15f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f81797b0914 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f81797b0d22 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f81797b11e2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f816f1854a6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x00007f81797d4645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f817bd87e9a in start_thread (arg=0x7f815f57c700) at pthread_create.c:308
#8  0x00007f8180992cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#9  0x0000000000000000 in ?? ()

Thread 6 (Thread 0x7f8157143700 (LWP 3730)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f818176a07b in wait (time=18446744073709551615, this=0x1294b00) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x12894d8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000005cab28 in ?? ()
#4  0x00007f8181769b1c in QThreadPrivate::start (arg=0x128d290) at thread/qthread_unix.cpp:338
#5  0x00007f817bd87e9a in start_thread (arg=0x7f8157143700) at pthread_create.c:308
#6  0x00007f8180992cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f8156942700 (LWP 3731)):
#0  0x00007fff5debd626 in ?? ()
#1  0x00007fff5debd89c in clock_gettime ()
#2  0x00007f817841f15d in __GI_clock_gettime (clock_id=<optimized out>, tp=<optimized out>) at ../sysdeps/unix/clock_gettime.c:116
#3  0x00007f81817bf9f4 in do_gettime (frac=0x7f81569418a8, sec=0x7f81569418a0) at tools/qelapsedtimer_unix.cpp:123
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#5  0x00007f818189544d in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f8144002460) at kernel/qeventdispatcher_unix.cpp:343
#6  0x00007f8181895793 in QTimerInfoList::timerWait (this=0x7f8144002460, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#7  0x00007f81818942fc in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f8156941994) at kernel/qeventdispatcher_glib.cpp:136
#8  0x00007f81818943a5 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#9  0x00007f81797b0618 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f81797b0cab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f81797b0ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f8181894c46 in QEventDispatcherGlib::processEvents (this=0x7f81440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#13 0x00007f81818652ef in QEventLoop::processEvents (this=this@entry=0x7f8156941b50, flags=...) at kernel/qeventloop.cpp:149
#14 0x00007f8181865578 in QEventLoop::exec (this=0x7f8156941b50, flags=...) at kernel/qeventloop.cpp:204
#15 0x00007f8181766b40 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#16 0x00007f81818459df in QInotifyFileSystemWatcherEngine::run (this=0x128f6a0) at io/qfilesystemwatcher_inotify.cpp:248
#17 0x00007f8181769b1c in QThreadPrivate::start (arg=0x128f6a0) at thread/qthread_unix.cpp:338
#18 0x00007f817bd87e9a in start_thread (arg=0x7f8156942700) at pthread_create.c:308
#19 0x00007f8180992cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#20 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f815fd7d700 (LWP 3816)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f818176a07b in wait (time=18446744073709551615, this=0x15251c0) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x1524058, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f818480d7e9 in ?? () from /usr/lib/libdigikamcore.so.3
#4  0x00007f8181769b1c in QThreadPrivate::start (arg=0x1524040) at thread/qthread_unix.cpp:338
#5  0x00007f817bd87e9a in start_thread (arg=0x7f815fd7d700) at pthread_create.c:308
#6  0x00007f8180992cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f8156141700 (LWP 3817)):
#0  0x00007f81797edbb6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f81797ede19 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f81797b06eb in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f81797b0cf9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f81797b0ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f8181894c46 in QEventDispatcherGlib::processEvents (this=0x7f8148002a70, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f81818652ef in QEventLoop::processEvents (this=this@entry=0x7f8156140b50, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f8181865578 in QEventLoop::exec (this=0x7f8156140b50, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f8181766b40 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007f81818459df in QInotifyFileSystemWatcherEngine::run (this=0x18a15a0) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f8181769b1c in QThreadPrivate::start (arg=0x18a15a0) at thread/qthread_unix.cpp:338
#11 0x00007f817bd87e9a in start_thread (arg=0x7f8156141700) at pthread_create.c:308
#12 0x00007f8180992cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f81227fc700 (LWP 3941)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f818176a07b in wait (time=18446744073709551615, this=0x4596a10) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x4595a48, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f81360c2e76 in KIPIPlugins::KPRawThumbThread::run() () from /usr/lib/libkipiplugins.so.3
#4  0x00007f8181769b1c in QThreadPrivate::start (arg=0x4595ed0) at thread/qthread_unix.cpp:338
#5  0x00007f817bd87e9a in start_thread (arg=0x7f81227fc700) at pthread_create.c:308
#6  0x00007f8180992cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f81871a1a00 (LWP 3714)):
[KCrash Handler]
#6  QString::operator= (this=0x68, other=...) at tools/qstring.cpp:1411
#7  0x00007f812f1de036 in ?? () from /usr/lib/kde4/kipiplugin_dlnaexport.so
#8  0x00007f812f1e0633 in ?? () from /usr/lib/kde4/kipiplugin_dlnaexport.so
#9  0x00007f818187bf8f in QMetaObject::activate (sender=0x4134440, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#10 0x00007f8182eb1398 in KDialog::slotButtonClicked (this=0x4134440, button=8192) at ../../kdeui/dialogs/kdialog.cpp:897
#11 0x00007f8182eb18b4 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./kdialog.moc:167
#12 KDialog::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./kdialog.moc:127
#13 0x00007f818187bf8f in QMetaObject::activate (sender=0x3069ad0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff5de7dca0) at kernel/qobject.cpp:3547
#14 0x00007f8181881e5e in QSignalMapper::mapped (this=this@entry=0x3069ad0, _t1=8192) at .moc/release-shared/moc_qsignalmapper.cpp:115
#15 0x00007f8181882065 in QSignalMapper::map (this=0x3069ad0, sender=0x132b680) at kernel/qsignalmapper.cpp:266
#16 0x00007f818187bf8f in QMetaObject::activate (sender=0x132b680, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff5de7de30) at kernel/qobject.cpp:3547
#17 0x00007f81828b2422 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:220
#18 0x00007f8182605d2e in QAbstractButtonPrivate::emitClicked (this=this@entry=0x12d59c0) at widgets/qabstractbutton.cpp:548
#19 0x00007f8182606560 in QAbstractButtonPrivate::click (this=this@entry=0x12d59c0) at widgets/qabstractbutton.cpp:541
#20 0x00007f81826067cc in QAbstractButton::mouseReleaseEvent (this=0x132b680, e=0x7fff5de7e6d0) at widgets/qabstractbutton.cpp:1123
#21 0x00007f8182297850 in QWidget::event (this=0x132b680, event=0x7fff5de7e6d0) at kernel/qwidget.cpp:8371
#22 0x00007f8182247e9c in QApplicationPrivate::notify_helper (this=this@entry=0xf74800, receiver=receiver@entry=0x132b680, e=e@entry=0x7fff5de7e6d0) at kernel/qapplication.cpp:4562
#23 0x00007f818224cb6b in QApplication::notify (this=<optimized out>, receiver=0x132b680, e=0x7fff5de7e6d0) at kernel/qapplication.cpp:4105
#24 0x00007f8182f50636 in KApplication::notify (this=0x7fff5de7f830, receiver=0x132b680, event=0x7fff5de7e6d0) at ../../kdeui/kernel/kapplication.cpp:311
#25 0x00007f818186659e in QCoreApplication::notifyInternal (this=0x7fff5de7f830, receiver=0x132b680, event=0x7fff5de7e6d0) at kernel/qcoreapplication.cpp:915
#26 0x00007f8182248cd3 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#27 QApplicationPrivate::sendMouseEvent (receiver=0x132b680, event=0x7fff5de7e6d0, alienWidget=0x132b680, nativeWidget=0x4134440, buttonDown=0x7f8182d24308 <qt_button_down>, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3173
#28 0x00007f81822c6554 in QETWidget::translateMouseEvent (this=this@entry=0x4134440, event=event@entry=0x7fff5de7ee50) at kernel/qapplication_x11.cpp:4622
#29 0x00007f81822c544f in QApplication::x11ProcessEvent (this=0x7fff5de7f830, event=0x7fff5de7ee50) at kernel/qapplication_x11.cpp:3737
#30 0x00007f81822ecfa2 in x11EventSourceDispatch (s=0xf74640, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#31 0x00007f81797b0ab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007f81797b0de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007f81797b0ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x00007f8181894c26 in QEventDispatcherGlib::processEvents (this=0xf73770, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#35 0x00007f81822ecc1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 0x00007f81818652ef in QEventLoop::processEvents (this=this@entry=0x7fff5de7f220, flags=...) at kernel/qeventloop.cpp:149
#37 0x00007f8181865578 in QEventLoop::exec (this=0x7fff5de7f220, flags=...) at kernel/qeventloop.cpp:204
#38 0x00007f818186a738 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#39 0x000000000048ed3b in ?? ()
#40 0x00007f81808c076d in __libc_start_main (main=0x48dc00, argc=5, ubp_av=0x7fff5de7fa68, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff5de7fa58) at libc-start.c:226
#41 0x0000000000490bfd in _start ()

Reported using DrKonqi
Comment 1 againsttcpa84 2013-02-21 15:47:02 UTC
Sorry, my first comment was wrong. I used the "HUPnP API" (not the miniDLNA), exported successfully some pictures, went back, changed to "miniDLNA" --> Crash
Comment 2 againsttcpa84 2013-02-21 15:50:52 UTC
Created attachment 77490 [details]
New crash information added by DrKonqi

digikam (3.0.0-beta3) on KDE Platform 4.10.00 using Qt 4.8.3

- What I was doing when the application crashed:

As mentionned in the comment before, I exported some pictures with HUPnP, went back (whis time without stopping the server!), changed to miniDLNA --> Crash
Btw, I installed miniDLNA (v1.0.24) with synaptic in Ubuntu 12.10

-- Backtrace (Reduced):
#6  QString::operator= (this=0x68, other=...) at tools/qstring.cpp:1411
[...]
#10 0x00007f90cc56a398 in KDialog::slotButtonClicked (this=0x5b62d90, button=8192) at ../../kdeui/dialogs/kdialog.cpp:897
#11 0x00007f90cc56a8b4 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./kdialog.moc:167
#12 KDialog::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./kdialog.moc:127
[...]
#14 0x00007f90caf3ae5e in QSignalMapper::mapped (this=this@entry=0x4f4b210, _t1=8192) at .moc/release-shared/moc_qsignalmapper.cpp:115
Comment 3 Marcel Wiesweg 2013-02-23 11:18:48 UTC
This is the proper summary of the backtrace:
#6 QString::operator= (this=0x68, other=...) at tools/qstring.cpp:1411 
#7 0x00007f812f1de036 in ?? () from /usr/lib/kde4/kipiplugin_dlnaexport.so 
#8 0x00007f812f1e0633 in ?? () from /usr/lib/kde4/kipiplugin_dlnaexport.so 
#9 0x00007f818187bf8f in QMetaObject::activate (sender=0x4134440, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547 
#10 0x00007f8182eb1398 in KDialog::slotButtonClicked (this=0x4134440, button=8192) at ../../kdeui/dialogs/kdialog.cpp:897 

indicating we'll need debug symbol for the DLNA export kipi plugin to proceed
Comment 4 againsttcpa84 2013-02-24 14:34:50 UTC
Created attachment 77552 [details]
New crash information added by DrKonqi

digikam (3.0.0-beta3) on KDE Platform 4.10.00 using Qt 4.8.3

I installed digikam-dbg and libkipi-dbg and triggered the crash again. I hope this time the crash-report contains enough information. If not, please let me know what else I can do to help.

-- Backtrace (Reduced):
#6  0x00007f5aa2b58d0a in KIPIDLNAExportPlugin::FinalPage::turnOff (this=0x527a720) at /build/buildd/digikam-3.0.0~rc-really-beta3/extra/kipi-plugins/dlnaexport/finalpage.cpp:134
[...]
#8  0x00007f5af62b6422 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:220
#9  0x00007f5af6009d2e in QAbstractButtonPrivate::emitClicked (this=this@entry=0x5312190) at widgets/qabstractbutton.cpp:548
#10 0x00007f5af600a560 in QAbstractButtonPrivate::click (this=this@entry=0x5312190) at widgets/qabstractbutton.cpp:541
#11 0x00007f5af600a7cc in QAbstractButton::mouseReleaseEvent (this=0x5312110, e=0x7fffab34b370) at widgets/qabstractbutton.cpp:1123
Comment 5 Smit Mehta 2013-03-01 10:14:02 UTC
Hi againsttcpa84@gmail.com

Thanks a lot. I think this back trace is enough for the moment. But I would like to know which app on Andorid do you use for testing the DLNA plugin.

Smit
Comment 6 againsttcpa84 2013-03-01 14:25:11 UTC
Hi Smit,
I approached the digiKam-user mailing-list to get suggestions for DLNA-apps for Android and iOS. 
http://thread.gmane.org/gmane.comp.kde.digikam.user/19814

"BubbleUPnP" works best for me. The app supports thumbnails (veeery helpful in my opinion, but sometimes the app has some caching problems), swiping to change pictures, slideshow, ...
In addition, I use "AnDLNA" to double-check if something does not work as expected. 
A couple of other apps I tried did not work at all (MediaHouse, iMediaShare, ...)
Btw, I use now the final digiKam 3.0 release (not beta3 anymore).

[Off topic]
* only HUPnP works, miniDLNA (1.0.24) shows me only four empty folders on all apps
* digiKam forgets the path to miniDLNA every time and needs to be told again
* HUPnP delivers the picture not in alphabetical order, but based on some magic, which breaks any picture presentation if the locations jump back and forth
* Pictures with spaces in their filename _can_ be streamed actually (contrary to what I said on the mailinglist)
* on iOS, MediaConnect works sometimes, it looks like only for the first 3 pictures?!? But Gilles Caulier reports this app works well on iPad 2&4
* DLNA export is a great feature! Thank you very much for your work!
Comment 7 caulier.gilles 2013-03-04 22:00:16 UTC
*** Bug 316126 has been marked as a duplicate of this bug. ***
Comment 8 Smit Mehta 2013-03-05 09:34:54 UTC
Hi

Thanks for your inputs. First of all, once the server starts, back button should be deactivated. I will modify the code to do that. Secondly, after you click the stop button, you should be able to go back and forth again. There is some problem with deletion of the object which actually is responsible for sharing the pictures on the server. I shall take a look into that. So I assume, your latest trace is after clicking the "stop" button, and then going back, right?

Smit
Comment 9 Smit Mehta 2013-03-05 10:05:01 UTC
Git commit 67b8f5a26dcc00d29a14867ec01ee69ec33bf1e1 by Smit Mehta.
Committed on 05/03/2013 at 11:03.
Pushed by smitmehta into branch 'master'.

Added signal/slotting for disabling/enabling back button when sharing starts/stops.
TODO: Figure out the crash, fix finish button, save minidlna binary path in system

M  +6    -0    dlnaexport/finalpage.cpp
M  +3    -0    dlnaexport/finalpage.h
M  +12   -0    dlnaexport/wizard.cpp
M  +1    -0    dlnaexport/wizard.h

http://commits.kde.org/kipi-plugins/67b8f5a26dcc00d29a14867ec01ee69ec33bf1e1
Comment 10 Smit Mehta 2013-03-05 10:06:09 UTC
Sorry, closed it by mistake.
Comment 11 José Juan 2013-03-05 14:51:09 UTC
Thank you for your answer. If I'm not wrong, the trace was sent without
clicking either on stop nor start bottom. I think this was so, because I
had not decided myself yet on which to use.

José


2013/3/5 Smit Mehta <smit.meh@gmail.com>

> https://bugs.kde.org/show_bug.cgi?id=315580
>
> Smit Mehta <smit.meh@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|RESOLVED                    |REOPENED
>          Resolution|FIXED                       |---
>
> --- Comment #10 from Smit Mehta <smit.meh@gmail.com> ---
> Sorry, closed it by mistake.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
Comment 12 Smit Mehta 2013-03-06 19:06:43 UTC
Hi againsttcpa84@gmail.com

I have fixed quite a bunch of stuff. I dont think it will crash now. I am still looking in minidlna as to why its not able to share stuff. Kindly get the latest source code, and see if it still crashes.

Smit
Comment 13 José Juan 2013-03-06 21:58:24 UTC
I have not been able to see it today (sorry - there's been a lot of work)
I'll try it out tomorrow.


2013/3/6 Smit Mehta <smit.meh@gmail.com>

> https://bugs.kde.org/show_bug.cgi?id=315580
>
> Smit Mehta <smit.meh@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REOPENED                    |RESOLVED
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #12 from Smit Mehta <smit.meh@gmail.com> ---
> Hi againsttcpa84@gmail.com
>
> I have fixed quite a bunch of stuff. I dont think it will crash now. I am
> still
> looking in minidlna as to why its not able to share stuff. Kindly get the
> latest source code, and see if it still crashes.
>
> Smit
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
Comment 14 José Juan 2013-03-07 14:56:58 UTC
Well, I've trying to share my photos with the plugin to my smartTV. I've
not been able to see anything neither with HUP nor with minidlna. The
problem might have to do with two things:
First, and I think this is specific to openSUSE, minidlna as such requires
root privileges to be run. So when you start sharing using the plugin
nothing at all will happen unless you have started the service (rcminidlna)
by yourself as root.
Second, minidlna stores its configuration file in /etc. (minidlna.conf).
You have to manually edit this file to specify the folders you want to
share. This, as before, requires root privileges. Even more, since minidlna
does not automatically rescans your collections, if you want to add other
directories or actualize what you share, the command minidlna -R must be
run with root privileges. So choosing directories with the plugin does not
have any consequence for what you share.

Besides, there are some strange things. After starting as root the service,
and starting the plugin inside digiKam, the TV was able to see the folders
that I have chosen to be shared. But they did not contain any pictures even
though I have selected them in the last window.
Even more, I've seen that when specifying the folders to share, the
selection doesn't work recursively. I mean, if in a directory (like /fotos)
you have something like /fotos/Nature; and /fotos/Cities; and you only tick
on /fotos; the folders inside /fotos didn't appear on the TV.

Well, I hope I can throw some light into the problems with this promising
plugin. I have always wonder why minidlna installs with root privileges in
SUSE (default installation using either zypper or YaST). I suppose that if
you compile it from source yourself, this will not happen; but I have not
try it myself.

Thanks a lot for your work.

José


2013/3/6 José Juan González <netphilos@gmail.com>

> I have not been able to see it today (sorry - there's been a lot of work)
> I'll try it out tomorrow.
>
>
> 2013/3/6 Smit Mehta <smit.meh@gmail.com>
>
>> https://bugs.kde.org/show_bug.cgi?id=315580
>>
>> Smit Mehta <smit.meh@gmail.com> changed:
>>
>>            What    |Removed                     |Added
>>
>> ----------------------------------------------------------------------------
>>              Status|REOPENED                    |RESOLVED
>>          Resolution|---                         |WAITINGFORINFO
>>
>> --- Comment #12 from Smit Mehta <smit.meh@gmail.com> ---
>> Hi againsttcpa84@gmail.com
>>
>> I have fixed quite a bunch of stuff. I dont think it will crash now. I am
>> still
>> looking in minidlna as to why its not able to share stuff. Kindly get the
>> latest source code, and see if it still crashes.
>>
>> Smit
>>
>> --
>> You are receiving this mail because:
>> You are on the CC list for the bug.
>>
>
>
Comment 15 caulier.gilles 2015-06-26 13:41:12 UTC
New Kipi-plugins 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 16 caulier.gilles 2015-06-26 13:52:46 UTC
Not reproducible here...

Gilles Caulier
Comment 17 caulier.gilles 2017-10-01 13:55:50 UTC
The tool to export collection through DLNA media server was fully re-written with next 5.8.0. The server is now based on Platinum SDK (same used in Kodi media center), and work fine under Linux, Windows, and MacOS.

https://farm5.staticflickr.com/4346/36415316353_cb72c443e6_c.jpg