| Summary: | application crashes when closing completed batch resize or convert | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Mathieu Baudier <mbaudier> |
| Component: | Plugin-Bqm-Resize | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | anaselli |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 0.3.0 | |
| Sentry Crash Report: | |||
|
Description
Mathieu Baudier
2009-04-14 20:19:04 UTC
Well, i cannot see what is wrong here. Ther eis nothing special in backtrace. To be sure, try to reproduce the crash using Gwenview as kipi host program. Gilles Caulier I just installed Gwenview but I cannot use the plugins (batch resize / convert). They are grey even when I select a few pictures. Only Red eyes removal is active. What should I do to use them / activate them? I forgot to say that I am working with Gnome. There is no reason. I don't know why it doesn' work under GWenview... Angelo, any tips here ? Note: Gnome as no incidence here... Gilles Please note that it is pretty easy to reproduce with Digikam. I ran it in GDB but got the same backtrace. Don't hesitate to tell me if I can do something else. I am a developer myself (rather Java, but I'm comfortable with building Linux apps). I've made some changes in current SVN, maybe they fixed the problem. Can you test it? Note: You need to compile kipi-plugins from SVN, it is not a digiKam problem (I hope so at least). Andi Hi, I followed the instructions on this page in order to build digikam and Kipi plugins: http://www.digikam.org/drupal/download/svn?q=download/KDE4 I uninstalled the standard digikam and kipi-plugins packages from Fedora in order to avoid the distirbute dkipi-plugins being taken by digikam. But when I now start the built digikam I cannot see the kipi-plugins (in the Digikam Settings), so I probably missed a step... How do I tell digikam to use them? (I ran 'make install' as root, is there a way to remove them afterwards? I am not too happy that it impacted /usr and not /usr/local, I should have probably changed the prefix...) Thanks for your help! Mathieu If you done every step as in the above link, /usr is the right way to go. KIPIplugins are KDE services, so they need to reside in the KDE main dir. If 'kde4-config --prefix' delivered /usr for you, then it is /usr :-) There is no way to tell digiKam to use them, try to either 1. run 'kdeinit4' while still logged into a KDE4 session 2. logout / login 3. restart your system Sometimes new services / plugins are not detected by kdeinit4, so you need to run it manually or logout / restart the system. If it is still not working, please post the console output you get when starting digiKam. You can also try to start gwenview and see if the plugins are in there. Andi /usr > ok no pb, I have anyhow the gut feeling that I will run more and more the SVN verison of DigiKam :) (I'm eager to work on some kipi-plugins) I am actually working under GNOME. Is it a problem? I had some weird logs from kdeinit, so as soon as I'm doen with what I am currently doing, I will reboot and try again. (In reply to comment #6) > (I ran 'make install' as root, is there a way to remove them afterwards? Since all files are in their correct place ('kde4-config --prefix' should guarantee this), then you could simply reinstall your fedora packages. If you still want to delete everything first, try the following as root: 1. updatedb 2. locate -i digikam | grep $(kde4-config --prefix). It should save to delete those listed files. But I would skip files in this folder: /YOUR_PREFIX/share/icons/, maybe you delete icons from other packages. 3. do the same with kipi-plugins, just change the search term in the above step: digikam => kipiplugin Andi (In reply to comment #8) > I am actually working under GNOME. Is it a problem? Not directly, but maybe kdeinit4 is not working correctly under Gnome? Try the restart... Andi Restarting did the trick, and I could see the plugins... I tested, and it is not crashing anymore when closing the Kipi Plugin!! To recap my environment: Fedora 10, 2.6.27.21-170.2.56.fc10.x86_64, GNOME 2.24.3 Am I supposed to set the status to RESOLVED? May I ask what do you use as IDE for developing Kipi Plugins? I'd like to have a closer look? (I ten to use Eclipse CDT for C++, but that's rather low-lvel C++ not big UIs like Digikam). Many thanks! Mathieu I'll close it. Well I use Eclipse + CDT, for me it is the best IDE (because I use it for Python and Java, too, so I'm familiar with the UI). Others use KDevelop, or simply vim or emacs. Little note on why I use Eclipse: Although Eclipse is sometimes slower then KDevelop or vim / emacs, I like it because of one plugin: MyLyn. This is very helpful for working on bigger projects. Maybe you know it? It can also connect to the KDE bugtracker and help you organize your workflow. So if you already use Eclipse and don't know MyLyn, take a look: http://www.eclipse.org/mylyn/ It changed my way of programming a lot :-) For the time being, I use MyLyn rather as an UI for Bugzilla, or to deal with specific bugs among tens of different projects, where the focused UI really has an added value. But during new features development, I tend to find it a little too intrusive, with some weird side effects. Anyhow, this is definitely a very interesting approach! |