https://bugs.kde.org/show_bug.cgi?id=266086
Summary: Digikam 2.0.0-beta2 crashed after closing it Product: digikam Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: [hidden email] ReportedBy: [hidden email] Application: digikam (2.0.0-beta2) KDE Platform Version: 4.6.00 (4.6.0) Qt Version: 4.7.0 Operating System: Linux 2.6.35-25-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: I had been moving files and renaming, creating and removing folders in Nautilus to see if the changes reflected in digiKam. Before that I viewed few images and added 3 tags to 2 images. I was finished and decided to close digiKam (upper right corner), when at first it seemed unresponsive and Ubuntu's 'Application x is not responsing, force quit' appeared. I decided to wait and after few seconds the main window of digiKam disappeared and then Report crash appeared. I have the terminal output of digikam for this entire session if you want it. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [Current thread is 1 (Thread 0x7f3e6848a9a0 (LWP 11170))] Thread 2 (Thread 0x7f3e49e33700 (LWP 11171)): #0 0x00007f3e5f4ed203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f3e5a84a009 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007f3e5a84a7b5 in g_main_loop_run () from /lib/libglib-2.0.so.0 #3 0x00007f3e552400f4 in ?? () from /usr/lib/libgio-2.0.so.0 #4 0x00007f3e5a86f7e4 in ?? () from /lib/libglib-2.0.so.0 #5 0x00007f3e5bbfc971 in start_thread (arg=<value optimized out>) at pthread_create.c:304 #6 0x00007f3e5f4f992d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f3e6848a9a0 (LWP 11170)): [KCrash Handler] #6 QMapData::continueFreeData (this=0x2ec7600, offset=0) at tools/qmap.cpp:89 #7 0x00000000005c4091 in Digikam::AlbumManagerPriv::~AlbumManagerPriv() () #8 0x00000000005af97a in Digikam::AlbumManager::~AlbumManager (this=0x102fbd0, __in_chrg=<value optimized out>) at /src/trunk/digikam-2.0.0-beta2/core/digikam/albummanager.cpp:348 #9 0x00000000005af9d7 in ~AlbumManagerCreator () at /src/trunk/digikam-2.0.0-beta2/core/digikam/albummanager.cpp:277 #10 destroy () at /src/trunk/digikam-2.0.0-beta2/core/digikam/albummanager.cpp:281 #11 0x00007f3e5f44c4f2 in __run_exit_handlers (status=0) at exit.c:78 #12 exit (status=0) at exit.c:100 #13 0x00007f3e5f431d95 in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff1bd08f88) at libc-start.c:258 #14 0x00000000004855d9 in _start () Reported using DrKonqi -- 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=266086
--- Comment #1 from Marcel Wiesweg <marcel wiesweg gmx de> 2011-04-07 20:57:01 --- Crash occurs when data structures are cleared at shutdown. There is no clear indication where the problem lies. Can you reproduce at all? -- 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 terri.bugs@gmx.com
https://bugs.kde.org/show_bug.cgi?id=266086
--- Comment #2 from <terri bugs gmx com> 2011-04-07 21:58:11 --- With beta2, I could reproduce this crash every time I did all the things mentioned in comment #1, order of execution did not seem to matter. However, I have had no such crashes with beta3 so I assume the problem, whatever it was, has been solved. As far as I'm concerned, you can mark this as closed. Will open again if I have similar problems with beta4. -- 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 terri.bugs@gmx.com
https://bugs.kde.org/show_bug.cgi?id=266086
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |[hidden email] Version|unspecified |2.0.0 Resolution| |FIXED -- 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 terri.bugs@gmx.com
https://bugs.kde.org/show_bug.cgi?id=266086
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version Fixed In| |2.0.0 -- 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 terri.bugs@gmx.com
https://bugs.kde.org/show_bug.cgi?id=266086
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|general |Database-Scan -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |