https://bugs.kde.org/show_bug.cgi?id=247175
Summary: digiKam doesn't exit after closing main window Product: digikam Version: 1.3.0 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: [hidden email] ReportedBy: [hidden email] Version: 1.3.0 (using KDE 4.5.0) OS: Linux If I click close button or select "Album — Exit [Ctrl-Q]", main window closes, but the application still remains in memory. Even if no other windows are opened. Then I need to kill it, because when I try to start it again, there are two copies of digikam in memory. Reproducible: Always Steps to Reproduce: 1. start digikam from konsole or 2. start digikam from anywhere. Then try to close it. Actual Results: 1. I don't see the command prompt again, need to Ctrl-C. or 2. open "top", "htop" or use "ps aux" or smth like this, see "digikam" in list. Expected Results: digikam should have disappeared from memory -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #1 from Johannes Wienke <languitar semipol de> 2010-08-09 23:19:52 --- Please start digikam, exit digikam and leave the process running. In another console find the PID of digikam with ps and start "gdb digikam PID". Inside gdb type "thread apply all bt" and paste the output here. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #2 from xapienz <kde org xapienz ru> 2010-08-09 23:49:06 --- Here: (gdb) thread apply all bt Thread 6 (Thread 0xb287cb70 (LWP 24339)): #0 0x003f1416 in __kernel_vsyscall () #1 0x003fc4bc in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0x0466f8e7 in QWaitConditionPrivate::wait (this=0xa47adf8, mutex=0xa47adf4, time=4294967295) at thread/qwaitcondition_unix.cpp:88 #3 QWaitCondition::wait (this=0xa47adf8, mutex=0xa47adf4, time=4294967295) at thread/qwaitcondition_unix.cpp:160 #4 0x05e1c34a in Digikam::ParkingThread::run (this=0xa47ade8) at /build/buildd/digikam-1.3.0/libs/threads/threadmanager.cpp:101 #5 0x0466ed19 in QThreadPrivate::start (arg=0xa47ade8) at thread/qthread_unix.cpp:266 #6 0x003f7cc9 in start_thread (arg=0xb287cb70) at pthread_create.c:304 #7 0x06f6a73e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 5 (Thread 0xb207bb70 (LWP 24340)): #0 0x003f1416 in __kernel_vsyscall () #1 0x06f5be76 in *__GI___poll (fds=0x6ff3ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x07affc0b in g_poll () from /lib/libglib-2.0.so.0 #3 0x07af25bc in ?? () from /lib/libglib-2.0.so.0 #4 0x07af29c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x0479eea5 in QEventDispatcherGlib::processEvents (this=0x9b88af8, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #6 0x0476ef29 in QEventLoop::processEvents (this=0xb207b2c0, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #7 0x0476f3aa in QEventLoop::exec (this=0xb207b2c0, flags=...) at kernel/qeventloop.cpp:201 #8 0x0466ba9e in QThread::exec (this=0x9bc31d0) at thread/qthread.cpp:490 #9 0x0466ed19 in QThreadPrivate::start (arg=0x9bc31d0) at thread/qthread_unix.cpp:266 #10 0x003f7cc9 in start_thread (arg=0xb207bb70) at pthread_create.c:304 #11 0x06f6a73e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 4 (Thread 0xb187ab70 (LWP 24341)): #0 0x003f1416 in __kernel_vsyscall () #1 0x06f5be76 in *__GI___poll (fds=0x6ff3ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x07affc0b in g_poll () from /lib/libglib-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #3 from Johannes Wienke <languitar semipol de> 2010-08-09 23:51:06 --- Please press enter until there is no more output ;) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #4 from xapienz <kde org xapienz ru> 2010-08-09 23:58:04 --- oh, sorry, I need to have a good sleep =\ (gdb) thread apply all bt Thread 6 (Thread 0xb287cb70 (LWP 24339)): #0 0x003f1416 in __kernel_vsyscall () #1 0x003fc4bc in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0x0466f8e7 in QWaitConditionPrivate::wait (this=0xa47adf8, mutex=0xa47adf4, time=4294967295) at thread/qwaitcondition_unix.cpp:88 #3 QWaitCondition::wait (this=0xa47adf8, mutex=0xa47adf4, time=4294967295) at thread/qwaitcondition_unix.cpp:160 #4 0x05e1c34a in Digikam::ParkingThread::run (this=0xa47ade8) at /build/buildd/digikam-1.3.0/libs/threads/threadmanager.cpp:101 #5 0x0466ed19 in QThreadPrivate::start (arg=0xa47ade8) at thread/qthread_unix.cpp:266 #6 0x003f7cc9 in start_thread (arg=0xb287cb70) at pthread_create.c:304 #7 0x06f6a73e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 5 (Thread 0xb207bb70 (LWP 24340)): #0 0x003f1416 in __kernel_vsyscall () #1 0x06f5be76 in *__GI___poll (fds=0x6ff3ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x07affc0b in g_poll () from /lib/libglib-2.0.so.0 #3 0x07af25bc in ?? () from /lib/libglib-2.0.so.0 #4 0x07af29c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x0479eea5 in QEventDispatcherGlib::processEvents (this=0x9b88af8, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #6 0x0476ef29 in QEventLoop::processEvents (this=0xb207b2c0, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #7 0x0476f3aa in QEventLoop::exec (this=0xb207b2c0, flags=...) at kernel/qeventloop.cpp:201 #8 0x0466ba9e in QThread::exec (this=0x9bc31d0) at thread/qthread.cpp:490 #9 0x0466ed19 in QThreadPrivate::start (arg=0x9bc31d0) at thread/qthread_unix.cpp:266 #10 0x003f7cc9 in start_thread (arg=0xb207bb70) at pthread_create.c:304 #11 0x06f6a73e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 4 (Thread 0xb187ab70 (LWP 24341)): #0 0x003f1416 in __kernel_vsyscall () #1 0x06f5be76 in *__GI___poll (fds=0x6ff3ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x07affc0b in g_poll () from /lib/libglib-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #3 0x07af25bc in ?? () from /lib/libglib-2.0.so.0 #4 0x07af29c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x0479eea5 in QEventDispatcherGlib::processEvents (this=0x9bc73f8, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #6 0x0476ef29 in QEventLoop::processEvents (this=0xb187a2c0, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #7 0x0476f3aa in QEventLoop::exec (this=0xb187a2c0, flags=...) at kernel/qeventloop.cpp:201 #8 0x0466ba9e in QThread::exec (this=0x9bb62a0) at thread/qthread.cpp:490 #9 0x0466ed19 in QThreadPrivate::start (arg=0x9bb62a0) at thread/qthread_unix.cpp:266 #10 0x003f7cc9 in start_thread (arg=0xb187ab70) at pthread_create.c:304 #11 0x06f6a73e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 3 (Thread 0xaa513b70 (LWP 24342)): #0 0x003f1416 in __kernel_vsyscall () #1 0x003fc864 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:236 #2 0x075b6a2f in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 2 (Thread 0xa9106b70 (LWP 24344)): #0 0x003f1416 in __kernel_vsyscall () #1 0x06f5be76 in *__GI___poll (fds=0x6ff3ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x07affc0b in g_poll () from /lib/libglib-2.0.so.0 #3 0x07af25bc in ?? () from /lib/libglib-2.0.so.0 #4 0x07af29c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x0479eea5 in QEventDispatcherGlib::processEvents (this=0xa6a24e8, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #6 0x0476ef29 in QEventLoop::processEvents (this=0xa9106250, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #7 0x0476f3aa in QEventLoop::exec (this=0xa9106250, flags=...) at kernel/qeventloop.cpp:201 #8 0x0466ba9e in QThread::exec (this=0xaaaff78) at thread/qthread.cpp:490 #9 0x097ca81a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so #10 0x0466ed19 in QThreadPrivate::start (arg=0xaaaff78) at thread/qthread_unix.cpp:266 #11 0x003f7cc9 in start_thread (arg=0xa9106b70) at pthread_create.c:304 #12 0x06f6a73e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 ---Type <return> to continue, or q <return> to quit--- Thread 1 (Thread 0xb663d740 (LWP 24329)): #0 0x003f1416 in __kernel_vsyscall () #1 0x06f5be76 in *__GI___poll (fds=0x6ff3ff4, nfds=21, timeout=996) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x07affc0b in g_poll () from /lib/libglib-2.0.so.0 #3 0x07af25bc in ?? () from /lib/libglib-2.0.so.0 #4 0x07af29c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x0479eea5 in QEventDispatcherGlib::processEvents (this=0x9a8b698, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #6 0x014680e5 in QGuiEventDispatcherGlib::processEvents (this=0x9a8b698, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #7 0x0476ef29 in QEventLoop::processEvents (this=0xbfb40174, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #8 0x0476f3aa in QEventLoop::exec (this=0xbfb40174, flags=...) at kernel/qeventloop.cpp:201 #9 0x0477392f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #10 0x013a5857 in QApplication::exec () at kernel/qapplication.cpp:3665 #11 0x083bdeab in main (argc=1, argv=0xbfb406f4) at /build/buildd/digikam-1.3.0/digikam/main.cpp:195 (gdb) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #5 from Johannes Wienke <languitar semipol de> 2010-08-10 00:03:30 --- Marcel, this looks like something for you ;) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
You're using KDE 4.5.
I'm using svn trunk and Martin is using a 4.5 packages. We get this same problem.
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #6 from Aditya Bhatt <adityabhatt1991 gmail com> 2010-08-10 00:05:12 --- You're using KDE 4.5. I'm using svn trunk and Martin is using a 4.5 packages. We get this same problem. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
Johannes Wienke <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #7 from Johannes Wienke <languitar semipol de> 2010-08-12 09:43:51 --- *** Bug 247469 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #8 from Philippe ROUBACH <philippe roubach free fr> 2010-08-12 10:00:51 --- i have same pb with konsole and ksysguard -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #9 from Johannes Wienke <languitar semipol de> 2010-08-12 10:11:11 --- Is there a special bug report for KDE 4.5 that summarizes this problem? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #10 from Philippe ROUBACH <philippe roubach free fr> 2010-08-12 11:35:32 --- don't know if there is a special report about 4.5 but it's a long last pb since 4.2.98 ! (konsole,digikam, ksysguard) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #11 from Johannes Wienke <languitar semipol de> 2010-08-12 11:53:32 --- Ok, your konsole issues etc. probably are unrelated to this bug. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #12 from Philippe ROUBACH <philippe roubach free fr> 2010-08-12 12:08:13 --- digikam has also this pb since kde 4.3 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #13 from Philippe ROUBACH <philippe roubach free fr> 2010-08-12 19:15:40 --- is it normal digikam nepomuk service is active even if digikam is closed ? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
I don't think this could have anything to do with nepomuk or digiKam's nepomuk interface, I've tried this with both nepomuk running and not running, and with the digikam nepomuk interface both on and off. Problem persists.
I'm inclined to think that this is caused by the KDE 4.5 libs, probably. Because I didn't see this problem on my stable 4.4 install.
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #14 from Aditya Bhatt <adityabhatt1991 gmail com> 2010-08-12 19:41:12 --- I don't think this could have anything to do with nepomuk or digiKam's nepomuk interface, I've tried this with both nepomuk running and not running, and with the digikam nepomuk interface both on and off. Problem persists. I'm inclined to think that this is caused by the KDE 4.5 libs, probably. Because I didn't see this problem on my stable 4.4 install. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #15 from <tnemeth free fr> 2010-08-13 18:02:05 --- *** Bug 247550 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
--- Comment #16 from Johannes Wienke <languitar semipol de> 2010-08-13 21:27:30 --- I just found these lines in the kile code: // BUG 220343: Under some circumstances (Qt 4.5.3 or KDE 4.3 issues (?)) Kile doesn't terminate when the // main window is closed. So, we force this here. Everything seems to work fine with Qt 4.6. connect(m_mainWindow, SIGNAL(destroyed(QObject*)), kapp, SLOT(quit())); Can someone with this problem test if this helps? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from kde.org@xapienz.ru
https://bugs.kde.org/show_bug.cgi?id=247175
Martin Klapetek <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #17 from Martin Klapetek <martin klapetek gmail com> 2010-08-13 23:44:20 --- Adding it to digikamapp.cpp indeed does solve this issue. although sometimes some errorneous behaviour then appears on the console in form of "Object::disconnect: Unexpected null parameter", but nothing serious. Works for me. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Free forum by Nabble | Edit this page |