Summary: | digiKam crashed after I changed the DLNA implementation from "HUPnP API" to "miniDLNA" | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | againsttcpa84 |
Component: | Plugin-Generic-MediaServer | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | againsttcpa84, caulier.gilles, netphilos, smit.meh |
Priority: | NOR | ||
Version: | 3.0.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kipi-plugins/67b8f5a26dcc00d29a14867ec01ee69ec33bf1e1 | Version Fixed In: | 5.8.0 |
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
againsttcpa84
2013-02-21 15:32:15 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 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
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 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
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 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! *** Bug 316126 has been marked as a duplicate of this bug. *** 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 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 Sorry, closed it by mistake. 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. > 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 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. > 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. >> > > New Kipi-plugins 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier Not reproducible here... Gilles Caulier 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 |