| Summary: | Digikam does not quit gracefully | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | tnemeth |
| Component: | Database-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version First Reported In: | 1.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.0.0 | |
| Sentry Crash Report: | |||
Can you have a look if this is a duplicate of bug 247175 by doing the same gdb steps? (In reply to comment #1) > Can you have a look if this is a duplicate of bug 247175 by doing the same gdb > steps? I don't have the version with debugging symbols so I'm not able to show you the stack, but by the given description, it seems to be indeed a duplicate... Sorry I didn't find it before. *** This bug has been marked as a duplicate of bug 247175 *** Not reproducible using digiKam 7.0.0 beta1. |
Version: 1.3.0 (using KDE 4.5.0) OS: Linux Digikam keeps running after beeing closed in a infinite loop waiting for some event. $ ps aux | grep digikam ... thomas 16157 2.2 8.5 950500 175980 ? Sl 19:13 0:07 /usr/bin/digikam -caption digiKam -icon digikam ... With : S Interruptible sleep (waiting for an event to complete) l is multi-threaded (using CLONE_THREAD, like NPTL pthreads do) Reproducible: Always Steps to Reproduce: Launch digikam, look at some photographs, quit it and have a look at the process table. Actual Results: thomas 16157 2.2 8.5 950500 175980 ? Sl 19:13 0:07 /usr/bin/digikam -caption digiKam -icon digikam Expected Results: Nothing should appear. I don't know if it's a wanted feature, but it keeps the action "Download Photos With Digikam" from properly beeing executed. I discovered that when trying to download my photographs and it didn't worked. I then had a look at the action menu to know how digikam was launched: that gave me the idea to have a look at the process table. There was 3 instance of digikam running. When I killed the 3 instances with SIGTERM (does digikam handle this signal ?) I could use the action menu normally. But still the new instance was still running after I quit the application.