Bug 152217 - Showfoto crashes on exit Signal 11
Summary: Showfoto crashes on exit Signal 11
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Showfoto-Core (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-12 20:46 UTC by Santam Chakraborty
Modified: 2022-01-20 06:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Santam Chakraborty 2007-11-12 20:46:26 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Mandriva RPMs
OS:                Linux

When opening Showfoto to view a screenshot taken while running a cube in Compiz Fusion the image displays properly but when closing the application crashes.
I have tried restarting the computer and opening other images in showfoto in compiz fusion - but the crash recurrs.I have noticed if I keep the application running for some time in the background the crash doesnot occur.
The Backtrace generated by the application is as follows:
(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1238829360 (LWP 11811)]
[New Thread -1242551408 (LWP 11813)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb6305870 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#7  0x01010101 in ?? ()
#8  0x00000020 in ?? ()
#9  0xb63c48bc in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#10 0xb6306e41 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#11 0xb63dd12c in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#12 0xb63c2aad in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#13 0xb63c4858 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#14 0xb63dd120 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#15 0x64002d00 in ?? ()
#16 0xb63dd144 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#17 0xb63dd14c in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#18 0x1b602800 in ?? ()
#19 0xb63dd150 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#20 0x00007008 in ?? ()
#21 0xb63c4858 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#22 0x083eb3ff in ?? ()
#23 0xbf7fc060 in ?? ()
#24 0x00000068 in ?? ()
#25 0xb63057eb in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#26 0xb63dbff4 in ?? () from /lib/i686/libc.so.6
#27 0x0820f390 in ?? ()
#28 0x000266b0 in ?? ()
#29 0xbf7fc0c0 in ?? ()
#30 0xb63072ee in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#31 0xbf7fc088 in ?? ()
#32 0x00000010 in ?? ()
#33 0xb63c48bc in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#34 0xb6306e41 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#35 0xb63dd12c in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#36 0x0823b368 in ?? ()
#37 0xb63c4858 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#38 0x0820f390 in ?? ()
#39 0xbf7fc0a8 in ?? ()
#40 0x00000010 in ?? ()
#41 0xb63c48bc in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#42 0x082455d0 in ?? ()
#43 0xb63dd130 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#44 0x08245470 in ?? ()
#45 0xb63c4858 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#46 0x08248208 in ?? ()
#47 0xbf7fc0c8 in ?? ()
#48 0xb63dbff4 in ?? () from /lib/i686/libc.so.6
#49 0xb63dd120 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#50 0x082453f0 in ?? ()
#51 0xbf7fc0d8 in ?? ()
#52 0x08235a40 in ?? ()
#53 0xb63dd120 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#54 0x082420d8 in ?? ()
#55 0xbf7fc0e8 in ?? ()
#56 0xb63dbff4 in ?? () from /lib/i686/libc.so.6
#57 0xb63dd120 in QWidget::setUpdatesEnabled () from /lib/i686/libc.so.6
#58 0x082359e0 in ?? ()
#59 0xbf7fc0f8 in ?? ()
#60 0xb630b010 in free () from /lib/i686/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Comment 1 Paweł Marciniak 2007-11-16 12:48:59 UTC
I think this is a duplicate of bug #152092. From what you've written, the crash doesn't depend on any particular image being displayed, but is rather random.
Comment 2 Santam Chakraborty 2007-11-16 17:17:30 UTC
Sorry for the duplication - I am not a programmer so is there any other way I can help or give more information? Yes you are correct that it is apparently random and doesnot depend on the image being loaded - but I have noticed that few times I kept the program running for sometime it does not crash when exiting.
Comment 3 caulier.gilles 2008-01-04 11:13:59 UTC

*** This bug has been marked as a duplicate of 152092 ***
Comment 4 caulier.gilles 2022-01-20 06:40:14 UTC
Fixed with https://bugs.kde.org/show_bug.cgi?id=152092